Where it fits
Ops and platform teams that want uptime and heartbeat monitoring managed from an assistant.
- Inspect monitoring coverage for a project.
- Propose configurations for uptime monitors.
- Create job heartbeats and webhook sources.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with MonoDuty
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Dispatches one agent per independent problem domain so unrelated failures can be investigated concurrently, then reviews and integrates the results. Use it when failures are separate, need no shared context, and can run without interfering.
For carrying out an implementation plan inside the current session, with the agent acting as the implementer itself. That happens when the human partner picked inline execution or when no subagent tool is available.
Helps decide how to integrate finished work after implementation and passing tests. Presents structured choices for merging locally, pushing and creating a pull request, or keeping the branch.
No skills found
Try a different search term or clear the filters.
Endpoint and configuration
The installer uses the server name monoduty. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
monodutyappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Inspect monitoring coverage for a project. Check the result before you give the server more access.
- 3Check permissions.
Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.
This MCP server isn't available right now. We couldn't connect to the published address when we checked on Nov 16, 2026, so installation is turned off. We've kept the listing for reference. Check the provider's documentation for a current address. The provider page does not currently load. This page stays online as a reference; check the provider's current page before setup.
Technical details
Cloudflare returned error 522 (connection timed out) for the docs and endpoint on 2026-11-16.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- The provider's page did not load when we checked. Confirm the current setup steps before troubleshooting the client.
- We couldn't reach the published address on the last check. Don't use the install command until the provider confirms a current address.
- The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
- The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider documentation
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
MonoDuty documentationhttps://monoduty.com/docs/mcp