Chainstack

What Chainstack MCP server does

The Chainstack MCP server exposes Chainstack platform functions to MCP-compatible AI agents. It supports two broad workflows: finding information about Chainstack and operating resources in a Chainstack organization.

For information tasks, agents can search the Chainstack documentation, retrieve complete documentation pages, check platform incidents, send a message to Chainstack, and read a live pricing snapshot. The pricing response includes plan tiers, feature comparisons, add-ons, and a catalog of dedicated nodes by chain.

For account and infrastructure tasks, the Chainstack MCP server can inspect the current organization, list and manage projects, and list, inspect, create, update, or delete blockchain nodes. It can also return deployment options. The faucet operation requests testnet funds for supported addresses across 12 EVM, Solana, and TON networks.

How it works

The service is hosted at mcp.chainstack.com and can be registered as a remote MCP server over HTTP. A client can begin onboarding by fetching mcp.chainstack.com, or use the MCP endpoint at https://mcp.chainstack.com/mcp when adding the server directly.

Tools that search documentation, retrieve pages, report platform status, send contact messages, and return pricing do not need an API key. Organization, project, node, and testnet-faucet operations do require a Chainstack API key. The README directs users to create that key in the Chainstack console.

The repository also includes a reusable skill that can be installed with the skills CLI. This provides an alternative to registering the remote endpoint directly and is intended for supported agent environments.

Setup and configuration

One setup path is to install the bundled skill:

npx skills add chainstacklabs/mcp-server

Another is to register the hosted endpoint with an MCP client. For example, the README gives this Claude Code command:

claude mcp add --transport http chainstack https://mcp.chainstack.com/mcp -s user

VS Code can install the server from the GitHub MCP Registry by searching for @mcp chainstack in Extensions, or by using the registry entry. The README states that this installation path does not require an API key for unauthenticated tools. For authenticated operations, configure the API key through the client’s MCP setup according to the full setup guide; no environment variable names are specified in the provided material.

Tools and capabilities

The Chainstack MCP server includes these unauthenticated tools:

• search_docs searches Chainstack documentation.
• get_doc_page retrieves the full content of a documentation page.
• get_platform_status checks platform status and incidents.
• contact_chainstack sends sales, support, or general messages to Chainstack.
• get_chainstack_pricing returns current plan, feature, add-on, and dedicated-node pricing information.

With an API key, it also provides organization lookup; project listing, creation, retrieval, updates, and deletion; node listing, retrieval, creation, updates, and deletion; deployment-option lookup; and request_testnet_funds for supported testnet addresses.

The README identifies the service in both the GitHub MCP Registry and the official MCP Registry as com.chainstack/chainstack. Its registry entry is the appropriate place to check the published version.

Limitations and notes

The provided material does not specify the exact API-key configuration field, supported node types beyond the deployment-options tool, or detailed limits for each faucet network. Testnet funding is limited to the 12 networks supported by the faucet, spanning EVM, Solana, and TON. Contact messages are described as covering sales, support, or general questions, but no response-time or delivery guarantees are given.