Connect an MCP client

Connect your MCP client to:

https://mcp.onlineornot.com/mcp

Choose your client

Use the instructions for your MCP client. OAuth-capable clients open a browser so you can sign in to OnlineOrNot and approve access.

Claude Code

Run:

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

Claude Code should start OAuth automatically. If it does not, run /mcp inside Claude Code and authenticate the onlineornot server.

Cursor

Open Cursor Settings with Cmd + Shift + J on macOS or Ctrl + Shift + J on Windows and Linux. Select Skills and Integrations, select New MCP Server, and add:

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

You can also use the Install in Cursor button on the MCP installation page.

VS Code

1. Open the Command Palette with Cmd + P on macOS or Ctrl + P on Windows and Linux.
2. Search for and select MCP: Add Server.
3. Select HTTP (HTTP or Server-Sent Events).
4. Enter https://mcp.onlineornot.com/mcp.
5. Name the server OnlineOrNot and complete the authentication flow.

You can also use the Install in VSCode button on the MCP installation page.

Codex

Run:

codex mcp add onlineornot --url https://mcp.onlineornot.com/mcp

The next time you run codex, it opens the OnlineOrNot OAuth flow automatically.

Amp

Run:

amp mcp add onlineornot https://mcp.onlineornot.com/mcp

Amp starts OAuth using Dynamic Client Registration. Follow the browser prompts to authorize the connection.

Gemini CLI

Add the server to ~/.gemini/settings.json:

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

Restart Gemini CLI, then run:

/mcp auth onlineornot

Complete the OAuth flow in the browser window that opens.

OpenCode

Add the server to your global opencode.json configuration:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "onlineornot": {
      "type": "remote",
      "url": "https://mcp.onlineornot.com/mcp",
      "oauth": {}
    }
  }
}

Restart OpenCode, then run:

opencode mcp auth onlineornot

Warp

Open Settings > Agents > MCP Servers, select + Add, then select Streamable HTTP or SSE Server (URL) and enter:

{
  "OnlineOrNot": {
    "url": "https://mcp.onlineornot.com/mcp",
    "headers": {}
  }
}

Windsurf

Open Settings > Tools > Windsurf Settings. Under Model Context Protocol Servers, select View Raw Config and add:

{
  "mcpServers": {
    "onlineornot": {
      "serverUrl": "https://mcp.onlineornot.com/mcp"
    }
  }
}

Zed

Open Zed settings with Cmd + , on macOS or Ctrl + , on Windows and Linux, then add:

{
  "context_servers": {
    "onlineornot": {
      "url": "https://mcp.onlineornot.com/mcp"
    },
    "settings": {}
  }
}

Other MCP clients

Configure a remote Streamable HTTP server with the URL https://mcp.onlineornot.com/mcp. If the client supports MCP OAuth discovery, it should start authentication automatically.

Connect with an API token

Use an API token when your client supports custom HTTP headers. The exact configuration key varies by client; add this header to the remote server configuration:

Authorization: Bearer <your-onlineornot-api-token>

1. In OnlineOrNot, open API Tokens and create a token.
2. Grant READ access only to the resources the agent needs. Add EDIT only when the agent must make changes.
3. Configure the MCP server and bearer header in your client. For clients that use the mcpServers format, the configuration is:

{
  "mcpServers": {
    "onlineornot": {
      "url": "https://mcp.onlineornot.com/mcp",
      "headers": {
        "Authorization": "Bearer <your-onlineornot-api-token>"
      }
    }
  }
}

4. Restart or reload your MCP client.

API tokens belong to one organization. OAuth connections can ask you to select an organization when your account has access to more than one.

The MCP server card advertises OAuth because clients use it for automatic authentication discovery. API-token authentication is also supported, but must be configured manually as an Authorization header.

Verify the connection

Ask the agent to list your uptime checks or heartbeat monitors. A valid credential without the required grant returns a permission error; an invalid or expired credential returns an authentication error.

Treat API tokens and OAuth access tokens as secrets. Do not place them in source control, prompts, screenshots, logs, or agent output.

For tools, permissions, and supported resource categories, see the MCP reference.