blurt-mcp-server

Talk to the Blurt blockchain from an AI assistant.

blurt-mcp-server is a Model Context Protocol (MCP) server for the Blurt blockchain. It gives MCP-capable assistants such as Claude, ChatGPT, Cursor, Codex and other tools a safe way to read public Blurt blockchain data: accounts, posts, communities, witnesses, curation data, notifications and market information.

The public hosted endpoint is read-only by default. It holds no private keys and cannot post, vote, transfer, or change on-chain state.

🟢 Try it in 30 seconds — nothing to install. Add this hosted endpoint as a custom/remote MCP connector in your AI app:

https://mcp.blurt-blockchain.com/mcp

Who is this for?

• Blurt blockchain users and community members who want to ask natural-language questions about accounts, posts, communities, witnesses and rewards.
• Witnesses and ecosystem maintainers who want a quick read-only view of network health, witness status, curation and public activity.
• AI-assistant users who want their assistant to understand Blurt blockchain data without copying URLs or JSON by hand.
• Developers and operators who want to self-host, inspect, extend or integrate an MCP server for the Blurt blockchain.

If you already know MCP, this package gives you a ready-to-use Blurt blockchain connector. If you are new to MCP, think of it as a standard way for an AI assistant to call well-described tools instead of scraping webpages or guessing API calls.

What you can ask

You never need to name a tool. Ask a normal question and let the AI assistant choose the right tool or chain of tools:

• "What is the Blurt blockchain's market cap and how many BLURT are in circulation?"
• "Analyze the account nalexadre: profile, vote value in USD, followers and latest posts."
• "Find a community about cats and show me its details."
• "List the top 10 Blurt blockchain witnesses and flag any that look inactive or behind on version."
• "Who are the biggest curators on this post, and how much is each of their upvotes worth?"

→ More examples and the read-tool reference: Tools & resources.

What it can do

| Area | Examples | | --- | --- | | 👤 Accounts & wallets | profiles, balances, Blurt Power, operation history, rewards, pending rewards, relationships, delegations, account lookup | | ✍️ Content | individual posts, full discussion trees, account posts, trending/ranked publications | | 🌐 Communities | discovery, details, subscriptions and roles | | 🌱 Onboarding | referrals from the beBlurt referral system | | 🏅 Curation | post voters and rebloggers, vote-value estimates in BLURT and USD | | 🔔 Notifications | recent notifications and unread counts | | 🏛️ Governance | witness ranking, witness health and account witness votes | | 💰 Market & network | BLURT price, market cap, supply, reward pool and chain status | | 🔎 Search / fetch | blurt:// resource discovery for connector-style clients | | ✍️ Write (opt-in, local by default) | claim, vote, comment, post and social actions signed locally with a posting key; see write operations |

Quick start

1. Hosted endpoint

Use this when your AI app supports remote MCP / Streamable HTTP connectors:

https://mcp.blurt-blockchain.com/mcp

2. Desktop app through a bridge

Some desktop apps only launch local commands. In that case, bridge the hosted endpoint with mcp-remote:

{
  "mcpServers": {
    "blurt": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.blurt-blockchain.com/mcp"]
    }
  }
}

3. Fully local stdio server

Use this when your client launches a local MCP server process:

npx -y -p @blurt-blockchain/blurt-mcp-server blurt-mcp-stdio

For client configuration, prefer the same environment-file layout used by write mode, even for read-only usage:

{
  "mcpServers": {
    "blurt": {
      "command": "npx",
      "args": ["-y", "-p", "@blurt-blockchain/blurt-mcp-server", "blurt-mcp-stdio"],
      "env": { "BLURT_ENV_FILE": "/home/you/.config/blurt-mcp/secret.env" }
    }
  }
}

The file can start empty or contain read-only configuration such as BLURT_RPC_URLS and BLURT_PRICE_URL. Add a posting key only if you deliberately enable local write tools.

→ Full setup guide: Installation & usage → Copy-paste client configs: Install snippets.

Compatible clients

Remote-capable clients can use the hosted endpoint directly. Stdio-only clients can either bridge the hosted endpoint with mcp-remote or run the package locally.

| Client | Type | Local stdio | Remote HTTP | Config file | Open source | | --- | --- | ---: | ---: | --- | ---: | | ChatGPT web — Apps / Connectors | Web | No | Yes | UI only | No | | Claude Desktop | Desktop | Yes | Yes | claude_desktop_config.json | No | | Claude Code | CLI | Yes | Yes | ~/.claude.json, .mcp.json | No | | OpenAI Codex (CLI / IDE) | CLI / IDE | Yes | Yes | ~/.codex/config.toml | Yes | | VS Code — Copilot agent | IDE | Yes | Yes | .vscode/mcp.json | Partial | | Cursor | IDE | Yes | Yes | .cursor/mcp.json | No | | Windsurf / Cascade | IDE | Yes | Yes | mcp_config.json | No | | Gemini CLI | CLI | Yes | Yes | ~/.gemini/settings.json | Yes | | JetBrains AI Assistant | IDE | Yes | Yes | Settings UI | No | | Cline | IDE ext. / CLI | Yes | Yes | ~/.cline/mcp.json | Yes |

→ Full compatibility matrix: Compatible clients. (Community-maintained; as of 2026-06-28.)

Documentation

• Overview — start here if you are new to the project
• Installation & usage — requirements, configuration and connection modes
• Install snippets — copy-paste hosted, package, stdio and client configs
• Tools & resources — readable tool categories and example prompts
• Generated tool reference — generated contract index from the tool registry
• Write operations — opt-in local signing with a posting key
• Compatible clients — client compatibility notes
• Architecture, MCP compatibility register, Deployment, Operations
• Security · Contributing

Security

The server is read-only by default and holds no private keys. Optional write tools are opt-in and local by default, use a posting key only and are not exposed over HTTP unless an operator deliberately enables an unsafe trusted-deployment override.

New write deployments should start with a small capability profile such as BLURT_WRITE_PROFILE=curator. See the security guide and write operations.

Support

You can contact the maintainer in the dev channel of the Blurt Discord server: https://discord.blurt.world/.

Useful Blurt blockchain development posts can also be found in the Dev on Blurt community.

Contributing

Pull requests for new features, bug fixes and documentation improvements are welcome.

Before opening a pull request, run the checks that match your change. For most code changes:

npm ci
npm run docs:check
npm run build
npm test
npm run typecheck

See CONTRIBUTING.md for the development workflow.

Author

@nalexadre — Blurt blockchain witness.

License

This package currently declares GPL-3.0-or-later in package.json.

See the LICENSE file for the full license text.