Local MCP Integration

Local MCP is the right choice when you are developing on your own machine and want your tools to talk to a FluxA MCP server running locally. This guide focuses on Claude Code and gives you concrete commands and config you can copy directly from this page.

Claude Code

Claude Code supports MCP via its own CLI. You can register the FluxA MCP server with a single command.

Option 1: Configure via CLI (recommended)

Run this command in your terminal, replacing the placeholders with values that make sense for your setup:

claude mcp add-json fluxa-ai-wallet-mcp '{
  "command": "npx",
  "args": ["-y", "@fluxa-pay/fluxa-wallet-mcp@latest"],
  "env": {
    "AGENT_EMAIL": "your-email@example.com",
    "AGENT_NAME": "Claude Code - your-machine",
    "CLIENT_INFO": "Claude Code on macOS"
  }
}'

Field meanings:

• AGENT_EMAIL – the email you want associated with this agent.
• AGENT_NAME – a human‑readable label (it will show up in FluxA).
• CLIENT_INFO – a short string describing where this agent runs (e.g., OS / environment).

You can re‑run this command if you ever want to update the configuration.

Option 2: Edit ~/.claude.json manually

If you prefer editing configuration files directly, add a mcpServers entry to ~/.claude.json:

{
  "mcpServers": {
    "fluxa-ai-wallet-mcp": {
      "command": "npx",
      "args": ["-y", "@fluxa-pay/fluxa-wallet-mcp@latest"],
      "env": {
        "AGENT_EMAIL": "your-email@example.com",
        "AGENT_NAME": "Claude Code - your-machine",
        "CLIENT_INFO": "Claude Code on macOS"
      }
    }
  }
}

If you already have a mcpServers block, just add the fluxa-ai-wallet-mcp entry to it instead of overwriting the entire object.

After you save the file, restart Claude Code so it picks up the new configuration.

Checking that Local MCP is working

Once you’ve configured Claude Code, verify that everything is connected:

• In Claude Code, start a fresh session and look for FluxA tools in the MCP tool list (you can use /mcp command to check, it will show the following if it's connected).

• Try invoking a simple FluxA tool to confirm the wiring.
• In the FluxA Dashboard:
  • check Transactions for new activity, and
  • on AI Agents, confirm the relevant agent shows updated spend and activity entries.

If something doesn’t look right:

• make sure the config file was saved and the JSON is valid,
• confirm you restarted Claude Code after editing its config, and
• double‑check that Claude Code is pointing at the Local MCP configuration and not a Remote MCP URL.