🤖 Talk to Blurt: The Blockchain You Can Finally Talk To

Hello Blurtians!

Imagine simply asking your AI:

"I just wrote a post about my cat. Which Blurt community should I publish it in, and why?"

"Give me an investor snapshot of Blurt: market price, market cap, circulating supply, blockchain health, witness activity, and anything else an investor should know."

"Recommend three Blurt witnesses I should support, and explain your choices based on their real contributions to the ecosystem."

No searching through explorers.
No learning blockchain APIs.
No switching between five different websites…

…you simply ask your AI.

Yesterday, I had a conversation with @megadrive, one of the founders of Blurt, about something I had built — and then quietly shelved — about eight months ago: a small MCP connector for Blurt (Model Context Protocol). Back then it was just a proof of concept, a weekend experiment to see if an AI could talk to our lovely Blurt blockchain.

That conversation lit the fire again. And the timing turned out to be perfect: this very morning, @megadrive published *Blurt's 6th Anniversary — The Roadmap Ahead*, and there it was, written in black and white among the projects for Blurt's future:

Blurt Official Public MCP — What began as a community wish list item, became possible thanks to @nalexadre, who is generously open-sourcing his prototype repository.

So I dusted off the project, rebuilt it properly, expanded it far beyond the original proof of concept, and open-sourced it under GPL-3.0.

The result isn't just another developer project.

It gives Blurt something it never had before: a standard, AI-friendly interface that lets modern assistants explore the blockchain using natural language instead of blockchain-specific APIs.

From today, any AI that understands MCP can understand Blurt.

🧩 First, what on earth is an "MCP connector"?

If the term sounds intimidating, don't worry — the idea is simple.

For a long time, AI assistants like ChatGPT or Claude were closed boxes. You asked a question, and they answered from memory. Useful, but limited — and often out of date or simply making things up when they didn't know.

MCP (Model Context Protocol) changes that. Originally created by Anthropic, it's now an open standard that the big players — Claude, ChatGPT, Grok, Mistral — all support, even new AI Agent like Hermes, OpenClaw. Think of it as a universal power socket for AI: it lets an assistant safely plug into the outside world — apps, databases… or a blockchain like Blurt.

An MCP connector is the bridge. It tells the AI: "here's what you're allowed to read, and here's how to ask for it."

I already wrote about why this matters for our community in two earlier posts, if you want the bigger picture:

The Blurt MCP connector is exactly that bridge — between any MCP-capable AI and the Blurt blockchain.

🔍 So what can it actually do?

Once connected, you can ask your favorite AI questions about Blurt in plain language, and it will fetch the real, live answer straight from the chain. No commands, no code, no copy-pasting block explorers.

It currently exposes 20 read-only tools, grouped into a few families:

💰 Market & network — the BLURT price in USD, market cap, circulating supply, chain health.

👤 Accounts & wallets — anyone's profile, balance, Blurt Power, rewards, pending (unclaimed) rewards.

✍️ Content & discovery — trending posts, an account's blog, a single post and its discussion.

🏅 Curation — who upvoted a post, the biggest curators on it, and how much a given account's upvote is worth in BLURT and dollars.

🌐 Communities — discover communities, their details, and which ones an account follows.

🏛️ Governance — the witness ranking, a witness's health (is it up to date and producing blocks?), and which witnesses an account supports.

⚖️ Comparison — put 2 to 5 accounts side by side in a single question.

One important thing for peace of mind: everything is read-only. The connector can look, never touch. It holds no private keys and cannot post, vote, or move a single BLURT on your behalf. (Signing actions are a separate, future chapter — see the roadmap at the end.)

⚙️ How to set it up (in ~3 minutes)

The connector runs as a remote MCP server, so you just give your AI one address:

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

ℹ️ The exact menu names below change often as these apps evolve — but the idea is always the same: find "Connectors" or "Integrations", add a custom/remote MCP server, and paste the URL above.

🟣 Claude Desktop (Anthropic) - Free Tier

Open Settings → Connectors.
Click Add custom connector.
Paste the URL and confirm. Claude will list the Blurt tools — you're done.

🟢 ChatGPT Web version (OpenAI) - Free Tier

Go to Settings → Apps (you may need Developer mode enabled, depending on your plan).
Click on Create App.
Paste the URL and confirm.

⚫ Grok (xAI) - Free Tier

Open Skills and Connectors.
Click on Connectors then New Connector.
Click on Custom then Paste the URL and confirm.

🟠 Vibe (Mistral) - Free Tier

Open the Context / Connectors section.
Click on Add connector then Custom MCP Connector tab.
Paste the URL and confirm.

That's it. No wallet, no extension, no risk.

💬 Your first prompts (copy-paste these)

Here's the magic part: you never tell the AI which tool to use. You ask a question in plain words, and it picks the right tools, chains several of them together, and hands you the answer. Start simple, then watch it shine.

🟢 Warm-up — one quick question

"What is the current BLURT price and market cap?"

"What are the most popular Blurt communities right now?"

"Find a Blurt community about cats and show me its details."

🔵 Dig into an account

"Give me a deep analysis of the Blurt account nalexadre: profile, wallet value in USD, who follows him, and which communities he belong to."

"Compare Blurt accounts nalexadre, megadrive and khrom — stake, reach and earnings — and present it as a table."

🟣 Now show off — these chain many tools at once

"Take nalexadre's latest post, find its biggest curators, and tell me how much each of their upvotes is worth in USD."

"Show me today's top trending Blurt post, summarize it in 3 bullet points, then tell me who upvoted it."

"List the top 30 Blurt witnesses and flag any that look inactive or behind on node version."

"Which witnesses does nalexadre vote for — and are they all healthy and still producing blocks?"

"Give me an investor snapshot of Blurt: price, market cap, supply, and how the #1 witness's stake compares to the rest."

🔥 Boss level

"Imagine you are preparing an executive report for someone considering acquiring 10% of the entire Blurt supply. Give me a complete assessment of the ecosystem: blockchain health, witness decentralization, infrastructure, developer activity, community growth, content quality, AI readiness, strengths, weaknesses and the biggest risks over the next three years." (👉 *ChatGPT answer*)

"From an investor’s perspective, evaluate whether delegating Blurt Power to @beblurt makes sense. Consider not only curation returns, but also the broader value BeBlurt brings to the ecosystem: infrastructure, public RPC services, frontend adoption, AI integrations, developer tooling, search engine visibility, community growth and long-term sustainability. Finish with a balanced recommendation, including potential drawbacks."

"You have been hired as Blurt’s Head of Growth. Analyze the blockchain, identify its three biggest weaknesses and its three biggest competitive advantages, then propose five concrete initiatives that could realistically double the number of active users over the next 12 months. Base your recommendations on current on-chain data, not assumptions."

_{👉 *Full Claude answer* - 👉 *ChatGPT answer*}

Try one, then just keep asking follow-up questions. The more you push, the more impressive it gets.

🛠️ For the curious & the devs — what happened under the hood

(Non-technical readers can happily stop here — the rest is bonus material.)

Rebuilding the old proof of concept into something I'd be comfortable open-sourcing turned into a proper little engineering journey, and a few moments are worth sharing:

From 7 to 20 tools. The PoC had a handful of features. I rebuilt the foundation, then added market, social, curation and governance tools — each with descriptions carefully written for AI to understand when and how to use them. With an AI connector, the tool's description is its user interface.

Tests that earned their keep. I built a test suite across three layers (offline logic, live in-memory, and full end-to-end over the real transport). It immediately caught two genuine routing bugs — and later saved me from a nasty one.

The bug hunt. After deploying, one feature would loop forever inside the AI. After a long investigation, the root cause turned out to be a slow-request crash deep in the RPC transport of an underlying library. I wrote up a precise, fact-based report, and the library's developer is now working on a fix — a nice example of the open-source loop working as intended. To make sure it never comes back, I added a deterministic test that fails on purpose if the bug ever returns.

Done properly. The project is open-source under GPL-3.0, with a clean README, continuous integration, semantic versioning and a changelog. It's read-only by design — no private keys anywhere.

🔓 Want to look under the hood, open an issue, or contribute? The full source is on GitLab — feedback and merge requests are very welcome:
👉 **https://gitlab.com/blurt-blockchain/blurt-mcp-server**

And it's not just my own toy anymore: as the roadmap states, this prototype is the seed for a Blurt Official Public MCP, with future transaction-signing capabilities planned through the upcoming SSM Wallet — which would finally let an AI act on Blurt, securely and with your consent. (That's the part I deliberately left out for now: reading is safe for everyone; writing deserves a proper, key-secure foundation.)

🙌 Closing thoughts

What I love about this is how it fits Blurt's moment. We're six years in, the roadmap is looking forward to AI, discoverability, and an official MCP, and here's a small, concrete piece anyone can try today — turning our blockchain into something you can simply talk to.

And this isn't only for end users.

Developers can now build AI-powered applications on top of Blurt without first learning the blockchain APIs.

If their AI already supports MCP, it already speaks Blurt.

I'd genuinely love your help: connect it, ask it things, and tell me what's missing. Which tools would make it more useful to you? Curators, authors, investors, witnesses — you all look at Blurt differently, and that feedback is exactly what will shape the next version.

Happy upcoming 6th Birthday, Blurt! 🎉

Read-only. No keys. Just ask.

@nalexadre

Top 20 Witness on Blurt

Strengthening the ecosystem foundation

Beyond Block Production

Running a witness node is only one part of my contribution to Blurt.

I actively operate and maintain:

a public RPC server → https://rpc.beblurt.com
the BeBlurt frontend → https://beblurt.com
open-source tools available on my GitLab → https://gitlab.com/imtase
advanced on-chain analytics
a delegation system via @beblurt & manual curation
experimental integrations connecting Blurt with AI environments and external systems

My role is not limited to producing blocks.

It is about:

strengthening infrastructure
improving accessibility
increasing transparency
enabling data-driven understanding
supporting organic curation
experimenting with new integrations

Supporting my witness is not about increasing my rewards —
it is about maintaining an actively developed infrastructure node within the Top 20.

If you believe that infrastructure, transparency, curation balance, and innovation matter,
your support is always appreciated.