IsoKron

Connecting your fleet

Last updated

IsoKron is a BYO-fleet platform: your own AI agent fleet runs on your own infrastructure and connects to us over the Model Context Protocol (MCP). This article walks through getting your fleet connected and showing as "active" in your dashboard.

Before you start

  • You need a IsoKron workspace (free tier is fine for testing).
  • You need a frontier vendor API key already added to the workspace — see Adding your API key. Without it your fleet will connect but compilations cannot proceed.
  • You need an MCP-capable agent runtime. Claude Code, Cursor, and most modern coding agents support MCP out of the box. Custom MCP clients work as long as they speak the standard transport.

Step 1 — get your connection details

  1. Sign in to your workspace at https://isokron.ai/<your-workspace>.
  2. Open Settings → Fleet.
  3. You will see a connection block containing the MCP host URL and a per-workspace token. Treat the token like a password — anyone who has it can connect a fleet to your workspace until you rotate it.

Step 2 — configure your agent runtime

Claude Code

Add IsoKron to your Claude Code MCP configuration. Open your ~/.config/claude-code/mcp.json (or the per-project equivalent) and add an entry under servers:

{
  "servers": {
    "isokron": {
      "url": "https://mcp.isokron.ai",
      "headers": {
        "Authorization": "Bearer YOUR_WORKSPACE_TOKEN"
      }
    }
  }
}

Restart Claude Code; the IsoKron server should appear in the connected-MCP-servers list.

Cursor

In Cursor, open Settings → MCP servers and add a new entry with the same URL and Authorization header. Restart Cursor.

Custom MCP client

Any client that implements the standard MCP transport works. The endpoint accepts the standard MCP handshake; supply the Authorization header on connect.

Step 3 — verify the connection

Back in Settings → Fleet in your workspace, you should see your fleet listed as Connected within a few seconds, with a recent last heartbeat timestamp.

If it does not appear, the most common causes are:

  • Token typo or stale token. Re-copy the token from Settings → Fleet; the workspace token never has spaces or line breaks.
  • Network egress blocked. Some corporate networks block outbound WebSocket connections; check whether your environment allows the IsoKron MCP host URL.
  • Wrong workspace. If you are a member of multiple workspaces, ensure the token you copied belongs to the one you expect.

What happens after the fleet connects

Once a fleet is connected, you can submit your first compilation from the workspace dashboard. We forward Compiled Output to your fleet via MCP messages; your fleet executes in your own environment using your own credentials. We never see your code or your fleet's credentials.

Troubleshooting

Multiple customers reporting connection issues at once usually indicates a platform incident; we publish those on our public status page. For an issue affecting only your workspace, please email support@isokron.ai with your runtime, the error you are seeing, and (if possible) a screenshot of Settings → Fleet.

Paired with the SR-FLEET-001 customer-support flow.

← All docs