Enables AI agents to interact with the Cookie Chain blockchain for swapping tokens, launching NFTs, managing liquidity, and bridging to Solana.
Also known as cookiechain/cookie-mcp
- Stars
- 4
- Tools
- 1
- Downloads, 30 days
- —
- Latest version
- 0.9.0
- Last commit
- Oct 30, 2026
- License
- MIT
What is cookie MCP?
cookie enables AI agents to interact with the Cookie Chain blockchain for swapping tokens, launching NFTs, managing liquidity, and bridging to Solana. It exposes 1 tool, such as limit.
Summary generated from the project's README
About cookie MCP server
Developers and AI agents can interact with the Cookie Chain blockchain to manage digital assets and execute financial transactions. This server provides tools for reading market data, swapping token pairs through aggregators like Cookiebox Swap API or Candy Shop, and managing liquidity across various venues. It also supports advanced activities such as launching NFT collections on MomoSwap, liquid-staking COOK for bCOOK, and lending or borrowing on Aera.
The server runs locally via stdio and is designed to be non-custodial by signing transactions on your machine using a provided private key. For web-based applications, it can operate in an external-signer mode where the server holds no keys and instead waits for a user to sign transactions through a browser wallet. Users can connect this server to clients like Claude Desktop, Cursor, or Claude Code to perform tasks ranging from simple balance checks to complex bridging between Cookie Chain and Solana via Hyperlane.
What you can do with it
- 1Execute token swapsAn AI agent can compare quotes from different aggregators and perform a token swap.
- 2Manage liquidity positionsUsers can ask an agent to create new pools or add and remove liquidity from existing ones.
- 3Bridge assets to SolanaAn agent can move COOK or SOL between the Cookie Chain and Solana mainnet.
Written from the project's README. Every use case is checked against a quote from it.
How to install cookie MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall cookie MCP in Claude Code
$ claude mcp add --env 'COOKIE_PRIVATE_KEY=<YOUR_COOKIE_PRIVATE_KEY>' cookie-mcp -- npx -y cookie-mcpInstall cookie MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"cookie-mcp": {
"command": "npx",
"args": [
"-y",
"cookie-mcp"
],
"env": {
"COOKIE_PRIVATE_KEY": "<YOUR_COOKIE_PRIVATE_KEY>"
}
}
}
}Install cookie MCP in VS Code
.vscode/mcp.json
{
"servers": {
"cookie-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cookie-mcp"
],
"env": {
"COOKIE_PRIVATE_KEY": "<YOUR_COOKIE_PRIVATE_KEY>"
}
}
}
}Install cookie MCP in VS Code CLI
$ code --add-mcp '{"name":"cookie-mcp","type":"stdio","command":"npx","args":["-y","cookie-mcp"],"env":{"COOKIE_PRIVATE_KEY":"<YOUR_COOKIE_PRIVATE_KEY>"}}'Install cookie MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"cookie-mcp": {
"command": "npx",
"args": [
"-y",
"cookie-mcp"
],
"env": {
"COOKIE_PRIVATE_KEY": "<YOUR_COOKIE_PRIVATE_KEY>"
}
}
}
}Install cookie MCP in Codex
$ codex mcp add cookie-mcp --env 'COOKIE_PRIVATE_KEY=<YOUR_COOKIE_PRIVATE_KEY>' -- npx -y cookie-mcpInstall cookie MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.cookie-mcp] command = "npx" args = ["-y", "cookie-mcp"] [mcp_servers.cookie-mcp.env] COOKIE_PRIVATE_KEY = "<YOUR_COOKIE_PRIVATE_KEY>"
Install cookie MCP in Gemini CLI
$ gemini mcp add -s user -e 'COOKIE_PRIVATE_KEY=<YOUR_COOKIE_PRIVATE_KEY>' cookie-mcp npx -- -y cookie-mcpInstall cookie MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"cookie-mcp": {
"command": "npx",
"args": [
"-y",
"cookie-mcp"
],
"env": {
"COOKIE_PRIVATE_KEY": "<YOUR_COOKIE_PRIVATE_KEY>"
}
}
}
}cookie MCP tools 1
Detected from the READMElimit
| limit | — |
Configuration
COOKIE_PRIVATE_KEYSecretWallet key for money-moving tools (base58 secret, solana-keygen JSON array, or a path to a keypair file). Optional — without it the server runs read-only and money-moving tools return a clear error. The key is used only to sign locally and is redacted from all output.
COOKIE_MAX_TRADE_COOKHard per-transaction spend cap in COOK; money-moving tools refuse inputs valued above it (0 disables). Defaults to 100.
COOKIE_MCP_ALLOWED_HOSTSCOOKIE_RPC_URLCookie Chain RPC endpoint. Defaults to the public Cookiescan RPC (https://rpc.cookiescan.io).
COOKIE_SIGNERCOOKIE_SLIPPAGE_BPSDefault slippage tolerance in basis points (500 = 5%). Defaults to 500.
SOLANA_RPC_URLSolana mainnet RPC endpoint, used only by the bridge tool. Defaults to the public endpoint, which is rate-limited; a dedicated RPC is recommended for reliable bridging.
| Name | Description | |
|---|---|---|
| COOKIE_PRIVATE_KEY | Wallet key for money-moving tools (base58 secret, solana-keygen JSON array, or a path to a keypair file). Optional — without it the server runs read-only and money-moving tools return a clear error. The key is used only to sign locally and is redacted from all output. | Secret |
| COOKIE_MAX_TRADE_COOK | Hard per-transaction spend cap in COOK; money-moving tools refuse inputs valued above it (0 disables). Defaults to 100. | |
| COOKIE_MCP_ALLOWED_HOSTS | — | |
| COOKIE_RPC_URL | Cookie Chain RPC endpoint. Defaults to the public Cookiescan RPC (https://rpc.cookiescan.io). | |
| COOKIE_SIGNER | — | |
| COOKIE_SLIPPAGE_BPS | Default slippage tolerance in basis points (500 = 5%). Defaults to 500. | |
| SOLANA_RPC_URL | Solana mainnet RPC endpoint, used only by the bridge tool. Defaults to the public endpoint, which is rate-limited; a dedicated RPC is recommended for reliable bridging. |
Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHubcookie-mcp
A Model Context Protocol (MCP) server that gives any AI agent onchain tools for the Cookie Chain blockchain — read the market, swap, launch tokens and NFT collections, manage liquidity, stake, trade NFTs, and bridge to Solana.
It runs locally over stdio and signs with your key on your machine, so it is non-custodial by design. For hosted apps (a web chat, a bot behind a website) it runs in external-signer mode: the server holds no key, every action stops at the signing step with a verified transaction, and the user's own browser wallet signs it — same tools, same guardrails (details). It is a community project for the whole Cookie Chain ecosystem.
Contents
- What it can do
- Install — Claude Code · Claude Desktop · Cursor
- Enable trading (add a key)
- Try it
- Configuration
- Tools
- Hosted / wallet-signed mode — for web apps and other integrators
- Client identity · Safety
- Development — Release
What it can do
- Read the market — chain health, pools, token info, token search, swap quotes, and wallet balances. No key needed.
- Swap any Cookie Chain token pair through either aggregator — the
Cookiebox Swap API or Candy Shop —
both routing across all Cookie Chain DEX liquidity. Agents pick per call with the
aggregatorparameter and can quote both to compare.chain: "solana"buys/sells the bridged COOK on Solana mainnet via Jupiter instead. - Transfer COOK or any SPL / Token-2022 token.
- Rest limit and stop orders in the Cookiebox limit-order escrow — take-profit at a price or better, or a stop-loss that sells at market once the rate falls to a trigger — filled by a keeper across every routable Cookie Chain market.
- Launch tokens on the MomoSwap launchpad — create a token on a COOK bonding curve, buy / sell the curve, claim after graduation, and sweep your creator fees.
- Launch and mint NFT collections on the MomoSwap NFT launchpad — launch a fixed-supply drop from a folder of images, mint items off its COOK bonding curve, sell them back while it is live, redeem the floor after graduation, and claim a creator's proceeds.
- Manage liquidity — create pools, add / remove liquidity, claim fees, and permanently lock positions across Cookiebox DAMM v2, Cookiebox CLMM, and CookieSwap BAMM (venue auto-detected).
- Liquid-stake COOK for bCOOK and redeem it instantly.
- Lend and borrow on Aera — supply COOK to earn interest, or lock bCOOK as collateral and borrow COOK against it, with health-factor guards before anything is signed.
- Trade NFTs on Baked Bazaar — search, browse, buy, list, and make / accept offers (Cookie Chain's Metaplex Auction House marketplace).
- Bridge COOK, SOL — and any token added to the bridge later — 1:1 between Cookie Chain and Solana mainnet over Hyperlane.
- Own a name — register, transfer, and resolve
.cooknames on the CookOven name service, and use them anywhere an address is expected (transfer to: "bot.cook").
Safe by default: read-only until you add a key, and every money-moving action is simulated before it is sent.
Install
Requires Node ≥ 22. There is nothing to install or build — npx fetches the published package on
first run. Pick your client below. All three use the same server; the only difference is where the
config lives.
Claude Code
The quickest way — one command, available in every project:
claude mcp add --scope user --transport stdio cookie-mcp -- npx -y cookie-mcp
This registers the server read-only (no key). See Enable trading to add a wallet.
Scopes — claude mcp add writes to one of three places; choose with --scope:
--scope |
Available in | Stored in |
|---|---|---|
user |
all your projects | ~/.claude.json |
(omitted) local |
the current project dir | ~/.claude.json (per-folder) |
project |
anyone who clones a repo | .mcp.json at the repo root |
Use --scope project only when you want the server committed into a specific repo — it writes a
.mcp.json that teammates must approve on first use. For a general-purpose tool like this, --scope user is the right default.
Verify it registered:
claude mcp list # all servers
claude mcp get cookie-mcp # this one's details
# or run /mcp inside a Claude Code session
Claude Desktop
Edit the config file (create it if missing), then restart Claude Desktop:
- macOS —
~/Library/Application Support/Claude/claude_desktop_config.json - Windows —
%APPDATA%\Claude\claude_desktop_config.json
Add the server block below under mcpServers.
Cursor
Edit ~/.cursor/mcp.json (applies everywhere) or .cursor/mcp.json in a project (project wins if
both exist), then add the server block.
Server block
Claude Desktop, Cursor, and a Claude Code .mcp.json all use the identical shape:
{
"mcpServers": {
"cookie-mcp": {
"type": "stdio",
"command": "npx",
"args": ["-y", "cookie-mcp"],
"env": {
"COOKIE_RPC_URL": "https://rpc.cookiescan.io",
"COOKIE_PRIVATE_KEY": ""
}
}
}
}
Enable trading (add a key)
Reads work with no key. To let the agent swap, transfer, launch, stake, LP, buy NFTs, or bridge,
provide a wallet via COOKIE_PRIVATE_KEY — a base58 secret, a solana-keygen JSON byte array, or a
path to a keypair file.
-
Config-file clients (Desktop / Cursor /
.mcp.json): put it in theenvblock above. -
Claude Code: re-run the add with
--env(note: this is saved to~/.claude.json; avoid leaving the raw secret in your shell history):claude mcp add --scope user --transport stdio cookie-mcp \ --env COOKIE_RPC_URL=https://rpc.cookiescan.io \ --env COOKIE_PRIVATE_KEY=<your-key-or-path> \ -- npx -y cookie-mcp
Your key never leaves your machine, is used only to sign locally, and is redacted from all output. Every money-moving action is simulated before it is sent. A transaction that a venue API built (a swap, any launchpad action) is also held to what you asked for: if its simulation would take more than the requested amount plus fees, touch another token you hold, hand one of your token accounts or a delegate to someone else, or deliver less than the quoted minimum, it is refused unsigned.
Try it
Once it's registered, just talk to your agent naturally:
- "What's the health of Cookie Chain right now?" →
chain_health - "Find the cookhouse token and show me its price and liquidity." →
search_tokens→get_token_info - "Quote swapping 10 COOK for bCOOK." →
get_quote - "Swap 10 COOK for bCOOK." →
get_quote→trade(needs a key; simulated first) - Token-2022 transfer-hook tokens (issuer code runs on every transfer and can reject it):
get_quotealways returnswarnings[]andtradereturnsrouteWarnings[]— one entry per hooked mint withreviewed,title,detail. Readdetailbefore trading.transferhandles hooked mints;add_liquidity/create_poolon Cookiebox CLMM split the open+deposit tx when a hooked mint would overflow it, andcreate_poolrefuses up front when the mint still needs a Cookiebox TokenBadge. - "What COOKHOUSE NFTs are listed, and buy the cheapest under 50 COOK." →
search_nfts→buy_nft - "Which wallet are you about to trade from?" →
get_wallet
The agent resolves names to mint addresses with search_tokens / search_nfts, then acts on the mint —
it never turns a name straight into a trade.
Configuration
| Variable | Default | Purpose |
|---|---|---|
COOKIE_RPC_URL |
https://rpc.cookiescan.io |
Cookie Chain RPC. |
COOKIE_PRIVATE_KEY |
— | Wallet key for money-moving tools. Read-only if unset. |
COOKIE_SIGNER |
local |
external = no key in the process; tools return needs_signature for the user's wallet to sign. |
COOKIE_WALLET_ADDRESS |
— | External mode: default wallet when a request carries no x-cookie-wallet header. |
COOKIE_MCP_HTTP_PORT / _HOST / _PATH |
— / 127.0.0.1 / /mcp |
Serve Streamable HTTP instead of stdio (same as --http [port]). |
COOKIE_MCP_CORS_ORIGIN |
*, or none with a local key |
Comma-separated browser origins allowed to call the HTTP server (* = any). |
COOKIE_MCP_HTTP_TOKEN |
— | Bearer token every HTTP MCP request must send. Required with a local key over HTTP. |
COOKIE_MCP_ALLOWED_HOSTS |
loopback names on a loopback bind | Comma-separated Host values the HTTP server answers to (blocks DNS rebinding). |
COOKIE_IMAGE_DIR |
home directory | The only folder deploy_token.imagePath and create_nft_drop's art may read from (stdio only). |
COOKIE_SLIPPAGE_BPS |
500 |
Default slippage (bps). |
COOKIE_REFERRER |
mcp treasury |
Referral wallet (MomoSwap only). |
COOKIE_APP_ID |
— | Name of your app, sent to the venues in User-Agent (see Client identity). |
SOLANA_RPC_URL |
https://api.mainnet-beta.solana.com |
Solana RPC. |
JUPITER_API_KEY |
— | Optional; else keyless Jupiter at 0.5 req/s. |
cookie MCP questions
How do I add cookie MCP to Claude Code?
Run claude mcp add --env 'COOKIE_PRIVATE_KEY=<YOUR_COOKIE_PRIVATE_KEY>' cookie-mcp -- npx -y cookie-mcp in your terminal. Add --scope user to make it available in every project.
How do I add cookie MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does cookie MCP provide?
It exposes 1 tool, including limit.
Can I use this for a web-based AI bot?
Yes, for hosted applications you can use external-signer mode where the server holds no key and the user signs transactions via their browser wallet.
Do I need a private key to read market data?
No, you can read market health, pools, and token information without providing a key.