Chainstack
MCP server by Chainstack
Deploy and manage blockchain nodes across 70+ protocols, search Chainstack docs, check status and pricing, and request testnet funds.
Connect to Chainstack
Chainstack needs an API key. Connect with its own URL and your key:
Send your key in the Authorization header. mcp.tc never sees or stores keys. Where to get a key
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/chainstackAbout
Connects an assistant to the Chainstack platform. You can list projects and nodes, create and delete them, look up valid blockchain and cloud deployment options, search the protocol and RPC documentation, check platform status, read live pricing, request testnet faucet funds, and send a message to the Chainstack team.
It runs as a hosted streamable HTTP endpoint at https://mcp.chainstack.com/mcp. Docs search, page fetch, platform status, pricing and contact tools work without a key. Node, project and faucet tools need a Chainstack API key sent as an Authorization Bearer header.
What you can do
- Deploy, rename and delete blockchain nodes
- Create, update and delete projects that hold nodes
- List valid blockchain, cloud and region options before deploying
- Search Chainstack docs and fetch full pages
- Check platform status, incidents and maintenances
- Fetch live pricing for plans, add-ons and dedicated nodes
- Top up testnet addresses from the Chainstack faucet
- Send a message to Chainstack sales and support
Tools 23
get_organizationRead-onlyGet organization name and ID.
get_deployment_optionsRead-onlyList blockchain, cloud and network combinations valid for node deployment.
list_projectsRead-onlyList all projects, which are containers for nodes.
create_projectWritesCreate a new project with a name and optional description.
list_nodesRead-onlyList nodes with status and endpoints, optionally filtered by project.
get_nodeRead-onlyGet a node's full details including endpoints and cloud info.
create_nodeWritesDeploy a new blockchain node in a project on a chosen blockchain and cloud.
get_projectRead-onlyGet details of a project.
update_projectCan deleteUpdate a project's name or description.
delete_projectCan deleteDelete a project (irreversible).
update_nodeCan deleteRename a node.
delete_nodeCan deleteDelete a node (irreversible).
Show 11 more tools
list_node_access_rulesRead-onlyList node access rules
create_node_access_ruleCan deleteCreate node access rule
update_node_access_ruleCan deleteUpdate node access rule
delete_node_access_ruleCan deleteDelete node access rule
set_node_access_rules_statusCan deleteActivate or deactivate all node access rules
search_docsRead-onlySearch Chainstack docs for RPC methods, node setup and code examples.
get_doc_pageRead-onlyFetch the full content of a Chainstack documentation page.
get_platform_statusRead-onlyCheck platform status, active incidents and maintenances.
contact_chainstackCan deleteSubmit a message to Chainstack's sales and support team after user confirmation.
request_testnet_fundsCan deleteTop up a testnet address from the Chainstack faucet to the per-network cap.
get_chainstack_pricingRead-onlyReturn a live snapshot of plan tiers, add-ons and dedicated-node pricing.
Read from the live server on 17 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.
Example prompts
Deploy an Ethereum node in my default project
Search the Chainstack docs for supported eth_call parameters
Is there any active incident on the Chainstack platform?
Top up my Sepolia address with testnet ETH
Set up
Every client connects to mcp.chainstack.com. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http chainstack https://mcp.chainstack.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"- Replace the placeholder with your key before you run it, then check it with
/mcpinside Claude Code.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Use the
mcp-remotebridge, which keeps the key on this computer (a connector added on claude.ai with the key under Request headers also shows up here). Open Settings → Developer → Edit Config and add:
{
"mcpServers": {
"chainstack": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.chainstack.com/mcp",
"--header",
"Authorization: Bearer <YOUR_API_KEY>"
]
}
}
}- Replace the placeholder with your key and restart Claude Desktop.
The bridge needs Node.js on your computer.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://mcp.chainstack.com/mcp. Under Request headers, addAuthorization: Bearer <YOUR_API_KEY>with your key from Chainstack, then click Add. - Turn it on in a chat from the tools menu.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"chainstack": {
"url": "https://mcp.chainstack.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}VS Code
Add it to .vscode/mcp.json. VS Code asks for the key the first time and stores it securely:
{
"servers": {
"chainstack": {
"type": "http",
"url": "https://mcp.chainstack.com/mcp",
"headers": {
"Authorization": "Bearer ${input:api-key}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "api-key",
"description": "API key",
"password": true
}
]
}Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"chainstack": {
"serverUrl": "https://mcp.chainstack.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}- Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add chainstack --url https://mcp.chainstack.com/mcp --bearer-token-env-var CHAINSTACK_API_KEYOr edit ~/.codex/config.toml directly:
[mcp_servers.chainstack]
url = "https://mcp.chainstack.com/mcp"
bearer_token_env_var = "CHAINSTACK_API_KEY"Set CHAINSTACK_API_KEY to your key in the shell that runs Codex.
Gemini CLI
gemini mcp add --transport http --header "Authorization: Bearer <YOUR_API_KEY>" chainstack https://mcp.chainstack.com/mcpThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"chainstack": {
"type": "http",
"url": "https://mcp.chainstack.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://mcp.chainstack.com/mcp.
Embed
Show Chainstack in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/chainstack)<a href="https://mcp.tc/i/chainstack"><img src="https://mcp.tc/i/chainstack/badge.svg" alt="Chainstack on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/chainstack.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/chainstack" title="Chainstack on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/chainstack.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Chainstack card to your site.
Add the mcp.tc card for Chainstack, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/chainstack.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="chainstack"><a href="https://mcp.tc/i/chainstack">Chainstack on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/chainstack)
```
Reference: https://mcp.tc/embedChange history
We read this server’s tool list every 3 hours and record what changes. Last read 18 Nov 2026, 05:34 UTC.
-
New version 1.12.0 (was 1.11.4). Reported by the server.
-
2 tools changed. Server instructions changed.
New server instructions
Details, 26 Oct 2026, 11:38 UTC
Changed 2
create_nodedescription and input schemaBeforeDeploy a new blockchain node. Call get_deployment_options first for valid IDs.
Trader nodes are region-bound (e.g., London, Ashburn, Singapore). Always confirm the region with the user before deploying — region cannot be changed after deployment.AfterDeploy a new blockchain node. Call get_deployment_options first for valid IDs. Use a Global option (node_tier "Global") from get_deployment_options.
- Description of
cloudBeforeCloud ID from get_deployment_options (e.g.,
CC-0016 for Global; Trader IDs vary by region).AfterCloud ID of a Global option from get_deployment_options (e.g., CC-0016).
- Description of
get_doc_pageinput schema- Description of
pageBeforePage path from search results — pass the `page` field from a search_docs result (e.g.,
"docs/ethereum-trader-nodes").The leading slash, the `.mdx` extension, and the docs.chainstack.com URL prefixa…AfterPage path from search results — pass the `page` field from a search_docs result (e.g., "docs/ethereum-tooling"). The leading slash, the `.mdx` extension, and the docs.chainstack.com URL prefix are al…
- Description of
Server instructions
BeforeChainstack MCP server — deploy and manage blockchain nodes, search protocol docs and RPC references, check platform status, get pricing, request testnet funds, and contact the Chainstack team. Key behaviors: - If the user needs a node, DEPLOY IT with create_node. Never send them to the console — they're using MCP to stay in their IDE. - For a protocol's features or RPC methods, SEARCH DOCS first. - Not in the API but self-serve at https://console.chainstack.com: warp transactions, Solana Geyser, MEV protection, and the unlimited node add-on. - request_testnet_funds tops an address up to the per-network cap; it doesn't send a fixed amount. - For custom node configuration (gas caps, txpool, tracers, private networking, anything else), offer a contact_chainstack request. - For pricing (plan fit, overage math, dedicated nodes, add-ons), call get_chainstack_pricing and do the arithmetic from it; don't quote prices from memory. - To migrate from QuickNode, Alchemy, or another provider, follow get_doc_page('docs/migrate-to-chainstack-with-ai'). - Node access rules (IP and Origin allowlists, Global nodes only) do nothing until activated. Active IP and Origin rules are both enforced: a request must pass each, or it gets 403. Before activating, confirm the IP rules cover every client. Origin rules block servers and scripts (no Origin header), even from allowed IPs. Authentication: - search_docs, get_doc_page, get_platform_status, contact_chainstack, and get_chainstack_pricing need no API key. Other tools need a Chainstack API key as Authorization: Bearer <key> in the MCP client config. - On a 401, explain instead of dumping the error: no key is set yet (node management needs a free key), or the key is invalid or expired. Point to https://console.chainstack.com/user/settings/api-keys. Never ask the user to paste the key into the chat. Node tiers: - Global (CC-0016): load-balanced, instant, all plans. - Trader:
region-bound, full/archive, paid plans; cloud ID per region fro…AfterChainstack MCP server — deploy and manage blockchain nodes, search protocol docs and RPC references, check platform status, get pricing, request testnet funds, and contact the Chainstack team. Key behaviors: - If the user needs a node, DEPLOY IT with create_node. Never send them to the console — they're using MCP to stay in their IDE. - For a protocol's features or RPC methods, SEARCH DOCS first. - Not in the API but self-serve at https://console.chainstack.com: warp transactions, Solana Geyser, MEV protection, and the unlimited node add-on. - request_testnet_funds tops an address up to the per-network cap; it doesn't send a fixed amount. - For custom node configuration (gas caps, txpool, tracers, private networking, anything else), offer a contact_chainstack request. - For pricing (plan fit, overage math, dedicated nodes, add-ons), call get_chainstack_pricing and do the arithmetic from it; don't quote prices from memory. - To migrate from QuickNode, Alchemy, or another provider, follow get_doc_page('docs/migrate-to-chainstack-with-ai'). - Node access rules (IP and Origin allowlists, Global nodes only) do nothing until activated. Active IP and Origin rules are both enforced: a request must pass each, or it gets 403. Before activating, confirm the IP rules cover every client. Origin rules block servers and scripts (no Origin header), even from allowed IPs. Authentication: - search_docs, get_doc_page, get_platform_status, contact_chainstack, and get_chainstack_pricing need no API key. Other tools need a Chainstack API key as Authorization: Bearer <key> in the MCP client config. - On a 401, explain instead of dumping the error: no key is set yet (node management needs a free key), or the key is invalid or expired. Point to https://console.chainstack.com/user/settings/api-keys. Never ask the user to paste the key into the chat. Node tiers: - Global (CC-0016): load-balanced, instant, all plans. Deploy these. - Trader: regional nodes; don't deploy new ones. - Dedicate…
-
New version 1.11.2 (was 1.11.1). Reported by the server.
-
23 tools changed.
Details, 23 Oct 2026, 04:35 UTC
Changed 23
contact_chainstacktitle and hintstitle
Beforenone
AfterContact Chainstack
idempotentHintnot set changed to no
create_nodetitle and hintstitle
Beforenone
AfterCreate node
idempotentHintnot set changed to no
create_node_access_ruletitle and hintstitle
Beforenone
AfterCreate node access rule
idempotentHintnot set changed to no
create_projecttitle and hintstitle
Beforenone
AfterCreate project
idempotentHintnot set changed to no
delete_nodetitle and hintstitle
Beforenone
AfterDelete node
idempotentHintnot set changed to yes
delete_node_access_ruletitle and hintstitle
Beforenone
AfterDelete node access rule
idempotentHintnot set changed to yes
delete_projecttitle and hintstitle
Beforenone
AfterDelete project
idempotentHintnot set changed to yes
get_chainstack_pricingtitle and hintstitle
Beforenone
AfterGet Chainstack pricing
openWorldHintyes changed to noidempotentHintnot set changed to yes
get_deployment_optionstitle and hintstitle
Beforenone
AfterGet deployment options
openWorldHintyes changed to noidempotentHintnot set changed to yes
get_doc_pagetitle and hintstitle
Beforenone
AfterGet docs page
openWorldHintyes changed to noidempotentHintnot set changed to yes
get_nodeget_organizationget_platform_statusget_projectlist_node_access_ruleslist_nodeslist_projectsrequest_testnet_fundssearch_docsset_node_access_rules_statusupdate_nodeupdate_node_access_ruleupdate_project -
New version 1.11.1 (was 1.11.0). Reported by the server.
-
3 tools changed. Server instructions changed.
New server instructions
Details, 12 Oct 2026, 13:33 UTC
Changed 3
create_nodeinput schema- Description of
cloudBeforeCloud ID from get_deployment_options (e.g., CC-0016 for
Global, CC-0020 for London).AfterCloud ID from get_deployment_options (e.g., CC-0016 for Global; Trader IDs vary by region).
- Description of
get_deployment_optionsoutput schemarequest_testnet_fundsdescription and output schemaBeforeTop up a testnet address from Chainstack's faucet. The faucet does not send a fixed amount — it tops the address up to the per-network maximum (e.g. 0.5 ETH for sepolia). If the address already sits above the cap, the call fails with an insufficient-balance error. Describe the behavior to the user as "top up" not "give", and surface the returned `amountSent` so they see the actual delta.
AfterTop up a testnet address from Chainstack's faucet. The faucet does not send a fixed amount — it tops the address up to the per-network maximum (e.g. 0.5 ETH for sepolia). If the address already sits above the cap, the call fails with an insufficient-balance error. Describe the behavior to the user as "top up" not "give", and surface the returned `amountSent` so they see the actual delta. One top-up per network every 24 hours: a repeat call for the same network is refused (429) if the same organization or the same address got funds there in the last 24 hours, and the error says when the next top-up is available. Other networks have separate cooldowns. A success is final even if the balance hasn't updated yet; track the returned `transaction` instead of calling again.
Server instructions
BeforeChainstack MCP server — deploy and manage blockchain nodes, search protocol docs and RPC references, check platform status, get pricing, request testnet funds, and contact the Chainstack team. Key behaviors: - If the user needs a node, DEPLOY IT with create_node. Never send them to the console — they're using MCP to stay in their IDE. - For a protocol's features or RPC methods, SEARCH DOCS first. - Not in the API but self-serve at https://console.chainstack.com: warp transactions, Solana Geyser, MEV protection, and the unlimited node add-on. - request_testnet_funds tops an address up to the per-network cap; it doesn't send a fixed amount. - For custom node configuration (gas caps, txpool, tracers, private networking, anything else), offer a contact_chainstack request. - For pricing (plan fit, overage math, dedicated nodes, add-ons), call get_chainstack_pricing and do the arithmetic from it; don't quote prices from memory. - To migrate from QuickNode, Alchemy, or another provider, follow get_doc_page('docs/migrate-to-chainstack-with-ai'). - Node access rules (IP and Origin allowlists, Global nodes only) do nothing until activated. Active IP and Origin rules are both enforced: a request must pass each, or it gets 403. Before activating, confirm the IP rules cover every client. Origin rules block servers and scripts (no Origin header), even from allowed IPs. Authentication: - search_docs, get_doc_page, get_platform_status, contact_chainstack, and get_chainstack_pricing need no API key. Other tools need a Chainstack API key as Authorization: Bearer <key> in the MCP client config. - On a 401, explain instead of dumping the error: no key is set yet (node management needs a free key), or the key is invalid or expired. Point to https://console.chainstack.com/user/settings/api-keys. Never ask the user to paste the key into the chat. Node tiers: - Global (CC-0016): load-balanced, instant, all plans. -
Trader (CC-0020–0028):region-bound, full/archive, paidplans.AfterChainstack MCP server — deploy and manage blockchain nodes, search protocol docs and RPC references, check platform status, get pricing, request testnet funds, and contact the Chainstack team. Key behaviors: - If the user needs a node, DEPLOY IT with create_node. Never send them to the console — they're using MCP to stay in their IDE. - For a protocol's features or RPC methods, SEARCH DOCS first. - Not in the API but self-serve at https://console.chainstack.com: warp transactions, Solana Geyser, MEV protection, and the unlimited node add-on. - request_testnet_funds tops an address up to the per-network cap; it doesn't send a fixed amount. - For custom node configuration (gas caps, txpool, tracers, private networking, anything else), offer a contact_chainstack request. - For pricing (plan fit, overage math, dedicated nodes, add-ons), call get_chainstack_pricing and do the arithmetic from it; don't quote prices from memory. - To migrate from QuickNode, Alchemy, or another provider, follow get_doc_page('docs/migrate-to-chainstack-with-ai'). - Node access rules (IP and Origin allowlists, Global nodes only) do nothing until activated. Active IP and Origin rules are both enforced: a request must pass each, or it gets 403. Before activating, confirm the IP rules cover every client. Origin rules block servers and scripts (no Origin header), even from allowed IPs. Authentication: - search_docs, get_doc_page, get_platform_status, contact_chainstack, and get_chainstack_pricing need no API key. Other tools need a Chainstack API key as Authorization: Bearer <key> in the MCP client config. - On a 401, explain instead of dumping the error: no key is set yet (node management needs a free key), or the key is invalid or expired. Point to https://console.chainstack.com/user/settings/api-keys. Never ask the user to paste the key into the chat. Node tiers: - Global (CC-0016): load-balanced, instant, all plans. - Trader: region-bound, full/archive, paid plans; cloud ID per region fro…
-
New version 1.11.0 (was 1.10.11). Reported by the server.
-
5 tools added and 2 tools changed. Server instructions changed.
New tool marked destructive, New server instructions
Details, 11 Oct 2026, 07:31 UTC
Added 5
create_node_access_ruleCan deleteAdd an IP or Origin allowlist rule to a Global node. New rules are deactivated and do nothing until activated. Active IP rules limit which client IPs can call the node; active origin rules limit which Origin headers it accepts. With both kinds active, a request must pass both. Everything else gets HTTP 403 within about 10 seconds. Rules don't affect the Chainstack API, so they can always be changed or deactivated with these tools. Before activating, confirm with the user that the IP rules cover every IP that calls the node (servers, CI, their own machine); you can't check this. Origin rules are for browser-only access: once one is active, every request without an Origin header (servers, scripts, curl) is blocked, even from an allowed IP. If an identical rule exists, it is returned instead of a duplicate.
delete_node_access_ruleCan deleteDelete an access rule from a node (irreversible). Deleting an active rule changes who can reach the node; the result says what's enforced afterwards. With no active rules left, the node accepts requests from any IP and origin.
list_node_access_rulesRead-onlyList a node's access rules (IP and Origin allowlists, Global nodes only). With no active rules, the node accepts requests from any IP and origin. If correctly configured rules still return 403, that's a support case: offer contact_chainstack.
set_node_access_rules_statusCan deleteActivate or deactivate every access rule on a node at once. Activating enforces every rule within about 10 seconds: active IP rules limit which IPs can call the node, active origin rules limit which Origin headers it accepts, and a request must pass both kinds. Others get HTTP 403. First confirm with the user that the IP rules cover every IP that calls the node (servers, CI, their own machine); you can't check this. Origin rules block every request without an Origin header (servers, scripts, curl), even from an allowed IP. Deactivating opens the node to any IP and origin.
update_node_access_ruleCan deleteChange an access rule's value, or activate or deactivate it. A rule's type can't change; delete it and create a new one. Before activating, confirm with the user that the IP rules cover every IP that calls the node. Activating the first origin rule blocks every request without an Origin header (servers, scripts, curl), even from allowed IPs. Changing or deactivating a rule can block clients that only it allowed.
Changed 2
contact_chainstackdescriptionBeforeSubmit a message to Chainstack's sales and support team. Use when the user wants to ask about pricing, get a custom quote, request a plan upgrade, request node customizations (Enterprise), report a problem, or reach Chainstack for any reason. Posts to the same contact form as chainstack.com/contact/. ## Before calling this tool CRITICAL — follow these steps EVERY time: 1. Draft the message based on your conversation context. 2. Show the user the EXACT message, email, and name you will send. 3. If the user has a Chainstack API key configured, tell them: "I'll also include your Chainstack account info (org name and ID) so the team can pull up your account immediately — this means significantly faster handling and a more tailored response." 4. Ask: "Shall I send this to Chainstack? Please confirm there's no sensitive information you'd like removed." 5. Only call this tool after the user explicitly confirms. NEVER include in the message: - API keys, tokens, passwords, private keys, wallet…
AfterSubmit a message to Chainstack's sales and support team. Use when the user wants to ask about pricing, get a custom quote, request a plan upgrade, request node customizations (Enterprise), report a problem, or reach Chainstack for any reason. Posts to the same contact form as chainstack.com/contact/. ## Before calling this tool CRITICAL — follow these steps EVERY time: 1. Draft the message based on your conversation context. 2. Show the user the EXACT message, email, and name you will send. 3. If the user has a Chainstack API key configured, tell them their org name and ID will be included so the team can find their account and reply faster. 4. Ask: "Shall I send this to Chainstack? Please confirm there's no sensitive information you'd like removed." 5. Only call this tool after the user explicitly confirms. NEVER include in the message: - API keys, tokens, passwords, private keys, wallet seeds, mnemonics - RPC endpoint URLs (Chainstack or any other provider) - Wallet addresses, trans…
get_chainstack_pricingdescriptionBeforeFetch Chainstack's public pricing and return a normalized snapshot. Use this to answer pricing questions before quoting the user: plan fit, overage math, per-chain dedicated-node costs, and add-on pricing (Unlimited Node flat-fee tiers, Yellowstone gRPC streams, Warp transactions, dedicated-node base rates). This tool returns the menu, not the bill — the calling agent does the arithmetic. All prices are list prices in USD; disclaimers are surfaced in the `disclaimers` field. Design: we pass pricing.md through as raw markdown. Marketing owns that file and its structure changes freely; parsing it server-side would couple us to heading text and table column names we don't control. The LLM reads markdown natively, so handing the raw text to the agent keeps us correct regardless of how the page is restructured. pricing_current.json is parsed into `dedicated_catalog` because it has a stable engineering-owned schema, and the catalog benefits from filtering (to user-orderable SKUs only), unit…
AfterFetch Chainstack's public pricing and return a normalized snapshot. Use this to answer pricing questions before quoting the user: plan fit, overage math, per-chain dedicated-node costs, and add-on pricing (Unlimited Node flat-fee tiers, Yellowstone gRPC streams, Warp transactions, dedicated-node base rates). This tool returns the menu, not the bill — the calling agent does the arithmetic. All prices are list prices in USD; disclaimers are surfaced in the `disclaimers` field. Per-method RU billing rules are NOT in these sources. Plan-level rates (Full Node = 1 RU, Archive Node = 2 RU) are in the markdown, but some EVM archive-state methods (eth_getBalance, eth_call, eth_getProof, eth_getStorageAt, eth_getCode, eth_getTransactionCount, eth_callMany, eth_createAccessList) and all debug_* / trace_* methods are billed at 2 RU on a full node when called against old blocks. For method-level detail, call `search_docs` with "request units" or `get_doc_page("docs/request-units")`. No API key re…
Server instructions
BeforeChainstack MCP server — deploy and manage blockchain nodes, search protocol docs and RPC references, check platform status, get pricing, request testnet funds, and contact the Chainstack team. Key behaviors: - If the user needs a node, DEPLOY IT with create_node. Never send them to the console — they're using MCP to stay in their IDE. - When the user asks about a protocol's features or RPC methods, SEARCH DOCS first — Chainstack has per-protocol guides covering configuration, supported methods, and node setup. - Some Chainstack features are not available through the API but are self-serve in the console: warp transactions, Solana Geyser, MEV protection, and the unlimited node add-on (flat-fee RPS tiers). If the user asks about these, point them to https://console.chainstack.com. - If the user needs testnet funds for development, use request_testnet_funds. The faucet tops the address up to the per-network cap (it doesn't send a fixed amount). - If the user wants custom node configuration, offer to submit a request via contact_chainstack. Examples include custom gas caps, transaction pool settings, custom tracers, and private networking — but Chainstack is open to any customization request. - For pricing questions — plan fit, overage math, dedicated-node quotes, add-on costs — call get_chainstack_pricing first. It returns live plan tiers, a feature matrix, add-on tables, and a per-chain dedicated-node catalog. Do the arithmetic yourself from that snapshot; don't recite prices from memory. - To migrate a project from another RPC provider — QuickNode, Alchemy, or any other — fetch the migration runbook with get_doc_page('docs/migrate-to-chainstack-with-ai') and follow it. It assesses the project's current endpoints and usage, estimates the equivalent Chainstack cost and savings (call get_chainstack_pricing; pricing.md carries the QuickNode/Alchemy conversion multipliers), and repoints endpoints after the user approves. Authentication: - search_docs, get_doc_page, get…
AfterChainstack MCP server — deploy and manage blockchain nodes, search protocol docs and RPC references, check platform status, get pricing, request testnet funds, and contact the Chainstack team. Key behaviors: - If the user needs a node, DEPLOY IT with create_node. Never send them to the console — they're using MCP to stay in their IDE. - For a protocol's features or RPC methods, SEARCH DOCS first. - Not in the API but self-serve at https://console.chainstack.com: warp transactions, Solana Geyser, MEV protection, and the unlimited node add-on. - request_testnet_funds tops an address up to the per-network cap; it doesn't send a fixed amount. - For custom node configuration (gas caps, txpool, tracers, private networking, anything else), offer a contact_chainstack request. - For pricing (plan fit, overage math, dedicated nodes, add-ons), call get_chainstack_pricing and do the arithmetic from it; don't quote prices from memory. - To migrate from QuickNode, Alchemy, or another provider, follow get_doc_page('docs/migrate-to-chainstack-with-ai'). - Node access rules (IP and Origin allowlists, Global nodes only) do nothing until activated. Active IP and Origin rules are both enforced: a request must pass each, or it gets 403. Before activating, confirm the IP rules cover every client. Origin rules block servers and scripts (no Origin header), even from allowed IPs. Authentication: - search_docs, get_doc_page, get_platform_status, contact_chainstack, and get_chainstack_pricing need no API key. Other tools need a Chainstack API key as Authorization: Bearer <key> in the MCP client config. - On a 401, explain instead of dumping the error: no key is set yet (node management needs a free key), or the key is invalid or expired. Point to https://console.chainstack.com/user/settings/api-keys. Never ask the user to paste the key into the chat. Node tiers: - Global (CC-0016): load-balanced, instant, all plans. - Trader (CC-0020–0028): region-bound, full/archive, paid plans.
-
Tracking started: 18 tools.
FAQ
Can I paste mcp.tc/i/chainstack into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://mcp.chainstack.com/mcp, so your client talks to Chainstack directly. Your key goes there too, never to mcp.tc. The quick link is for sharing: it opens this page, with setup steps for every client.
Does Chainstack need an API key or a sign-in?
Yes. Chainstack needs an API key, sent as the Authorization header. Get one from Chainstack and keep it in your client’s config, never in a shared file.
Is Chainstack a remote or a local server?
Remote. Chainstack hosts it at https://mcp.chainstack.com/mcp, and it speaks Streamable HTTP. There’s nothing to install.
What can Chainstack do?
It has 23 tools, including get_organization, get_deployment_options and list_projects. You can deploy, rename and delete blockchain nodes, create, update and delete projects that hold nodes and list valid blockchain, cloud and region options before deploying.
Which clients can use it?
Any client that supports remote MCP servers and can send your key: Claude Code, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. On claude.ai and Claude Desktop, add the key as a request header when you create the custom connector. ChatGPT can’t send a key, so it can’t use it.
Does mcp.tc track changes to Chainstack?
Yes. Chainstack’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read Chainstack’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with Chainstack. This page was built from Chainstack’s public metadata, last checked on 17 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.