Skip to main content
Glama
MinaProtocol

Mina MCP Server

Official
by MinaProtocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MINA_MCP_MODENoServer mode: live, tutorial, or snapshotsnapshot
ARCHIVE_DB_HOSTNoArchive PostgreSQL hostlocalhost
ARCHIVE_DB_PORTNoArchive PostgreSQL port5432
MINA_MCP_NETWORKNoNetwork for live mode: devnet, mainnet, mesa
MINA_MCP_WALLETSNoPath to wallets.json for live-write mode
MINA_MCP_HTTP_PORTNoHTTP port for http transport3000
MINA_MCP_TRANSPORTNoTransport type: stdio or httpstdio
ARCHIVE_API_ENDPOINTNoArchive-Node-API GraphQL endpointhttp://localhost:8282
MINA_GRAPHQL_ENDPOINTNoMina daemon GraphQL endpointhttp://localhost:3085/graphql
ACCOUNTS_MANAGER_ENDPOINTNoTest accounts manager endpointhttp://localhost:8181
MINA_MCP_ALLOW_MAINNET_WRITESNoSet to '1' to allow mainnet writes

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_sync_statusA

[infra] Get the sync status and daemon info. Returns the flat daemon status object directly — fields like syncStatus, blockchainLength, stateHash, numAccounts, chainId, addrsAndPorts are at the top level (not nested under daemonStatus). In snapshot mode returns archive DB stats instead. In tutorial and live modes returns the live daemon status.

query_archive_sqlA

[infra][tutorial+snapshot] Execute a read-only SQL query against the archive database. Only SELECT/WITH/EXPLAIN statements are allowed. Query timeout is 10 seconds. Not available in live mode (no archive DB). Common tables: blocks, user_commands, internal_commands, public_keys, accounts_accessed. Call get_archive_schema first if you don't know the table layout.

get_archive_schemaA

[infra] Get the archive database table names and their columns. Useful for understanding what data is available for SQL queries.

list_examplesA

[infra] List curated example workflows (each is a sequence of tool calls). Filter by the current server mode by default; pass all to see every workflow regardless of mode.

get_exampleA

[infra] Get the full step list for a single named example workflow. Use list_examples first to discover names.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: status retrieval, SQL querying, schema introspection, and example workflow listing/detail. No overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (get_, query_, list_). This makes the API predictable and easy to navigate.

Tool Count5/5

With 5 tools, the server is well-scoped and each tool earns its place. This is in the ideal range for a focused infrastructure server.

Completeness4/5

The core use case of inspecting node status and querying the archive DB is well covered. Minor gaps exist, such as no direct block/account retrieval tool, but SQL access mitigates this.

Maintenance

ActivityInactive
ResponsivenessResponsive

Resources