DERO MCP Server

DERO MCP server

A read-only Model Context Protocol server for the DERO privacy blockchain — a private-by-default Layer 1 with encrypted balances, private smart contracts (DVM-BASIC), and no public transaction graph. 21 daemon primitives + 12 composite tools (including TELA on-chain app inspection and dURL→SCID discovery), with a bundled documentation index spanning derod, tela, hologram, and deropay.

[MCP Registry] [CI] [dero-mcp-server MCP server]

Registry listing: io.github.DHEBP/dero-mcp-server · Version: 0.6.0 · Transports: stdio (default, npm package) · streamable-http (--http, for self-hosting)

What is an MCP server

An MCP server (Model Context Protocol) is a small program that gives your AI assistant — Claude Desktop, Cursor, OpenCode, ChatGPT with Custom Connectors — the ability to call specific tools on your behalf. Instead of the AI talking about DERO from memory, it can actually look things up: fetch a block, read a contract, search the docs, trace a transaction, estimate a deploy.

You install it once and point your AI host at it. From then on, every DERO question you ask in chat hits live chain data and the bundled docs corpus — not the AI's training cutoff.

What is DERO

If you're new to DERO: it's a privacy-first L1 blockchain — often described as a private alternative to Ethereum for builders who want smart contracts without a transparent ledger, or as a Monero alternative for users who want account-based privacy with native programmability instead of UTXO-only payments. Homomorphically encrypted balances. Ring signatures hide senders. Zero-knowledge range proofs (Bulletproofs) hide amounts. There is no public transaction graph. The current mainnet is DERO Stargate.

Full docs: derod.org

About this server

Model Context Protocol (MCP) server that exposes read-only and analysis calls against a DERO Stargate daemon JSON-RPC endpoint. Ships as a stdio process for local MCP hosts (Claude Desktop, Cursor, OpenCode) or in streamable-HTTP mode behind a domain (e.g. mcp.derod.org) for ChatGPT Custom Connectors, Cursor hosted mode, and any agent that needs a remote URL. See deploy/ for a reference self-hosted deployment.

Quick start

Get a working DERO MCP connection in under 5 minutes.

What you need

• Node.js 20+ (install) — verify with node --version.
• An MCP host — Claude Desktop, Cursor, OpenCode, or ChatGPT with Custom Connectors. This walkthrough uses Claude Desktop; the JSON config below works identically in Cursor and OpenCode.
• Optional: a local DERO daemon. If one is running on 127.0.0.1:10102, the server detects and uses it automatically; otherwise it falls back to a public RPC, so it works with zero setup. Run your own for production — how to.

1. Open your MCP host's config

Create the file if it doesn't exist.

2. Add the DERO MCP server

{  "mcpServers": {    "dero-daemon": {      "command": "npx",      "args": ["-y", "dero-mcp-server"]    }  }}

This uses npx to fetch and run the latest published version — no manual install or build required.

The server auto-detects a local node at 127.0.0.1:10102. To pin a specific daemon (custom port or a remote URL), add an env block:

"env": { "DERO_DAEMON_URL": "http://127.0.0.1:10102" }

3. Restart your MCP host

Fully quit and reopen — not just refresh. MCP servers load at startup.

4. Verify it works

In a new chat:

"What's the current DERO chain height?"

A number back means you're connected. If you see an error, confirm the config file path is correct and your host was fully restarted (not just refreshed).

Once it's working, jump to Try a prompt for a full tour.

What you can do with it

Once installed, your MCP host can do all of these on your behalf — in natural language, no JSON-RPC needed:

• Inspect the chain — blocks, transactions, mempool, encrypted balances, registered names
• Analyze smart contracts — read code and state, classify the pattern, estimate deploy gas, pull relevant DVM-BASIC docs in one call
• Trace transactions — look up any hash, confirm inclusion, classify the kind (transfer / SC install / SC call)
• Explore the on-chain web (TELA) — discover apps by name (vault.tela → SCID), browse what's deployed, inspect an app's manifest and files, and read the actual on-chain HTML/JS/CSS — no separate indexer to run
• Search the docs — across all four DERO sites (derod, tela, hologram, deropay)
• Run composite analyses — chain health, claim audits, docs path recommendations, deploy pre-flights — each returns curated DERO docs citations alongside the data

Try a prompt

After installing and restarting your MCP host, paste any of these. Start simple and work up.

Basic

Single-tool questions that verify the install and exercise live queries.

"What's the current DERO chain height?"

"Resolve the DERO name 'engram' to an address."

"Find the documentation page on Bulletproofs."

"What does the smart contract at SCID 0000…0001 do?"

Intermediate

Composite tools that fan out into multiple primitives and return a synthesized answer with citations.

"Explain the smart contract at SCID 0000000000000000000000000000000000000000000000000000000000000001 — what it does, its functions, and which DVM-BASIC docs are relevant."

"Trace transaction with full context — confirmation, classification, and what it touched."

"What's the right reading path for someone new to DERO smart contracts who wants to deploy a DVM-BASIC contract?"

"Estimate the gas cost to deploy this DVM source: "

TELA — the decentralized web on DERO

TELA apps are full web apps (HTML/CSS/JS) deployed entirely on-chain. The server discovers and reads them with no external indexer — the first discovery query runs a one-time ~15s scan, then it's instant.

"What's the SCID for vault.tela?"

"What TELA apps exist on DERO? Show me a few."

"Inspect the TELA app at SCID — what is it, who made it, and what files does it have?"

"Show me the actual HTML of that app's index.html."

For multi-step agent recipes, per-tool guidance, error contract, and the composite-first rule, see SKILL.md.

Not included (by design): wallet RPC (transfer, scinvoke), DERO.SendRawTransaction, DERO.SubmitBlock. Those can move funds or consensus data; add them only with explicit user consent and a locked-down setup.

See also

• SKILL.md — per-tool agent runbook: composite-first rule, structured error contract, citation rules, agent-loop recipes, port reference.
• POSITIONING.md — who DERO MCP is for, who it isn't, comparison vs ACP / Stripe / Crossmint / Skyfire, privacy posture.

Requirements

• Node.js 20+
• A reachable DERO daemon with RPC enabled (local node or your own remote URL).

Install & build

cd dero-mcp-servernpm installnpm run build

Run (auto-detects a local node at 127.0.0.1:10102, else public fallback, when DERO_DAEMON_URL is unset):

node dist/index.js

Or set an explicit URL (e.g. your local daemon):

DERO_DAEMON_URL=http://127.0.0.1:10102 node dist/index.js

Daemon resolution is local-first: with DERO_DAEMON_URL unset, the server uses a local node at 127.0.0.1:10102 if it answers, else the baked-in third-party public RPC (82.65.143.182:10102). Prefer your own node for privacy.

Strip a trailing /json_rpc if you paste a full JSON-RPC URL — this server appends /json_rpc.

HTTP mode (self-hosted)

For clients that can't launch a local subprocess — ChatGPT Custom Connectors, Cursor hosted mode, n8n / Zapier integrations — run the server in streamable-HTTP mode and put it behind your own domain:

DERO_MCP_AUTH_TOKEN=$(openssl rand -base64 48) \  dero-mcp-server --http# [dero-mcp-server] HTTP listening on 127.0.0.1:8787 (POST /mcp · GET /health)

Both stdio and HTTP serve MCP 2026-07-28 and retain compatibility with 2025-era clients. HTTP exchanges are stateless and do not issue Mcp-Session-Id; 2026 clients negotiate through server/discover.

For a turnkey deploy with Caddy + auto-TLS + Docker Compose, see deploy/README.md. It's a self-hosting reference for running your own hosted instance. The public mcp.derod.org instance was retired on 2026-10-10; use npx dero-mcp-server or self-host. The public default daemon behind a hosted instance may use an older GetInfo schedule formula than CalcSupply; verify_supply still treats the offline schedule number as authoritative (see Verify the Supply).

The stdio transport (below) and the HTTP transport share the same underlying server factory, so the tool surface, response shapes, and error codes are identical across both.

Claude Desktop (same pattern for OpenCode and Cursor)

Add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):

{  "mcpServers": {    "dero-daemon": {      "command": "node",      "args": ["/ABSOLUTE/PATH/TO/dero-mcp-server/dist/index.js"]    }  }}

Optional: add "env": { "DERO_DAEMON_URL": "http://127.0.0.1:10102" } to pin a specific daemon. Not needed if your local node uses the default port — the server auto-detects it.

Restart Claude Desktop (or your OpenCode/Cursor host).

Cursor (or OpenCode)

In Cursor Settings → MCP (or OpenCode MCP settings), add a server that runs the same command / args / env as above.

OpenCode

In OpenCode MCP settings, add a server with the same command / args / env as above.

Codex

Codex supports DERO MCP as either a local stdio server or a streamable-HTTP server. The stdio setup is simplest for local development because Codex launches the server process for each session.

Add the published npm package with:

codex mcp add dero-daemon --env DERO_DAEMON_URL=http://127.0.0.1:10102 -- npx -y dero-mcp-server

Replace http://127.0.0.1:10102 with your daemon base URL when using a custom host or port. Do not include /json_rpc; this server appends it.

Equivalent ~/.codex/config.toml:

[mcp_servers.dero-daemon]command = "npx"args = ["-y", "dero-mcp-server"]
[mcp_servers.dero-daemon.env]DERO_DAEMON_URL = "http://127.0.0.1:10102"

A copyable example lives at .codex/config.example.toml. Rename or copy it to .codex/config.toml only when you want a project-scoped Codex config; Codex loads project config only for trusted projects.

For an already-running streamable-HTTP deployment, add the URL instead:

codex mcp add dero-daemon --url http://127.0.0.1:8787/mcp

If the HTTP server requires a bearer token, store the token in an environment variable and add --bearer-token-env-var DERO_MCP_AUTH_TOKEN.

Restart Codex or start a new session, then run /mcp to confirm dero-daemon is enabled. A simple verification prompt is:

"What's the current DERO chain height?"

Environment

Maintainer: bundled docs

Docs tools read from data/docs-index.json, committed in this repo and shipped with the npm package. Rebuild the index when dero-docs changes:

npm run release:docs-checkgit add data/docs-index.json && git commit -m "Refresh bundled docs index."

Or run Refresh docs bundle under Actions to open a PR. Pushes to dero-docs main can trigger that workflow via repository_dispatch when MCP_DOCS_SYNC_TOKEN is configured on the docs repo.

After merging a bundle update: bump the patch version in package.json and server.json, then npm publish --otp=... and mcp-publisher publish.

Testing

# Check daemon connectivitynpm run doctor
# MCP surface contract checks (tools/resources/prompts + error probe)npm run smoke:mcp
# Docs retrieval checks (bundled index — no clone required)npm run smoke:docs
# Run flow tests (10 RPC checks)npm run test:flows
# Typechecknpm run typecheck

Flow tests run against the default public RPC. Set DERO_DAEMON_URL to test against your own daemon.

CI runs on every push and PR — see .github/workflows/ci.yml.

Official MCP Registry

Publish flow (maintainers):

mcp-publisher validatemcp-publisher login githubmcp-publisher publish

Verify listing:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.DHEBP/dero-mcp-server"

MCP Surface

• Tools (33): 21 daemon read/analysis primitives + 12 composites, including verify_supply (offline CalcSupply), TELA app inspection (tela_inspect, tela_get_doc_content), TELA discovery (dero_durl_to_scid, dero_tela_list_apps), and docs retrieval (dero_docs_search, dero_docs_get_page, dero_docs_list)
• Resources (4): dero://mcp/server-info, dero://mcp/safety-boundary, dero://mcp/example-flows, dero://mcp/composites
• Prompts (5): network_health_check, inspect_smart_contract, trace_transaction, find_dero_docs_for_intent, estimate_deploy_for_contract

Error Contract

When a tool call fails, the server returns a structured error payload in tool content:

{  "ok": false,  "tool": "dero_get_sc",  "_meta": {    "error": {      "code": "RPC_UNREACHABLE",      "hint": "Confirm daemon is running and reachable, then rerun `npm run doctor`.",      "retryable": true,      "raw": "fetch failed"    }  }}

Common code values:

• INVALID_INPUT
• RPC_INVALID_PARAMS
• RPC_METHOD_NOT_FOUND
• RPC_HTTP_ERROR
• RPC_UNREACHABLE
• RPC_INVALID_RESPONSE
• TOOL_EXECUTION_ERROR

Roadmap

• Optional wallet-RPC tools behind DERO_ENABLE_WALLET_RPC=1 + separate URL.
• Stricter typing / OpenAPI-derived tool schemas.
• TELA-aware contract tooling (INDEX/DOC inspection, on-chain app discovery).

License

MIT