IonWarp logoIonWarp
Get started
IonWarp Docs
Introduction

Connect Your Agent

Point a coding agent, a business agent, or any MCP client at IonWarp — one server URL, one token, three ways to wire it.

Any agent that speaks MCP can drive IonWarp — same tools, same gates, same objects as the product UI. Connecting takes two facts: the server URL, https://ionwarp.com/mcp?project=pr_acme (the ?project= query pins every call to one project), and a personal access token (PAT), minted by a human in the product on the MCP & API Keys page and sent as Authorization: Bearer pat_.... Pick your path below.

Coding agents (Claude Code, Codex, Cursor)

Every client takes the same URL and header; only the config file differs.

Add to .mcp.json at the project root (or ~/.claude.json for every project):

{
  "mcpServers": {
    "ionwarp": {
      "type": "http",
      "url": "https://ionwarp.com/mcp?project=pr_acme",
      "headers": { "Authorization": "Bearer pat_..." }
    }
  }
}

Add to ~/.codex/config.toml:

[mcp_servers.ionwarp]
url = "https://ionwarp.com/mcp?project=pr_acme"
http_headers = { "Authorization" = "Bearer pat_..." }

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "ionwarp": {
      "url": "https://ionwarp.com/mcp?project=pr_acme",
      "headers": { "Authorization": "Bearer pat_..." }
    }
  }
}

Then ask the agent to call whoami — the cheapest proof the token and URL are wired correctly.

Business agents (Hermes, OpenClaw)

Paste one line. The bootstrap page it names is written to be fetched raw and followed with no other context — it carries authentication, the tool list, and the rules that bind a connected agent:

Read and follow https://ionwarp.com/docs/raw/agent-onboarding.md

Any MCP client

The raw connection is one JSON object:

{
  "server": "https://ionwarp.com/mcp?project=pr_acme",
  "headers": { "Authorization": "Bearer pat_..." }
}

Confirm it with one argument-free call:

{ "method": "tools/call", "params": { "name": "whoami", "arguments": {} } }

whoami returns the workspace, the token's effective scopes, and whether the project is pinned — trust its answer over any assumption (Agent Onboarding reads it field by field). The same PAT drives the REST surface too: the API Quickstart is the first call, and Auth is the scope matrix.

Next: Build with AI to let the connected agent fill the project, MCP Tools for every tool it now has, and Skills for the workflows worth delegating.

On this page

IonWarp logoIonWarp

Ready to build? Connect an agent and go — no credit card needed to start.

Get startedSee our plans