Check the connection details
Use https://mcp.monoduty.com/mcp, including the final /mcp path. Confirm that your client supports remote Streamable HTTP and OAuth. A client that only supports a different transport needs a compatible connection method; changing the endpoint text does not add protocol support.
Sign-in succeeds but the workspace is unavailable
Check these separately:
- The MonoDuty account is active and its email is verified.
- You have administrator permissions in the intended workspace.
- The workspace plan includes API access.
See workspace roles and follow the roles and plan links in the MCP setup documentation for current requirements.
The assistant sees the wrong workspace
The workspace selected during OAuth stays attached to that connection. A dashboard workspace switch does not change it. Review the connected workspace before running tools; reconnect through OAuth to select the intended workspace.
Reading works, but creating or managing fails
Read, proposal, creation and management permissions are separate. Reconnect and explicitly grant the required permission. Approving a tool in your assistant cannot expand the MonoDuty authorization. Resource ownership and plan limits still apply.
Still blocked?
Open a support request. Include the client name and version, whether sign-in completed, the operation that failed, a sanitized error message, and when it happened. Do not paste OAuth tokens, authorization codes or secret integration URLs. If a tool fails, treat the result as unknown; a failed check is not evidence that the monitored service is healthy.
References
MonoDuty MCP setup and permissions · MonoDuty MCP overview
Reviewed against MonoDuty documentation on September 30, 2026.