Warp

A terminal with native Streamable HTTP support — the endpoint goes straight into Settings, no bridge needed.

Setup

1. Create a key in the console and export it as UNZOI_KEY.
2. Open Settings → Agents → MCP servers and click Add, or add the block below to ~/.warp/.mcp.json directly.
3. Paste the JSON block, substituting your key for the placeholder.
4. Ask Warp's agent something that needs current reporting and confirm the tool call appears in the run.

{
  "unzoi": {
    "url": "https://api.unzoi.com/mcp",
    "headers": { "x-api-key": "nai_your_key_here" }
  }
}

What differs here

• Multiple servers live under one JSON object in ~/.warp/.mcp.json, which Warp auto-detects on save — the Settings form writes to the same file, so hand-editing and the UI do not conflict.
• The endpoint is stateless, so there is nothing to restart on this side if a connection drops. Reopening the MCP servers panel reconnects it.
• Warp surfaces the tool call inline in the agent run rather than in a separate log, which makes this one of the faster clients to confirm a connection against.

Next

• Get a key at console.unzoi.com, if you have not.
• The tool reference — what the model is reading when it chooses between the 18 tools.
• Stories for context windows — the one habit that most changes how well an agent works against this API.
• Limits — an agent that loops can spend a month's credits faster than you expect.
• Warp's own MCP documentation — authoritative for anything about the client itself, including config paths, which move.

Endpoint, for copying: https://api.unzoi.com/mcp