Skip to navigation
Connect Your Client

Cursor

View as Markdown

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):

{
  "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 the Cursor UI

Alternatively, open Customize in the Cursor sidebar to add the server from the UI, using the same server URL and Authorization header.

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.