Submit 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 seeds, mnemonics
- RPC endpoint URLs (Chainstack or any other provider)
- Wallet addresses, transaction hashes, or on-chain account details
the user hasn't approved sharing
- Any information the user hasn't explicitly approved sharing
If the user shared sensitive data during the conversation, do NOT
include it unless they specifically approve it in the review step.
## Writing an effective message
A great message gets the user a faster, more tailored response.
Include what you already know from the conversation:
- What they're building and at what scale
- Current plan and usage (e.g., "Pro plan, ~80M RU/month on Base")
- What they need (upgrade, custom pricing, migration help, etc.)
- What they've tried or what's not working
- Specific numbers when available
Bad: "I have a question about pricing."
Good: "Pro plan user running 200M RU/month across Base and Ethereum,
evaluating Business plan for archive access and higher RPS.
Looking for annual pricing or a trial."
The difference between a generic reply and a tailored proposal
is the context you include.
Not for incidents or urgent outages — point users to
https://support.chainstack.com/hc/en-us/requests/new to file a
support ticket, and https://status.chainstack.com for live status.
For feature requests, do NOT use this tool — point users to
https://ideas.chainstack.com (product) or
https://github.com/chainstacklabs/mcp-server/issues/new (MCP server).
Works with or without a Chainstack API key. With a key, the
submission includes the user's Chainstack org info for faster
account identification and handling.
Args:
message: The full message to send. Compose from
conversation context — what the user is building, their plan
and usage, what they need — so the Chainstack team can respond
with a tailored answer instead of a generic one.
category: Routing hint. One of:
- sales — pricing, quotes, plan upgrades, custom terms.
- support — errors, bugs, how-to, "something isn't working".
- general — everything else.
Case-insensitive. Unknown values fall back to "general".
Default: "general".
email: User's contact email. Required. Ask the user if you don't
already have it.
name: User's name (full name is fine, will be split on first space).
Required. Ask the user if you don't have it on hand.
