Cline / Continue / Zed / others

Most other MCP-capable clients today use stdio. The bundled shim works the same way everywhere; only the config file location and key names differ.

Cline (VS Code)

Settings JSON → cline.mcpServers:

{
  "cline.mcpServers": {
    "agent_api": {
      "command": "node",
      "args": ["C:/path/to/5m-mcp/dist/mcp-stdio.js"],
      "env": {
        "AGENT_API_URL": "http://127.0.0.1:30120/agent_api/mcp",
        "AGENT_API_TOKEN": "PASTE_YOUR_TOKEN_HERE"
      }
    }
  }
}

Continue

~/.continue/config.json:

{
  "mcpServers": [
    {
      "name": "agent_api",
      "command": "node",
      "args": ["C:/path/to/5m-mcp/dist/mcp-stdio.js"],
      "env": {
        "AGENT_API_URL": "http://127.0.0.1:30120/agent_api/mcp",
        "AGENT_API_TOKEN": "PASTE_YOUR_TOKEN_HERE"
      }
    }
  ]
}

Zed AI

~/.config/zed/settings.json:

{
  "context_servers": {
    "agent_api": {
      "command": "node",
      "args": ["C:/path/to/5m-mcp/dist/mcp-stdio.js"],
      "env": {
        "AGENT_API_URL": "http://127.0.0.1:30120/agent_api/mcp",
        "AGENT_API_TOKEN": "PASTE_YOUR_TOKEN_HERE"
      }
    }
  }
}

Anything else MCP-spec-compliant

Run the shim as a subprocess, pipe JSON-RPC over stdio, set the two env vars:

AGENT_API_URL=http://127.0.0.1:30120/agent_api/mcp
AGENT_API_TOKEN=<your token>

For HTTP-capable clients that aren't covered above, see Custom client (raw HTTP).

Surface differences across clients

Feature	Claude Code	Cursor	Cline	Continue	Zed	Codex
Tools	✅	✅	✅	✅	✅	✅
Prompts (`/agent_api:scaffold-fivem-resource`)	✅	❌	❌	⚠️	❌	❌
HTTP MCP	✅	❌	❌	❌	❌	❌
Tools surface the scaffold workflow via `scaffold_fivem_resource_workflow`	✅	✅	✅	✅	✅	✅

Clients without prompts support still get the grill workflow — the agent auto-invokes the workflow tool from intent detection in the tool description.