Cookie MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add cookie-mcp -- npx -y cookie-mcp

{
  "mcpServers": {
    "cookie-mcp": {
      "args": [
        "-y",
        "cookie-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.cookie-mcp]
command = "npx"
args = ["-y", "cookie-mcp"]

{
  "mcpServers": {
    "cookie-mcp": {
      "args": [
        "-y",
        "cookie-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "cookie-mcp": {
      "args": [
        "-y",
        "cookie-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: COOKIE_RPC_URL (Cookie Chain RPC endpoint. Defaults to the public Cookiescan RPC (https://rpc.cookiescan.io).), 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.), 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_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.). The author declared them in the registry entry; get the values from the project itself.