MCP client setup

Generate config

Every block on this page is what init-client prints. It prints config only — it never edits your client files.

loopover-mcp init-client --print codex
loopover-mcp init-client --print claude
loopover-mcp init-client --print cursor
loopover-mcp init-client --print mcp
loopover-mcp init-client --print vscode
loopover-mcp init-client --print codex --mode remote
loopover-mcp init-client --print claude --mode remote
loopover-mcp init-client --print cursor --mode remote
loopover-mcp init-client --print vscode --mode remote
loopover-mcp init-client --print codex --mode miner
loopover-mcp init-client --print claude --mode miner
loopover-mcp init-client --print cursor --mode miner
loopover-mcp init-client --print mcp --mode miner
loopover-mcp init-client --print vscode --mode miner

Local stdio (gateway)

The recommended default. Runs loopover-mcp on your machine, keeps auth and git analysis local, and — once you have run loopover-mcp login — mounts the remote tool set too, so one entry serves every tool your session entitles you to.

• Run loopover-mcp login before starting the client; without a session you get the local-git tools only, plus an advisory resource explaining how to get the rest.
• Pass --no-remote to keep the server purely local and skip the remote mount entirely.
• Assumes loopover-mcp is on your PATH; pass --command /absolute/path/to/loopover-mcp if your client does not inherit your shell PATH.

Codex (OpenAI) (stdio)

[mcp_servers.loopover]
command = "loopover-mcp"
args = ["--stdio"]

Claude Desktop / Claude Code (stdio)

{
"mcpServers": {
  "loopover": {
    "command": "loopover-mcp",
    "args": ["--stdio"]
  }
}
}

Cursor (stdio)

{
"mcpServers": {
  "loopover": {
    "command": "loopover-mcp",
    "args": ["--stdio"]
  }
}
}

Other mcpServers hosts (stdio)

{
"mcpServers": {
  "loopover": {
    "command": "loopover-mcp",
    "args": ["--stdio"]
  }
}
}

VS Code (stdio)

{
"servers": {
  "loopover": {
    "type": "stdio",
    "command": "loopover-mcp",
    "args": ["--stdio"]
  }
}
}

Remote streamable-http

For agents that run in the cloud, or anywhere you do not want a local Node process. Connects straight to the hosted server; the local-git tools are not available over this transport because there is no local checkout to read.

• Authenticates with a bearer token read from LOOPOVER_API_TOKEN — the same variable the CLI honors. Set it in the environment your client starts in; never paste the token into the config file.
• Tools whose work is a local git operation are absent here by design. Use the stdio mode if you need them.

Codex (OpenAI) (remote)

[mcp_servers.loopover]
url = "https://api.loopover.ai/mcp"
bearer_token_env_var = "LOOPOVER_API_TOKEN"

Codex releases before its RMCP client became the default also need experimental_use_rmcp_client = true at the top level of config.toml.

Claude Desktop / Claude Code (remote)

{
"mcpServers": {
  "loopover": {
    "type": "http",
    "url": "https://api.loopover.ai/mcp",
    "headers": {
      "Authorization": "Bearer ${LOOPOVER_API_TOKEN}"
    }
  }
}
}

Cursor (remote)

{
"mcpServers": {
  "loopover": {
    "type": "http",
    "url": "https://api.loopover.ai/mcp",
    "headers": {
      "Authorization": "Bearer ${LOOPOVER_API_TOKEN}"
    }
  }
}
}

VS Code (remote)

{
"servers": {
  "loopover": {
    "type": "http",
    "url": "https://api.loopover.ai/mcp",
    "headers": {
      "Authorization": "Bearer ${LOOPOVER_API_TOKEN}"
    }
  }
}
}

Miner stdio

AMS's own local state-visibility tools, as a separate stdio server. It stays separate on purpose: it reads this machine's SQLite state and shares no code or network path with the hosted server.

• Takes no flags and needs no login — everything it reads is already on this machine.
• A dual-role operator runs this alongside the stdio gateway; the two entries coexist in one client config.

Codex (OpenAI) (miner)

[mcp_servers.loopover-miner]
command = "loopover-miner-mcp"
args = []

Claude Desktop / Claude Code (miner)

{
"mcpServers": {
  "loopover-miner": {
    "command": "loopover-miner-mcp",
    "args": []
  }
}
}

Cursor (miner)

{
"mcpServers": {
  "loopover-miner": {
    "command": "loopover-miner-mcp",
    "args": []
  }
}
}

Other mcpServers hosts (miner)

{
"mcpServers": {
  "loopover-miner": {
    "command": "loopover-miner-mcp",
    "args": []
  }
}
}

VS Code (miner)

{
"servers": {
  "loopover-miner": {
    "type": "stdio",
    "command": "loopover-miner-mcp",
    "args": []
  }
}
}

Every block above comes from the same grid the CLI prints from, so a snippet copied from here and one printed by init-client can never disagree.