Get started with MonoDuty MCP: connection, permissions and first checks

Before you connect

Use an active, verified MonoDuty account with administrator access to the workspace and a plan that includes API access. Your assistant must support remote Streamable HTTP and the MonoDuty OAuth sign-in flow. Check the client’s current connection options before starting.

Connect and confirm the workspace

1. Add https://mcp.monoduty.com/mcp as the remote MCP endpoint in your assistant.
2. Sign in to MonoDuty through OAuth. Select the workspace you want this connection to use.
3. Review the permissions and grant only the operations you intend to use.
4. Ask the assistant to inspect workspace context before making changes.

You do not need to paste a customer API token or workspace ID into a native OAuth connection. Switching workspaces in the dashboard does not move an existing MCP connection.

Try this first request:

Inspect the workspace connected to MonoDuty MCP. Summarize the monitoring context you can see and tell me which details you still need. Do not create or change resources.

Watch the example

Watch the MonoDuty ChatGPT MCP demo. The recording is an example; client screens and available tools may change. Use the current setup documentation for connection requirements.

Choose your next step

• Fix a connection or workspace problem
• Understand read, proposal, creation and management permissions
• Set up an API monitor and scheduled-job heartbeat

MonoDuty also advertises a Claude Community connector on its MCP overview. For any client, verify its current remote MCP and OAuth support rather than assuming all integrations expose the same tools.

References

MonoDuty MCP setup and permissions · MonoDuty MCP overview

Reviewed against MonoDuty documentation on September 30, 2026.