Blurt MCP Server
The Blurt MCP server connects AI assistants to public Blurt blockchain data.
It uses the Model Context Protocol TypeScript SDK and supports MCP clients negotiating protocol version 2025-06-18 for its implemented tools and resource-template features. See the MCP compatibility register for the maintained compatibility decisions.
If you are new to MCP, think of it as a standard bridge between an AI assistant and a set of well-described tools. Instead of asking the assistant to guess where data lives, MCP tells the assistant which tools are available, what each one does, and what information it needs.
For the Blurt blockchain, that means an assistant can answer questions about accounts, posts, communities, witnesses, rewards, curation and market data without you manually copying API responses or blockchain explorer pages.
Who is this for?
- People discovering the Blurt blockchain who want a conversational way to explore public activity.
- Blurt blockchain users and community members who want quick answers about posts, communities, rewards or witnesses.
- Witnesses and operators who want a readable view of network status and public endpoint behavior.
- Developers and maintainers who want to self-host, inspect or extend the MCP server.
- AI assistant users who want their assistant to use Blurt blockchain data safely and predictably.
Why it exists
Public blockchain data is useful, but it is not always convenient for humans or AI assistants to navigate directly. This project gives the Blurt blockchain ecosystem a focused MCP interface that is:
- read-only by default for the hosted public endpoint;
- plain-language friendly, because users ask questions instead of choosing tools by hand;
- transparent, because the tools, safety posture and configuration are documented;
- self-hostable, because operators can run the same package locally or behind their own HTTP endpoint;
- neutral infrastructure, because it does not enforce content, account, community or social policy.
Fastest path
Use the hosted public endpoint when your client supports remote MCP / Streamable HTTP:
https://mcp.blurt-blockchain.com/mcpUse the npm package when your client launches a local stdio server:
npx -y -p @blurt-blockchain/blurt-mcp-server blurt-mcp-stdioDocumentation map
Start
- Installation & usage — concepts first, then setup choices
- Install snippets — copy-paste client configuration
- Compatible clients — client support and known config locations
Reference
- Tools & resources — readable tool categories and examples
- Generated tool reference — generated contract index from the tool registry
- Write operations — optional local signing with a posting key
- Security — security model and threat posture
Operate
- Deployment overview — HTTP surface, topology, reverse proxy guidance and deployment method choices
- PM2 deployment — process-manager setup using
BLURT_ENV_FILE - Operations
- Cache policy
- Load checks
Maintain
- Architecture
- MCP compatibility register
- ADR 0001 — neutral infrastructure
- Development
- Release/provenance