Cookie MCP Server

Cookie Chain tools for AI agents: swap, launch, liquidity, staking, NFTs, and a Solana bridge.

Remote serverstreamable-http

What is the Cookie MCP server?

Connect Cookie to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Cookie Chain tools for AI agents: swap, launch, liquidity, staking, NFTs, and a Solana bridge. The cookie mcp server is what makes that connection.

What the server does

It runs locally over stdio and signs with your key on your machine, so it is non-custodial by design. It is a community project for the whole Cookie Chain ecosystem.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Cursor — Edit ~/.cursor/mcp.json (applies everywhere) or .cursor/mcp.json in a project (project wins if both exist), then add the [server

Credentials and setup notes

Configuration is passed through the environment: COOKIE_RPC_URL, COOKIE_PRIVATE_KEY, SOLANA_RPC_URL, COOKIE_WARP_PROGRAM_ID, SOLANA_WARP_PROGRAM_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Cookie's toolset — Cursor — is a fair guide to whether it matches your workflow. It is maintained by cookiechain; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
CursorEdit ~/.cursor/mcp.json (applies everywhere) or .cursor/mcp.json in a project (project wins if both exist), then add the [server block](#server-block).

How to install the Cookie MCP server

{
  "mcpServers": {
    "cookie": {
      "command": "npx",
      "args": ["-y", "cookie-mcp"],
      "env": {
        "COOKIE_RPC_URL": "your-value",
        "COOKIE_PRIVATE_KEY": "your-value",
        "SOLANA_RPC_URL": "your-value",
        "COOKIE_WARP_PROGRAM_ID": "your-value",
        "SOLANA_WARP_PROGRAM_ID": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
COOKIE_RPC_URLEndpoint or connection string the server talks to.Yes
COOKIE_PRIVATE_KEYCredential the server authenticates with.Yes
SOLANA_RPC_URLEndpoint or connection string the server talks to.Yes
COOKIE_WARP_PROGRAM_IDConfiguration value read at startup.Optional
SOLANA_WARP_PROGRAM_IDConfiguration value read at startup.Optional

Example prompts to try

  • Use Cookie to Cursor.

Frequently asked questions

It connects Cookie to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Cursor) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Cookie directly.