Set up Cursor

Cursor connects to the hosted server directly over HTTP with a header for the token.

No token needed

A server entry with only "url": "https://mcp.hypervalent.io/mcp" makes Cursor ask you to log in to Studio and approve the connection. See Connect by logging in. The steps below are the pasted-token alternative.

1. Get the snippet from Studio

In Studio open Settings → API tokens, create a Read + write token if the assistant should author content (which token?), then open Use with AI, choose Cursor and copy the JSON. Replace the token placeholder (the prefix followed by …) with the full atk_… value.

2. Add it to Cursor's MCP config

Open Cursor Settings → MCP → Add new global MCP server, or edit the file directly:

Scope	File
Every workspace	~/.cursor/mcp.json
This workspace only	.cursor/mcp.json in the repository

{
  "mcpServers": {
    "hypervalent": {
      "url": "https://mcp.hypervalent.io/mcp?org=YOUR_ORG_ID",
      "headers": { "Authorization": "Bearer atk_YOUR_TOKEN" }
    }
  }
}

Tokens in a repository

A workspace .cursor/mcp.json is easy to commit by accident. Prefer the global file, or keep the workspace file out of version control and give each developer their own token.

3. Check it connected

In Cursor Settings → MCP the server shows a green dot and its tool list. In the agent chat, ask:

Which Hypervalent projects can you reach?

Notes

• Cursor's agent asks before running a tool unless you enable auto-run. Keep publish, unpublish and trash on ask — they affect live sites immediately.
• Cursor caps the number of tools it sends to the model per request. The Hypervalent server exposes nineteen; if you run many servers at once, disable the ones you are not using so the Hypervalent tools stay in the set.