Marboba Mcp
Expose your MarBoba internal developer platform catalog—projects, APIs, runbooks, on-call, and SLOs—as MCP tools for your own LLM agent.
Overview
marboba-mcp is a MCP server for the Operate phase that exposes MarBoba IDP catalog data—projects, APIs, runbooks, on-call, and SLOs—to your agent via stdio.
What is this MCP server?
- stdio npm package @marboba/mcp version 0.2.2
- Tools oriented around MarBoba IDP: projects, APIs, runbooks, on-call, SLOs
- Requires MARBOBA_API_TOKEN (mb_pat_*) from MarBoba Settings
- Optional MARBOBA_ENDPOINT override for dev stacks such as api-dev.marboba.com
- Package version 0.2.2
- 2 documented environment variables (1 required secret token)
- Default API host https://api.marboba.com per package metadata
What problem does it solve?
During outages or ops work, context is scattered across dashboards and wikis, so agents guess instead of reading your canonical platform catalog.
Who is it for?
Builders already on MarBoba who want Claude Code or Cursor to read the same projects, SLOs, and runbooks the platform already indexes.
Skip if: Solo hackers without a MarBoba account or teams that need SonarQube-style code scanning rather than IDP operations data.
What do I get? / Deliverables
After you configure the token and npm MCP package, your agent can pull MarBoba-backed operational metadata while you investigate or execute runbooks.
- Agent-callable views into MarBoba projects, APIs, runbooks, on-call, and SLOs
- Faster operational lookups without leaving the coding agent
Recommended MCP Servers
Journey fit
Runbooks, on-call context, and SLO visibility matter once you are operating real services, not only while writing first commits. The server surfaces operational catalog data (SLOs, on-call, runbooks) that agents need during incident response and day-two engineering.
How it compares
MarBoba IDP operations catalog over MCP, not a standalone monitoring vendor or generic GitHub integration.
Common Questions / FAQ
Who is marboba-mcp for?
Teams using MarBoba as an internal developer platform who want MCP tools for projects, APIs, runbooks, on-call, and SLOs inside their agent.
When should I use marboba-mcp?
Use it in Operate when triaging incidents, following runbooks, or verifying SLO and on-call context with an LLM assistant.
How do I add marboba-mcp to my agent?
Install @marboba/mcp from npm as a stdio MCP server, set MARBOBA_API_TOKEN to an mb_pat_* token, and optionally MARBOBA_ENDPOINT for non-prod APIs.