Connect to your MCP client

The MetadataONE server speaks standard MCP over stdio and HTTP/SSE. Drop it into any MCP-compatible runner — Claude Code, Claude Desktop, Hermes, Paperclip, OpenClaw, or a custom agent harness.

Claude Code

Easiest path — one command:

Shell

claude mcp add metadataone npx -y @metadataone/mcp-server \
  --env METADATA_API_KEY=md1_live_7f3a…

Or edit ~/.config/claude-code/mcp.json directly:

JSON

{
  "mcpServers": {
    "metadataone": {
      "command": "npx",
      "args": ["-y", "@metadataone/mcp-server"],
      "env": {
        "METADATA_API_KEY": "md1_live_7f3a…"
      }
    }
  }
}

Restart Claude Code. You'll see 92 tools from metadataone in the MCP status line.

Claude Desktop

Edit the Claude Desktop config file:

OS	Path
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json`
Linux	`~/.config/Claude/claude_desktop_config.json`

Use the same JSON shape as Claude Code above.

Hermes

Hermes loads MCP servers from hermes.toml:

TOML

[mcp.metadataone]
command = "npx"
args    = ["-y", "@metadataone/mcp-server"]
env     = { METADATA_API_KEY = "md1_live_7f3a…" }

[mcp.metadataone.scopes]
read   = true
write  = true
launch = false   # gate launches behind human approval

Paperclip & OpenClaw

Both use MCP over HTTP/SSE. Point them at our hosted endpoint:

YAML

mcp_servers:
  - name: metadataone
    transport: sse
    url: https://mcp.metadataone.com/sse
    headers:
      Authorization: "Bearer $METADATA_API_KEY"

Custom agent (Python)

Using the official Anthropic SDK with MCP:

Python

from anthropic import Anthropic
from mcp.client import MCPClient

mcp_client = MCPClient(
    command="npx",
    args=["-y", "@metadataone/mcp-server"],
    env={"METADATA_API_KEY": os.environ["METADATA_API_KEY"]},
)

client = Anthropic()
tools  = mcp_client.list_tools()

response = client.messages.create(
    model="claude-opus-4-6",
    max_tokens=4096,
    tools=tools,
    messages=[{"role": "user", "content": "Build me an ICP audience of US SaaS VPs."}],
)

Verify the connection

Regardless of which client you use, run this smoke test:

Prompt

Use the metadataone MCP. Call get_account_details and
report the account name, plan, and number of connected channels.

If the response includes your account name and channel count, you're connected. If it errors, check auth errors or visit API status.

You're wired in. Jump to the first-campaign walkthrough or browse the tool catalog.