Source: https://manu-tests-all-orgs.docs-staging.pageloop.ai/mcp-tools/connect-your-client/cursor

# Cursor

## Connect from Cursor

Cursor supports remote MCP servers over HTTP. You can configure it via a JSON file or through the Settings UI.

### Configuration File

Create `.cursor/mcp.json` in your project root (or `~/.cursor/mcp.json` for global config):

```json
{
  "mcpServers": {
    "Atomicwork": {
      "type": "http",
      "url": "https://<your-subdomain>.atomicwork.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:ATOMICWORK_TOKEN}"
      }
    }
  }
}
```

Then set `ATOMICWORK_TOKEN` in your environment. Since `.cursor/mcp.json` is usually committed to your repo, prefer the `${env:...}` form over hardcoding — though you can inline the token directly as `"Authorization": "Bearer aw_xxx"` if you'd rather.

### Via Settings UI

1. Open **Settings** > **MCP**
2. Click **Add New MCP Server**
3. Select **HTTP** as the transport type
4. Enter the server URL: `https://<your-subdomain>.atomicwork.com/mcp`
5. Add the header `Authorization` with the value `Bearer aw_xxx`

### Notes

- Project-level config (`.cursor/mcp.json`) takes precedence over global config.
- Cursor resolves `${env:VAR_NAME}` interpolation in `url` and `headers`, so you can keep secrets out of the config file.