---
title: Connect Cursor & other clients
description: Use the UptimeTwin connector from Cursor or any MCP client that supports a remote server.
category: integrations
updated: 2026-09-05
tags: [cursor, mcp, connector, setup, integration]
---

The UptimeTwin connector works with any tool that can connect to a remote MCP server with a header — Cursor is a common one. You'll need an [API token](/docs/integrations/api-tokens), on any plan (Free includes 300 connector requests in your first 14 days).

## What every client needs

However you connect, you give the client two things:

- **The server address:** `https://api.uptimetwin.com/api/mcp`
- **An authorization header:** `Authorization: Bearer uwk_live_your_token_here` (your API token, with `Bearer ` in front)

The connector uses the standard MCP **Streamable HTTP** transport, so any up-to-date MCP client can talk to it.

## Cursor

1. Create or open `.cursor/mcp.json` — either in your project folder, or `~/.cursor/mcp.json` for all projects.
2. Add an `uptimetwin` entry, pasting your token where shown:

   ```json
   {
     "mcpServers": {
       "uptimetwin": {
         "url": "https://api.uptimetwin.com/api/mcp",
         "headers": {
           "Authorization": "Bearer uwk_live_your_token_here"
         }
       }
     }
   }
   ```
3. Open Cursor's MCP settings and confirm "uptimetwin" shows as connected.
4. Ask it to "list my UptimeTwin monitors" to check it works.

## If it won't connect

Two responses tell you almost everything, and they mean different things:

- **401 Unauthorized** (`{"error": "Invalid or missing API token."}`) — the request
  reached the connector and the token was rejected. Check you kept `Bearer ` in
  front of it, that you pasted the whole token, and that it hasn't been revoked on
  the [API Tokens](/docs/integrations/api-tokens) page.
- **403 Forbidden** (`{"error": "Forbidden"}`) — this one is **not** about your
  token; the connector never even saw it. It means the request arrived at our
  origin by some route other than the address above, usually because a client
  followed a redirect. Point the client straight at
  `https://api.uptimetwin.com/api/mcp` and don't let it substitute a different host.

You can check a token from a terminal without involving any client:

```bash
curl -i -X POST https://api.uptimetwin.com/api/mcp \
  -H "Authorization: Bearer uwk_live_your_token_here" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
```

A working token returns `200` and a JSON list of tools. `401` means the token is
the problem; anything else means the address or the network path is.

## Other clients

For any other MCP client, point it at the server address above and set the authorization header. The exact place you enter these depends on the client, but the two values are always the same.

If your client only supports **stdio** servers (a local command rather than a URL), use the `mcp-remote` bridge shown in the [Connect Claude](/docs/integrations/connect-claude) guide — it turns the hosted connector into a local command any client can run.

## Get started
- [What the connector can do](/docs/integrations/mcp-tools-reference)
- [Connect Claude](/docs/integrations/connect-claude)

## Related
- [API tokens](/docs/integrations/api-tokens)
- [The UptimeTwin connector (MCP)](/docs/integrations/mcp-overview)