Cookie MCP

cookie-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 aggregator parameter 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 .cook names 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:

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 the env block 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= \ -- 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_quote always returns warnings[] and trade returns routeWarnings[] — one entry per hooked mint with reviewed, title, detail. Read detail before trading. transfer handles hooked mints; add_liquidity/create_pool on Cookiebox CLMM split the open+deposit tx when a hooked mint would overflow it, and create_pool refuses 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

| COOKIE_APP_ID | — | Name of your app, sent to the venues in User-Agent (see [Client identit