Docs

Connect Cursor

Connect Cursor to your workspace memory. The server is https://agentics.you/mcp, named agentics in every tool, so an admin can allowlist one name.

One click from the desktop app

In the Agentics desktop app, Connect your agents lists Cursor with its state. Nothing changes until you confirm.

Click Connect. Before anything changes, the app shows what it will do: “Add Agentics to Cursor's global MCP settings (~/.cursor/mcp.json), keeping your other servers.” With it is the file it changes.
Click Confirm. The app saves a backup of the file beside it (<file>.agentics-backup-<timestamp>, readable by you only), adds the agentics entry and keeps your other servers, then reads the file back to check it.

If Cursor isn't installed, its row says so and offers nothing to click. Once it has agentics, the row says Connected and offers Disconnect.

The app is for macOS and Windows. Get it from Download, which lists each build once a release is published.

By hand

Add this to ~/.cursor/mcp.json, keeping any other servers under mcpServers. Create the file if it doesn't exist:

MCP

{
  "mcpServers": {
    "agentics": {
      "url": "https://agentics.you/mcp"
    }
  }
}

Or open Cursor's install link, which adds the same entry once you confirm in Cursor:

TEXT

cursor://anysphere.cursor-deeplink/mcp/install?name=agentics&config=eyJ1cmwiOiJodHRwczovL2FnZW50aWNzLnlvdS9tY3AifQ%3D%3D

~ is your home folder.

Leave the address as it is: do not add /sse.

A project can have its own .cursor/mcp.json. When both exist, the project's file wins.

Open Cursor Settings > MCP and click Login next to agentics. With the Cursor CLI, run agent mcp login agentics.

A console API key (ak_…) does not work here. Production answers HTTP 401 {"error":"invalid_token"} to one.

The entry holds no token: Cursor signs in with OAuth.

Without a browser

A machine that can't open a browser sends an agent key (agk_mcp_…) instead of signing in. Create one under API keys, Agent keys: it is shown once. Keep it in the environment, not in a file you commit.

MCP

{
  "mcpServers": {
    "agentics": {
      "url": "https://agentics.you/mcp",
      "headers": {
        "Authorization": "Bearer ${env:AGENTICS_AGENT_KEY}"
      }
    }
  }
}

Check it worked

Open ~/.cursor/mcp.json: mcpServers has agentics with https://agentics.you/mcp.

In Agent chat, paste this.

Paste this into your agent

Call the remember tool with content "The customer prefers email over phone." Then call recall with the query "how does the customer like to be contacted?" and tell me the receipt_hash.

remember answers with saved true and a receipt_hash. recall returns that memory in results. Open the verify_url: the check does not show the memory's text.

Disconnect

In the desktop app, click Disconnect, then Confirm. When nothing else in the file changed since Connect, it goes back exactly as it was; otherwise only the agentics entry comes out.

By hand, delete agentics from mcpServers in ~/.cursor/mcp.json.

If your organization manages Cursor

Before it changes anything, the app reads these files. One that blocks agentics stops the connect: the row says “Blocked by your organization's policy” and names the file. One that already provides agentics means there is nothing to add. A file that exists but can't be read stops the connect too.

Cursor's permissions file, which MDM can manage. An mcpAllowlist that leaves out agentics blocks it. The app looks at ~/.cursor/permissions.json.

What the app can't check

Your team's MCP allowlist in the Cursor dashboard isn't visible on this computer.

If it does not connect

What you see	What it means
Needs login, then HTTP 401 `{"error":"invalid_token"}`	Sign-in did not finish, or the header is an `ak_` key. Click Login, or send an `agk_mcp_…` key.
`invalid_redirect_uri`, `redirect_uri must be https, loopback http, or a private-use app scheme`	The sign-in redirect was not one this server accepts. Cursor's own redirects are, so do not set a custom `auth` client in the entry.
Not installed	The app found no Cursor on this computer. Install it, then click Check again.
Another agentics server	Cursor already has a different server named `agentics`. The app won't replace it: remove that one in Cursor first.
Can't read its settings	The app couldn't read Cursor's config or a policy file, so it changes nothing. The row names the file and why.
Blocked by policy	A policy file blocks agentics. The row names it; see the policy files.
Provided by your organization	Your organization already gives Cursor `agentics`, so there is nothing to add.
HTTP 401 `{"error":"invalid_token"}`	Sign-in did not finish, or a console key (`ak_…`) was sent. Sign in again, or send an agent key (`agk_mcp_…`).
HTTP 405 `{"error":"Use POST for JSON-RPC"}`	Something sent GET, as a browser tab does. Clients send POST to `https://agentics.you/mcp`.
HTTP 403, code `-32000`, `Token lacks the mcp:tools scope`	The sign-in can't use the server. Remove agentics, add it again, and choose Allow.
`Unknown tool: remember`	The tool list is stale. Reconnect agentics so the tools are read again after sign-in.
`This connection cannot use remember.`	The grant is missing `actions:record`. Connect again and choose Allow.
`content is required.` (code `-32602`)	`remember` needs `content` as a string.
`Unknown field: …` (code `-32602`)	That argument is not one `remember` takes.
HTTP 429 `{"error":"Too many requests. Try again in a minute.","retry_after":…}`	120 calls a minute on that sign-in. Wait `Retry-After` seconds.
`This workspace has used its 10,000 actions for this month on Free. New actions are paused until the 1st (UTC).`	Free is at its monthly write cap. `recall` still works.

More errors are on Connect any MCP client.