MCP Tools Reference

Beta integrations should use DCP through MCP. The HTTP endpoint is streamable HTTP MCP, not a public REST API.

Endpoint

dcp-agent run --mode http-mcp --host 127.0.0.1 --port 8420
http://127.0.0.1:8420/mcp

Initialize With curl

curl -i -sS \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -X POST http://127.0.0.1:8420/mcp \
  --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"curl-test","version":"1.0.0"}}}'

Copy the returned mcp-session-id.

List Tools

curl -i -sS \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'mcp-session-id: PASTE_SESSION_ID_HERE' \
  -X POST http://127.0.0.1:8420/mcp \
  --data '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'

Tool Input Notes

  • chain is currently solana.
  • currency can be SOL, USDC, USDT, or 1LY.
  • 1LY SPL mint: Aih3sbAbu39Yn7jB2Qf4btZ5eWtDGQJH2gMfC4qdBAGS.
  • Use identity.name for name and identity.email for email. Do not guess aliases.

Approval Behavior

Reads, writes, message signing, and transaction signing can require approval. The user can approve in DCP Desktop or Telegram. Small transactions may auto-approve if under the user's configured threshold.