Connect MarBoba to your AI editor (MCP)

MarBoba ships a Model Context Protocol (MCP) server, so any MCP-aware AI editor can read and write your catalog — projects, APIs, runbooks, on-call, scorecards, SLOs — right where you code. You bring your own LLM (Claude Code, Cursor, Copilot, Cline, Windsurf, Continue); MarBoba just exposes the catalog.

It’s free on every plan, including Free — there’s no per-seat MCP charge.

For the complete tool list (30 read + 34 write tools) and their parameters, see the MCP server reference.

1. Create a Personal Access Token

In the app: Settings → API Tokens → New token. Tokens look like mb_pat_live_…. Grant the least scope you need:

Copy the token now — it’s shown once.

2. Add the server to your editor

Every MCP client uses the same mcpServers block. Drop this into the right config file and paste your token:

Claude Code

~/.claude/settings.json:

{
  "mcpServers": {
    "marboba": {
      "command": "npx",
      "args": ["-y", "@marboba/mcp"],
      "env": { "MARBOBA_API_TOKEN": "mb_pat_live_…" }
    }
  }
}

Cursor

~/.cursor/mcp.json (or per-project .cursor/mcp.json) — same block.

Cline · Windsurf · Continue · Claude Desktop

All read the same mcpServers shape. Paste the identical JSON into that editor’s MCP config file.

3. Restart and verify

Restart the editor so it launches the server, confirm marboba shows as connected, then ask the assistant to run list_projects — your catalog comes back. With a write token, try create_project and watch it appear in the MarBoba UI (every write is audit-logged and attributed to your token).

4. Point at a non-prod environment (optional)

Defaults to https://api.marboba.com. Override per server:

"env": {
  "MARBOBA_API_TOKEN": "mb_pat_test_…",
  "MARBOBA_ENDPOINT": "https://api-dev.marboba.com"
}

Other install options

• Homebrew: brew install SomexAI-Applications-Group/marboba/marboba-mcp, then set the client’s command to marboba-mcp (drop the npx args).
• Docker: see the reference.

Safe by design

• The token is read from the environment only — never written to disk by the server.
• Scope is enforced by the API, not the client: a read token can’t mutate even if the model tries.
• Privileged actions (rotate a vault secret, roll back, scale) can only be proposed through MCP — a different human approves them in MarBoba’s two-person flow. The server never executes them directly.
• Revoke or rotate a token any time in Settings → API Tokens.