AKAMAN MCP client integrations

AKAMAN is an MCP server available over local stdio or optional authenticated HTTP. Any MCP client capable of launching a local stdio server can potentially use AKAMAN; the configurations below are clients we have documented or tested.

Codex and OpenCode were verified against the tools available on this host. The remaining clients follow each vendor’s published stdio MCP configuration format; adapt the binary path to your own install.

Local stdio integrations

In stdio mode the agent launches /usr/local/bin/akaman --mcp on the same machine and talks to it over standard input and output. There is no network listener, which makes this the default and simplest path for local coding agents.

Codex

Register the local stdio server with the exact minimal command:

codex mcp add akaman -- /usr/local/bin/akaman --mcp

In words: Codex launches the binary, passes --mcp, communicates over stdin/stdout, discovers the single man tool, and calls it when documentation is needed.

Claude Code

Claude Code registers an MCP server with the same shape (see the Claude Code MCP documentation):

claude mcp add akaman -- /usr/local/bin/akaman --mcp

The -- separates Claude Code’s options from the command it should launch.

Gemini CLI

Google’s Gemini CLI provides a dedicated mcp add command for stdio servers:

gemini mcp add akaman /usr/local/bin/akaman --mcp

OpenCode

OpenCode uses the same local command in its configuration file (commonly opencode.json or opencode.jsonc):

{
  "mcp": {
    "akaman": {
      "type": "local",
      "command": ["/usr/local/bin/akaman", "--mcp"],
      "enabled": true
    }
  }
}

• "type": "local" means OpenCode launches the server itself, on the same machine.
• The command array ends in --mcp so the binary starts in MCP stdio mode.

Cursor

Cursor supports local stdio MCP and manages the server process itself. Add AKAMAN to .cursor/mcp.json:

{
  "mcpServers": {
    "akaman": {
      "command": "/usr/local/bin/akaman",
      "args": ["--mcp"]
    }
  }
}

Cline

Cline (the editor extension and its CLI) supports MCP servers. Add AKAMAN to its MCP settings:

{
  "mcpServers": {
    "akaman": {
      "command": "/usr/local/bin/akaman",
      "args": ["--mcp"]
    }
  }
}

VS Code / GitHub Copilot Agent

Current VS Code agent tooling can use MCP servers as external tools. Declare AKAMAN in .vscode/mcp.json:

{
  "servers": {
    "akaman": {
      "type": "stdio",
      "command": "/usr/local/bin/akaman",
      "args": ["--mcp"]
    }
  }
}

Any other MCP client that can launch /usr/local/bin/akaman --mcp as a local process can use AKAMAN the same way.

Remote / HTTP integrations

In HTTP mode AKAMAN runs as a service and the client connects over HTTP with bearer authentication. This is opt-in: normal local use needs no network listener. It is useful for remote agents, containers, VMs, or a central AKAMAN instance shared by several clients.

• Start the server with akaman --http (or --web), which defaults to 127.0.0.1:8931.
• The bearer key is read from /etc/akaman/akamcp.conf (or a path given with --conf); the server refuses to start without it.
• Any MCP-capable client that can connect to an authenticated HTTP endpoint can talk to AKAMAN; the client supplies Authorization: Bearer <APIKEY>.
• Keep the default loopback bind unless you deliberately expose the service; bind outward only behind TLS and a trusted network.

See Configuration for the full file format and transport detail.

Model providers are separate

AKAMAN is an MCP server, not a model or a provider. A provider such as OpenRouter, Anthropic, OpenAI, or Google supplies the model; the agent (Codex, OpenCode, Claude Code, Cline, Cursor, VS Code) is the MCP client that launches or connects to AKAMAN. The two layers are independent:

OpenRouter / Anthropic / OpenAI / Google
                  │
                model
                  │
                  ▼
         Cline / OpenCode / Codex
                  │
               MCP client
                  │
                  ▼
               AKAMAN

This matters because people constantly confuse model, provider, agent, and MCP server. A tool such as Cline may use OpenRouter as its model provider while Cline itself remains the MCP client talking to AKAMAN — over either stdio or HTTP.