MCP server for interacting with cryptocurrency daemon RPC interfaces
If you already use Coin Daemon MCP, the coin daemon mcp mcp server is the piece that lets your assistant work with it directly. MCP server for interacting with cryptocurrency daemon RPC interfaces.
A Model Context Protocol (MCP) server for interacting with cryptocurrency daemon RPC interfaces. This server enables AI assistants to help manage and interact with cryptocurrency nodes in a controlled manner.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
send-coins — Send transparent transactionszsend-coins — Send shielded transactions (for privacy coins)shield-coins — Convert transparent to shielded fundsget-balance — Check balancesexecute-command — Execute any supported RPC commandcheck-status — Get daemon informationTools — 1. Transaction Management - send-coins: Send transparent transactions - zsend-coins: Send shielded transactions (for privacy coins) - shield-coinsResources — 1. Documentation Resources - crypto://{coinType}/help: Get detailed documentation for specific cryptocurrencies - daemon://{name}/help: Get help textPrompts — 1. Transaction Guidance - send-transaction-template: Generate a guided prompt for constructing transactions@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: CONFIG_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Coin Daemon MCP's toolset — send-coins, zsend-coins, shield-coins and 6 more — is a fair guide to whether it matches your workflow. It is maintained by raw391; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| send-coins | Send transparent transactions |
| zsend-coins | Send shielded transactions (for privacy coins) |
| shield-coins | Convert transparent to shielded funds |
| get-balance | Check balances |
| execute-command | Execute any supported RPC command |
| check-status | Get daemon information |
| Tools | 1. Transaction Management - send-coins: Send transparent transactions - zsend-coins: Send shielded transactions (for privacy coins) - shield-coins: Convert transparent to shielded funds |
| Resources | 1. Documentation Resources - crypto://{coinType}/help: Get detailed documentation for specific cryptocurrencies - daemon://{name}/help: Get help text specific to a daemon |
| Prompts | 1. Transaction Guidance - send-transaction-template: Generate a guided prompt for constructing transactions |
{
"mcpServers": {
"cryptocurrency": {
"command": "npx",
"args": [
"-y",
"@raw391/coin-daemon-mcp"
],
"env": {
"CONFIG_PATH": "C:/CryptoConfig/daemon-config.json"
}
},
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"C:/CryptoData"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CONFIG_PATH | Filesystem location the server is allowed to use. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.