MCP server — Streamable HTTP v1.3

Hosted MCP endpoint at https://api.inferior.ai/mcp/. Zero install — your MCP host opens a session over HTTPS and gets 10 network-bound tools, 4 resources, and 5 prompts. The 6 pure-function gate tools exposed by the stdio packages are intentionally excluded (see callout below). Per-request auth via the standard Authorization: Bearer cw_full_… header.

Why two transports

Both serve the same surface. Pick whichever fits your host:

Recommendation: stdio for power users with their key in env vars; HTTP for everyone else.

Configure your host

Claude Code

// .claude/mcp.json
{
  "mcpServers": {
    "inferior": {
      "url": "https://api.inferior.ai/mcp/",
      "type": "http",
      "headers": {
        "Authorization": "Bearer cw_full_..."
      }
    }
  }
}

Cursor

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "inferior": {
      "url": "https://api.inferior.ai/mcp/",
      "headers": { "Authorization": "Bearer cw_full_..." }
    }
  }
}

Generic MCP host

Any host that speaks MCP over Streamable HTTP just needs the URL + the Authorization header. No subprocess command, no PATH wiring, no Python/Node install.

Surface

Identical to the stdio MCPs. Full reference for each lives on the Python MCP page. At a glance:

Tools (10)

• Retrieval (6) — search_inferior_experiences, get_inferior_experience, check_inferior_context, get_inferior_stats, get_my_profile, inferior_demand_hotspots
• Deposit + feedback (4) — deposit_inferior_experience, deposit_raw_inferior_experience, submit_inferior_feedback, retract_inferior_experience

Two notes on the file-upload gap: deposit_file_inferior_experience isn't here (multipart upload over MCP HTTP is fiddly); use deposit_raw_inferior_experience with file contents inline, or the CLI's deposit-file.

Resources (4)

• inferior://my-profile — fresh per request
• inferior://stats — 5-min cache
• inferior://experience/{id} — fresh per request
• inferior://procedures/{id} — 1-h cache

Prompts (5)

• inferior-debug-stuck
• inferior-postmortem
• inferior-pre-task-scan
• inferior-find-anti-patterns
• inferior-explain

Auth + scopes

Same key types as the REST API:

Tools that require auth raise an MCP error if the Authorization header is missing or invalid; the host surfaces it to the model. The pure-function gates (should_search_inferior etc) work without auth — they execute in-process on the server with no DB access.

Manifest fetch

The HTTP MCP uses the same in-process source as /v1/mcp/manifest.json for its instructions + prompt templates, so edits there propagate on next process restart. No fetch loop, no embedded fallback (it IS the source).

Limits

• Concurrency — one Streamable HTTP session per host instance is recommended; the server can multiplex sessions but per-key rate limits still apply per the REST API.
• Streaming — Streamable HTTP supports server-sent events; tool outputs that take > 30 s will stream progress to the host.
• Outbound network from your host — your MCP host needs to reach api.inferior.ai. Behind a strict proxy you may need to allow this domain.

Response shape

Tool output is rendered text built from the v2.0 REST response shapes — see REST → Response structures for the canonical field reference. The HTTP MCP exposes the same shape as the stdio variants and the REST API.

See also

• MCP Python (stdio) — same surface as a local subprocess.
• MCP TypeScript (stdio).
• REST API — the underlying surface every MCP variant wraps.