mttrly_get_capabilitiesLABSCO SUMMARY
Server triage from the chat window, with the plan deciding what is on the menu.
The tools reach real machines through agents you already run, which is what separates this from a monitoring dashboard: you can ask what is wrong and then run the diagnostic. The capabilities call comes first because what you can reach depends on the plan you are on.
What it is
A remote connector for mttrly, an AI SRE service for server health, diagnostics, playbooks and audit history. Every call reaches the mttrly Central API first, which then talks to the agents on your servers over their existing channel - a standalone agent exposes no local MCP surface of its own.
What you get
- Your plan's capabilities: which tools are available, which are restricted, and the plan limits - the call the vendor asks you to make before any other
- The servers connected to your account, and the status of any one of them
- Current alerts
- A quick triage pass, and a diagnostic run against a server
- A service's actual state as the agent on the machine reports it
- The playbooks available to run
Requirements
An mttrly account with agents already connected, and OAuth with PKCE. The endpoint is remote, so add it as a custom connector rather than in a local stdio config. Browser-origin clients have to be allowlisted before they are accepted.
Setup effort
One command — claude mcp add --transport http mttrly https://api.mttrly.com/mcp
USE CASES
01
Finding out what is wrong right now
Read the current alerts and put a quick triage pass over them, so the first answer is a shortlist rather than a wall of events.
02
Checking one server before you escalate
Read its status, then ask the agent on the box what the service is actually doing rather than what the config claims.
03
Running the diagnostic instead of describing it
See which playbooks apply and run the diagnostic from the same conversation, rather than pasting commands into a terminal.
04
Knowing what your plan actually lets you do
Read the capabilities first - available tools, restricted tools and limits - before planning work around a tool you cannot call.
40 tools
Listed in project docs. Your client may show a different list.
mttrly_list_serversmttrly_get_server_statusmttrly_get_alertsmttrly_quick_triagemttrly_run_diagnosticmttrly_list_playbooksmttrly_get_service_realitymttrly_refresh_realitymttrly_get_server_timelinemttrly_run_deploy_verifiermttrly_read_filemttrly_read_privileged_filemttrly_search_filesmttrly_diff_filemttrly_compare_source_to_distmttrly_get_install_healthmttrly_search_knowledgemttrly_get_morning_briefmttrly_get_investigation_bypassmttrly_acknowledge_proactive_eventmttrly_run_playbookmttrly_execute_commandmttrly_get_pending_actionsmttrly_get_action_resultmttrly_approve_actionmttrly_cancel_actionmttrly_get_audit_logmttrly_write_filemttrly_cleanup_filemttrly_execute_scriptmttrly_bootstrap_recovermttrly_repair_installmttrly_regenerate_install_tokenmttrly_decommission_servermttrly_update_agentmttrly_start_investigationmttrly_generate_retrospectivemttrly_acquire_investigation_bypassmttrly_revoke_investigation_bypassBEFORE YOU INSTALL
What to know first
Tools you get
40 tools named in the project's documentation. On the watchdog plan only 8 tools work; the other 32 need deployment_bro or above and return PLAN_REQUIRED, so call mttrly_get_capabilities first. Six execute tools wait for an approval that expires after 30 minutes.
INSTALLATION
Connect your client
Server setup
Setup
Open Settings -> Connectors.
Choose Add custom connector.
Enter https://api.mttrly.com/mcp.
Complete the OAuth sign-in flow.
claude mcp add
Claude Code
TERMINAL
claude mcp add --transport http mttrly https://api.mttrly.com/mcpHosted endpoint
ENDPOINT URL
https://api.mttrly.com/mcpAdd this hosted endpoint to your MCP client, then sign in.
MCP Clients
Claude.ai, Claude Desktop
Open Settings -> Connectors.
Choose Add custom connector.
Enter https://api.mttrly.com/mcp.
Complete the OAuth sign-in flow.
Codex
Add this to ~/.codex/config.toml, then complete OAuth login with codex mcp login mttrly.
CODEX · TOML
[mcp_servers.mttrly]
url = "https://api.mttrly.com/mcp"Cursor
Add https://api.mttrly.com/mcp as a remote MCP server URL.
Cursor should discover the protected resource metadata from the server challenge and start OAuth.
