Developers · MCP

Connect RintUp to your AI assistant

Add a single URL to Codex, Claude, Cursor or any other assistant that supports MCP, then approve access in your browser with your RintUp account. From then on, manage your monitors, incidents and status pages from chat.

MCP server URL

https://mcp.rintup.com/mcp

No API key to copy: sign-in happens in your browser with OAuth.

What is RintUp MCP?

The Model Context Protocol (MCP) is an open protocol that lets AI assistants use the tools of external services in a safe, standard way.

The RintUp MCP server gives your assistant tools to list monitors, set up new ones, investigate incidents, schedule maintenance and create status pages in your RintUp account. The assistant only uses them with the permissions you grant, in the workspace you choose.

It is a remote server (Streamable HTTP); there is nothing to install on your computer.

Setup

The steps are the same in every client: add the server, sign in, then on the RintUp page that opens choose a workspace and permissions and click "Allow".

Codex CLI

Add the server and sign in. The login command opens the RintUp consent page in your browser.

Terminal

codex mcp add rintup --url https://mcp.rintup.com/mcp
codex mcp login rintup

Alternatively, add it directly to ~/.codex/config.toml:

~/.codex/config.toml

[mcp_servers.rintup]
url = "https://mcp.rintup.com/mcp"

Claude Code

Add the server with the HTTP transport:

Terminal

claude mcp add --transport http rintup https://mcp.rintup.com/mcp

Then type /mcp inside Claude Code, pick rintup from the list and start authentication; approve access in your browser.

Claude.ai (web and desktop)

Open Settings › Connectors.
Click "Add custom connector"; enter RintUp as the name and the URL below as the address.
Click "Connect" and approve access on the RintUp page that opens.

https://mcp.rintup.com/mcp

On Team and Enterprise plans an administrator may need to enable custom connectors.

Cursor

Add it to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json in your project; Cursor opens the browser to sign in on first use.

~/.cursor/mcp.json

{
  "mcpServers": {
    "rintup": {
      "url": "https://mcp.rintup.com/mcp"
    }
  }
}

VS Code (GitHub Copilot)

Add it to .vscode/mcp.json in your project, then start the server and sign in when prompted.

.vscode/mcp.json

{
  "servers": {
    "rintup": {
      "type": "http",
      "url": "https://mcp.rintup.com/mcp"
    }
  }
}

ChatGPT

If developer mode and custom connectors are available on your account, you can create a new connector in the connector settings and enter the MCP URL. Availability depends on your plan and region; if you don't see it, it isn't enabled for your account yet.

Other MCP clients

Any client that supports remote (Streamable HTTP) MCP servers with OAuth sign-in works: add the URL and the client starts the sign-in flow itself.

Tools

Your assistant can do the following. The exact tool names appear in your client's tool list; the list grows as RintUp evolves.

Monitors

ReadWrite

List monitors and their current status, details and response-time history; create HTTP, ping, port, SSL and domain monitors, edit, pause and resume them.

Incidents

ReadWrite

Incidents from monitors and from Alertmanager, Grafana and PagerDuty-compatible tools: list, acknowledge, resolve and add notes; see services and who they notify.

Alerts

ReadWrite

See alert channels and contact groups; route a monitor to a Slack, email, SMS or webhook channel.

Status pages

ReadWrite

List status pages; create a new page and add monitors to it as components.

Maintenance

ReadWrite

See scheduled maintenance windows and schedule new ones (no alerts are sent during them).

Reports

Read

Uptime percentage and response-time summaries for a given period.

Example prompts

Write to your assistant in plain language; it picks the right tools itself.

“Find the API routes in this Next.js project, create a RintUp monitor for each one and notify Slack if they go down.”
“Why did the payments API go down last night? From which regions, and for how many minutes?”
“Create a status page for my customers and add the website, API and payments monitors as components.”
“Schedule maintenance on Sunday 02:00–04:00 for a database migration so no alerts fire.”
“List the monitors whose uptime dropped below 99.9% in the last 30 days.”

Security

Read and write permissions are separate. Read is always granted; you can remove write on the consent screen. Write never goes beyond what your role in the workspace allows.
Access is limited to the single workspace you choose.
For irreversible actions such as deleting, the assistant asks for your explicit confirmation first.
Response bodies of the endpoints you monitor are never sent to the model; the assistant only sees summaries such as status, timing and status code. Secrets stored in your monitors (Authorization headers, passwords) are never returned.
Sign-in uses OAuth 2.1 with PKCE; the assistant never sees your password or API keys. Access tokens are short-lived and valid only for the RintUp MCP server.
You can remove access at any time under Settings › Connected apps; the application is signed out immediately.

Manage connected apps

Troubleshooting

The consent page says "This application runs on your computer".: Local tools such as Codex, Claude Code and Cursor return the sign-in to a temporary address on your computer (localhost); that is expected. If you did not start the request yourself, though, do not approve it.
Sign-in finished but I can't see the tools.: Restart your client or refresh its MCP server list. On business accounts an administrator may need to allow custom MCP servers.
I want to switch to a different workspace.: Remove the existing access on the Connected apps page, then sign in again from your client and choose the other workspace.