noc724 MCP Integration Guide

Connect your AI assistant to noc724 using the Model Context Protocol (MCP). Once connected, you can check monitor status, investigate incidents, and manage your monitoring setup using plain language instead of the dashboard.

MCP is an open standard that lets AI clients talk to external services. noc724's MCP server gives your AI assistant direct access to your monitors, incidents, status pages and maintenance windows.

Getting started

Step 1: Choose your authentication method

OAuth (recommended)

No setup needed. Your MCP client will prompt you to log in to noc724 and approve the connection. No client ID or secret is required.

Note: You can see and disconnect every app you approved under Integrations & API, in Connected apps. Deleting or rotating your API key does not affect an existing OAuth connection, since OAuth and API keys are separate authentication methods.

Changing your noc724 account password disconnects all MCP OAuth apps. To use them again, reauthorize each app. Write access needs a team role of owner, admin or editor.

API key

If your client does not support OAuth, use your noc724 API key instead.

To get your API key:

1. Log in to noc724
2. Go to Integrations & API
3. Copy your Main API key. If you only need read access, copy the Read-only API key instead.

Step 2: Configure your MCP client

The noc724 MCP server runs as a remote HTTP server. Add one of the following configurations to your MCP client:

Option A — OAuth (recommended)

{
  "mcpServers": {
    "noc724": {
      "url": "https://mcp.noc724.ir/mcp"
    }
  }
}

Your client will handle authentication automatically via OAuth. You can use the OAuth method to add noc724 MCP as a custom connector to ChatGPT, Claude.ai or Claude desktop, with this server address: https://mcp.noc724.ir/mcp

Option B — API key (Bearer token)

{
  "mcpServers": {
    "noc724": {
      "type": "http",
      "url": "https://mcp.noc724.ir/mcp",
      "headers": {
        "Authorization": "Bearer <your-api-key>"
      }
    }
  }
}

Use this for Cursor, VS Code and other clients without OAuth. The Main key can read and write; the Read-only key and monitor-specific keys can only read.

Step 3: Verify the connection

Once configured, ask your AI assistant something like:

• "Show me all monitors that are currently down"
• "What's the uptime of my website monitor over the last 30 days?"
• "What incidents occurred yesterday?"

What you can do

Monitors

Maintenance windows

Requires a plan with maintenance windows.

Incidents

Public Status Pages

Account, alert contacts and tags

Troubleshooting

The connector says it can't reach the server
Check the address is exactly https://mcp.noc724.ir/mcp, with /mcp at the end.

Authentication fails with an API key
Make sure the header is exactly "Authorization: Bearer <your-api-key>" and that the key still exists under Integrations & API.

OAuth login doesn't complete
Log in to the noc724 dashboard in the same browser, then try connecting again and approve the consent page. Clients that use a custom redirect scheme (not https or localhost) can't use OAuth; use an API key there.

I get 401 after it was working
The connection was revoked, your password changed, or the API key was deleted. Connect again.

A tool answers "This connection is read-only"
Use the Main API key, or reconnect over OAuth and keep write access ticked. Your team role must be owner, admin or editor.

A tool answers "Not available on your plan"
That feature needs a higher plan, the same as in the dashboard.

Security

• Your Main API key has the same permissions as your team in noc724. Use the Read-only API key when you only need to query data.
• MCP tool calls count against the same rate limit as API calls made with a key — they share one request quota per team, per rolling 60-second window.
• Phone numbers, channel addresses, webhook URLs, tokens and status page passwords are never sent to the AI assistant.

Limitations

• The Read-only API key cannot create, update, or pause monitors.
• Uptime stats are available for 1 hour, 6 hours, 24 hours, 7 days, 30 days and 90 days.
• Response time history is available for up to the last 30 days.
• Monitor list results are paginated at 100 per page.
• The limit is 120 requests per minute for each team, shared with the API. Over it, requests are rejected with an HTTP 429 error and a Retry-After header.
• Plan limits apply exactly as in the dashboard. Requests fail with a plan error if the feature is not available on your plan.
• Multi-step API monitors and status page passwords are set up in the noc724 dashboard only.
• Nothing can be deleted through MCP.