Bostrom MCP
Let your agent read Bostrom chain state and optionally sign transactions while you build or debug Cosmos-style blockchain features.
Overview
io.github.cyberia-to/bostrom-mcp is a MCP server for the Build phase that offers 86 tools to read Bostrom chain state and sign transactions when a wallet mnemonic is configured.
What is this MCP server?
- 86-tool MCP server covering Bostrom blockchain read and write operations
- Read chain state without secrets; optional BOSTROM_MNEMONIC unlocks signing and write tools
- npm package bostrom-mcp v0.5.0 with stdio transport for local agent hosts
- Published from github.com/cyberia-to/bostrom-mcp with MCP registry schema 2025-12-11
- 86 MCP tools documented in the server description
- Package version 0.5.0, identifier bostrom-mcp on npm, stdio transport
- Optional secret env: BOSTROM_MNEMONIC for write tools; read tools work without it
What problem does it solve?
Chain development sessions stall when you manually run dozens of RPC queries and wallet commands instead of letting the agent inspect Bostrom state in context.
Who is it for?
Solo Web3 builders targeting Bostrom who want agent-assisted debugging, state inspection, and scripted txs with an optional mnemonic for write tools.
Skip if: Teams on other chains without Bostrom, or anyone who needs a custody solution rather than a dev-time MCP wallet hook.
What do I get? / Deliverables
Once bostrom-mcp is registered, your agent can query and optionally sign on Bostrom through MCP tools while you stay in the editor.
- Local MCP server exposing 86 Bostrom-oriented tools to your agent
- Read-only chain inspection without wallet secrets
- Optional transaction signing path when mnemonic is configured securely
Recommended MCP Servers
Journey fit
Builders adopt this server when implementing or testing Bostrom-aware automation in code, which maps to Build rather than passive monitoring in Operate alone. Integrations fits because the package is a large tool surface (read + write) over a specific chain RPC/wallet flow, not generic cloud deploy.
How it compares
Bostrom-specific blockchain MCP with 86 tools, not a generic Ethereum JSON-RPC skill or a hosted indexer.
Common Questions / FAQ
Who is io.github.cyberia-to/bostrom-mcp for?
Developers building or operating on the Bostrom blockchain who use MCP agents and want consolidated read and sign tooling instead of ad hoc CLI scripts.
When should I use io.github.cyberia-to/bostrom-mcp?
Use it during Build and integration testing when you need chain reads in every session and controlled writes only after you set BOSTROM_MNEMONIC for signing tools.
How do I add io.github.cyberia-to/bostrom-mcp to my agent?
Install the npm package bostrom-mcp, configure stdio in your MCP client, and optionally set the secret environment variable BOSTROM_MNEMONIC for write and sign tools per the server registry.