stacks-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_accountB | Generate a new Stacks account with private key and basic info |
| get_account_balanceA | Get STX balance and account information for a Stacks address |
| get_transaction_infoB | Get information about a transaction by ID |
| search_transactionsC | Search for transactions by address |
| get_block_infoC | Get information about a specific block |
| get_network_statusC | Get current network status and blockchain information |
| call_read_only_functionA | Call a read-only function on a Stacks smart contract without creating a transaction |
| check_api_statusC | Check API key status and configuration |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| stacks_overview | Get an overview of Stacks blockchain capabilities available through this MCP server |
| getting_started_guide | Get a guide on how to start using Stacks blockchain features |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Stacks Networks | Available Stacks network configurations |
| Testnet Info | Current Stacks testnet information |
| Mainnet Info | Current Stacks mainnet information |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: account generation, balance lookup, transaction info, network status, transaction search, block info, read-only contract calls, and API status. No two tools overlap in what they do, making selection unambiguous.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., generate_account, get_balance, search_transactions). The verbs are varied but consistent in style, and the nouns clearly indicate the resource being acted upon.
With 8 tools, the server is within the ideal 3-15 range. Each tool covers a distinct aspect of Stacks blockchain interaction without being overwhelming or sparse, making the count well-scoped.
The tool set covers core query and read-only operations: accounts, balances, transactions, blocks, network status, and contract reads. However, there is no tool for submitting transactions or write operations, which could be a gap for a full blockchain interaction server, though it may be intended for read-only/query use.