OpsLevel MCP

OpsLevel's MCP server puts an internal developer portal's catalog behind MCP tools, so an assistant can answer the questions engineers normally resolve by searching stale wiki pages and pinging people in Slack. It serves component and service records with their owning team, incident and on-call contacts, tier, lifecycle stage, repositories and system dependencies, along with the technical documentation and API specifications attached to each service. The standards side is covered too. Scorecards, checks and maturity levels are readable, so an agent can report which checks a service is failing and what remediation looks like before anyone opens a pull request. During an incident the same catalog answers the questions that cost the most time: who owns the failing service, what depends on it, and who should be paged, without a responder walking the dependency graph by hand. Access runs through an OpsLevel API token, so results respect the permissions of the account behind it, and the workflow is read-heavy by nature: catalog context feeds a coding agent rather than the agent rewriting the catalog. Built for platform engineering teams already running OpsLevel who want service ownership and software standards available inside Claude Code, Cursor and other MCP clients where their engineers already work.