Build

MCP for Claude

@pyre-one/mcp is a Model Context Protocol server. Point Claude at it and launch, trade, or query Pyre in natural language.

Tools

Tool	What it does
pyre_list_tokens	recent launches
pyre_get_token	full details for one token
pyre_curve_state	live bonding-curve state
pyre_holders	top holders
pyre_stats	$PYRE burned, tokens launched
pyre_rewards	everything a wallet has earned
pyre_mixer_modes	the ten fee modes
pyre_launch_token	launch a token
pyre_buy / pyre_sell	trade the curve

Setup

Add Pyre to your MCP config — claude_desktop_config.json for Claude Desktop, or .mcp.json for Claude Code:

json

{
  "mcpServers": {
    "pyre": {
      "command": "npx",
      "args": ["-y", "@pyre-one/mcp"],
      "env": {
        "PYRE_CHAIN_ID": "4663",
        "PYRE_INDEXER_URL": "https://indexer-production-b7e1.up.railway.app",
        "PYRE_FACTORY": "0x…",
        "PYRE_FEE_CONFIG_REGISTRY": "0x…"
      }
    }
  }
}

Read-only vs signing

Without a key the write tools run prepare-only — they return an unsigned transaction for you to review and sign. Add a funded key to let Claude sign and broadcast:

json

"env": { "…": "…", "PYRE_PRIVATE_KEY": "0x…" }

Use a dedicated hot wallet

A key in your MCP config lets the agent spend from it. Fund a throwaway wallet with only what you're willing to automate — never your main account.

Then just ask

text

"Show me the newest Pyre tokens and their graduation progress."

"Launch a token called Ember (EMBER), standard preset, 60% Bonfire and
 40% Merry Men, with a 0.05 ETH dev buy."

"What has 0xabc… earned across all its tokens?"

Under the hood these call the same SDK, so behavior matches the web app exactly.