Monitoring MCP Server
Testable Monitoring exposes the monitoring web app’s capabilities through a hosted Model Context Protocol (MCP) server. Connect an MCP-compatible client to let external agents inspect and manage your monitoring account with the permissions granted during authentication.
The MCP server is not limited to a few special workflows. It is designed as an external agent interface for the same kinds of actions you can perform in the monitoring web app, including creating and updating monitors, reviewing checks and pings, managing incidents, configuring maintenance windows, working with status pages, changing notifications, and updating organization-level monitoring settings.
Server URL
Use the monitoring MCP endpoint:
https://m.mcp.testable.ioIf your organization uses SAML login, use the MCP endpoint that matches your team’s Testable Monitoring login subdomain:
| Login type | Web app URL | MCP server URL |
|---|---|---|
| Standard Monitoring login | https://m.testable.io | https://m.mcp.testable.io |
| SAML team login | https://[subdomain].m.testable.io | https://[subdomain].m.mcp.testable.io |
The server URL is also shown in the right-side panel on AI Conversations. Use its copy action, or open Agent Settings and copy the URL from the MCP Server section.
Authentication
The Monitoring MCP connection uses OAuth. Add the remote server URL to an MCP client that supports OAuth, then complete the Testable authorization flow in the browser. The client handles the OAuth credentials; you do not need to copy an API key from Testable Monitoring.
For SAML organizations, use [subdomain].m.mcp.testable.io instead of m.mcp.testable.io, using the same subdomain you use to sign in to Testable Monitoring.
What MCP Provides
MCP provides agent access to the same monitoring resources and actions available through the web app. If your authenticated Testable user can perform an action in the monitoring app, an MCP-connected agent can generally perform that action through the server, subject to the client’s approval flow and the tools exposed for your account.
Available actions still depend on your plan, organization permissions, feature flags, and rollout status. MCP clients may also present tool calls differently, so review and approve changes using the controls provided by your client.
Choosing a Client
Use an MCP-compatible client that supports remote HTTP servers and OAuth. Add the copied URL to that client, finish authorization, then verify that the client can list Testable tools before asking it to make changes.