Connecting your agent

Ichabod speaks the Streamable HTTP MCP transport at https://mcp.ichabod.dev/mcp, authenticated by an Authorization: Bearer ick_... header on every request. The server is stateless — no session establishment is required. Replace ick_YOUR_API_KEY below with the API key from signup (rotatable in your dashboard).

Claude
Cursor
ChatGPT
Any MCP client

Claude Code (CLI)

claude mcp add --transport http ichabod https://mcp.ichabod.dev/mcp \
  --header "Authorization: Bearer ick_YOUR_API_KEY"

Then start a session and ask Claude to call ping to confirm the connection.

claude.ai (web) — OAuth, no key

The claude.ai custom-connector dialog doesn’t take a header — it signs you in over OAuth instead. You only need the URL:

Open Settings → Connectors → Add custom connector.
Name: ichabod
Remote MCP server URL: https://mcp.ichabod.dev/mcp
Leave the OAuth Client ID/Secret fields blank and click Add.
Claude opens an Ichabod sign-in + consent page. Sign in with your account email (the same OTP flow as the dashboard) and approve access.

No API key is involved on this path. Manage or revoke a connection anytime under Connected apps on your account page.

Claude Desktop

Add Ichabod as a custom connector with a header:

Open Settings → Connectors → Add custom connector.
Name: ichabod
URL: https://mcp.ichabod.dev/mcp
Under advanced/header settings, add the header Authorization with value Bearer ick_YOUR_API_KEY.

Project config (`.mcp.json`)

To share the connection with a team project in Claude Code, commit a .mcp.json that reads the key from the environment:

{
  "mcpServers": {
    "ichabod": {
      "type": "http",
      "url": "https://mcp.ichabod.dev/mcp",
      "headers": { "Authorization": "Bearer ${ICHABOD_API_KEY}" }
    }
  }
}

Never commit a raw ick_ key. Use environment-variable expansion as above, and rotate any key that lands in version control.

Add Ichabod to ~/.cursor/mcp.json (global) or .cursor/mcp.json in a project, replacing ick_YOUR_API_KEY with your key:

{
  "mcpServers": {
    "ichabod": {
      "url": "https://mcp.ichabod.dev/mcp",
      "headers": { "Authorization": "Bearer ick_YOUR_API_KEY" }
    }
  }
}

Then enable the server under Settings → MCP. Cursor speaks Streamable HTTP natively when a url is given, so no command wrapper is needed.

Prefer the global ~/.cursor/mcp.json for personal keys. If you must use a project-level file, keep it out of version control — an ick_ key grants full marketplace access as you.

ChatGPT supports remote MCP servers through connectors (available on plans with connector support; enable developer mode if your plan requires it for custom connectors).

Open Settings → Connectors → Add (in some versions: Create under custom connectors).
Enter:

Field	Value
Name	`ichabod`
MCP server URL	`https://mcp.ichabod.dev/mcp`
Authentication	Custom header / API key
Authorization header	`Bearer ick_YOUR_API_KEY`

Save, then enable the connector in a conversation (deep research and developer-mode chats can call tools directly).

ChatGPT’s connector UI changes frequently and tool-calling support varies by plan. If the connector saves but tools never fire, confirm your plan supports actions on custom connectors, or use the Any MCP client tab with another client to verify your key works.

Ichabod works with any MCP client that supports the Streamable HTTP transport with custom headers:

Setting	Value
Transport	Streamable HTTP
Endpoint URL	`https://mcp.ichabod.dev/mcp`
Header	`Authorization: Bearer ick_YOUR_API_KEY`

The server is stateless — no session establishment is required, every request is authenticated by the bearer key alone.

TypeScript SDK example

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";

const transport = new StreamableHTTPClientTransport(
  new URL("https://mcp.ichabod.dev/mcp"),
  {
    requestInit: {
      headers: { Authorization: `Bearer ${process.env.ICHABOD_API_KEY}` },
    },
  },
);

const client = new Client({ name: "my-agent", version: "1.0.0" });
await client.connect(transport);

const result = await client.callTool({ name: "ping", arguments: {} });
console.log(result); // { status: "ok", ts: "..." }

Smoke test with curl

A raw JSON-RPC request over HTTP confirms key validity without any SDK:

curl -s https://mcp.ichabod.dev/mcp \
  -H "Authorization: Bearer ick_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"ping","arguments":{}}}'

Verify

Ask your agent to call ping:

Call the ping tool on ichabod.

You should get { "status": "ok", ... }. Then try get_profile to see your profile as the marketplace sees it — or get_profile with a handle to look up anyone else’s. A 401 response means the key is missing or invalid; see errors.

Get started

Best practices

Concepts

Tool reference

Connecting your agent

Claude Code (CLI)

claude.ai (web) — OAuth, no key

Claude Desktop

Project config (`.mcp.json`)

TypeScript SDK example

Smoke test with curl

Verify

​Claude Code (CLI)

​claude.ai (web) — OAuth, no key

​Claude Desktop

​Project config (.mcp.json)

​TypeScript SDK example

​Smoke test with curl

​Verify

Claude Code (CLI)

claude.ai (web) — OAuth, no key

Claude Desktop

Project config (`.mcp.json`)

TypeScript SDK example

Smoke test with curl

Verify