Skip to main content
Glama
Sign In
stacks-mcp-server

stacks-mcp-server

by aibtcdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

This repository has been archived. Development has moved to aibtc-mcp-server.

Stacks MCP Server

A Model Context Protocol (MCP) server that provides Stacks blockchain functionality for AI assistants like Claude.

Tools

Account Management

  • generate_account - Generate a new Stacks account with private key

  • get_account_balance - Check STX balance for any Stacks address

Blockchain Information

  • get_network_status - Get current network status and info

  • get_block_info - Get block details by height or hash

  • get_transaction_info - Get transaction details by ID

  • search_transactions - Search transactions by address

Configuration

  • check_api_status - Check API key status and rate limits

Related MCP server: MIDL MCP Server

Quick Start

Using with Claude Desktop

Add to your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: `%APPDATA%\Claude

Available Tools

8 tools
call_read_only_functionA

Call a read-only function on a Stacks smart contract without creating a transaction

Inputs: contractName (required), functionName (required), contractAddress (required), sender, +2 more.

check_api_statusC

Check API key status and configuration

Inputs: include_limits.

generate_accountB

Generate a new Stacks account with private key and basic info

Inputs: network.

get_account_balanceA

Get STX balance and account information for a Stacks address

Inputs: address (required), network.

get_block_infoC

Get information about a specific block

Inputs: blockId (required), network.

get_network_statusC

Get current network status and blockchain information

Inputs: network.

get_transaction_infoB

Get information about a transaction by ID

Inputs: txId (required), network.

search_transactionsC

Search for transactions by address

Inputs: address (required), limit, network.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

    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

    A3.6/5.0

    Scored across 8 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers