Mcp Server
Let your agent query Counterparty on Bitcoin, compose transactions, and sign via MCP instead of hand-rolling node RPC scripts.
Overview
io.github.XCP/mcp-server is an MCP server for the Build phase that lets agents query, compose, and sign Counterparty token operations on Bitcoin.
What is this MCP server?
- Query, compose, and sign Counterparty (Bitcoin token protocol) operations from MCP
- npm package @21e14/mcp-server v1.0.1 with stdio transport
- COUNTERPARTY_NODE env (default https://api.counterparty.io:4000)
- Optional WIF SIGNER_PRIVATE_KEY and SIGNER_ADDRESS for transaction signing
- On-chain finance MCP—not a wallet UI or generic blockchain explorer skill
- Server version 1.0.1
- Default node: https://api.counterparty.io:4000
- npm identifier @21e14/mcp-server
What problem does it solve?
You are building Bitcoin Counterparty features but repeating node RPC and signing steps the agent cannot safely invoke without a dedicated MCP bridge.
Who is it for?
Indie builders shipping agent-assisted Counterparty tooling who already understand WIF keys and node endpoints.
Skip if: Non-crypto products, teams forbidding hot keys in dev environments, or users who only need read-only block explorers without MCP.
What do I get? / Deliverables
After configuration, Claude or another MCP client can call tools to interact with Counterparty using your node URL and optional signing credentials.
- MCP tools wired to Counterparty query and compose flows
- Optional signing path when secret key and address env vars are set
Recommended MCP Servers
Journey fit
Token protocol work lands in Build when you integrate on-chain systems into a product or internal tooling. Integrations is the canonical shelf because the server wraps Counterparty node access and signing for agent-driven workflows.
How it compares
Counterparty protocol MCP bridge, not a multi-chain DeFi aggregator or security audit skill.
Common Questions / FAQ
Who is io.github.XCP/mcp-server for?
It is for developers building on Counterparty who want MCP tools for query, compose, and sign flows from an AI coding agent.
When should I use io.github.XCP/mcp-server?
Use it in Build when integrating Counterparty into an agent workflow and you need structured tool calls instead of manual RPC experimentation.
How do I add io.github.XCP/mcp-server to my agent?
Install @21e14/mcp-server from npm, set COUNTERPARTY_NODE and signing env vars if needed, register the stdio MCP server in your client config, and restart.