Ops platform / Develop
MCP with Claude
Give Claude Code the ops tools over MCP, within the limits of a token.
ops mcp serves the ops tools to an MCP client such as Claude Code. Claude can then read
your logs, traces, metrics and deployments and act on what it finds, as you and within the
token's permissions. Every call is audited as Claude acting for you.
Set it up
Sign the machine in with a token meant for MCP:
ops login --mcp --project rungholt
Add the server to the project's .mcp.json; the project's Develop page shows this
block filled in:
{
"mcpServers": {
"ops": { "command": "ops", "args": ["mcp", "--project", "rungholt"] }
}
}
--project fills in the project for tools that take one. It is a convenience, not a
limit: the token decides what Claude may reach. Pin the token to the project to keep
Claude inside it.
The tools
| tool | does |
|---|---|
list_projects, get_project | the projects you can see |
list_resources | the resources of an environment, with their state |
list_deployments | recent deployments and their verdicts |
search_logs, list_log_services | search the logs |
list_traces, get_trace | traces and their spans |
list_metric_names, metric_series | metrics |
list_secret_variables | variable names and kinds, never values |
list_translations | translation keys |
rollback_service | roll a service back |
set_secret_variable | set a variable |
run_job | run a job now |
set_translation | set a translation |
Twelve tools read and four write. There is no tool that creates or deletes a resource, changes access, or opens a shell, and no tool ever returns a secret value. The Develop page lists the same tools and marks the ones your role does not allow.