Skip to content
kmem

Connect Cursor

Cursor reads kmem from its MCP configuration file. You add kmem to the file once, and every project can then use it.

The Connect screen marks Cursor Not yet tested with kmem. The steps on this page come from the Cursor documentation.

The Cursor tab in Connect, with the configuration to merge into the Cursor MCP file. (open the full-size image, opens in a new tab)

Create a connection

  1. In kmem, select Connect. The MCP tab opens.
  2. Select Cursor in the list of clients.
  3. Check the New connection form. kmem fills in a name, for example "Cursor · Maya · 8 Oct". You can change it.
  4. Select Create connection.

Create a connection explains each field. Copy the token now. kmem shows it only one time.

Merge the configuration

Cursor keeps its MCP servers for your user account in the file ~/.cursor/mcp.json.

  1. Under Configuration for Cursor, select Copy configuration.
  2. Open ~/.cursor/mcp.json in a text editor. If the file does not exist, create it.
  3. Merge the kmem configuration into the file:
  4. If the file is empty or new, paste the whole configuration.
  5. If the file already has mcpServers, add only the acme-kmem entry inside it. Keep your other servers.
  6. Save the file.

The configuration looks like this:

{
  "mcpServers": {
    "acme-kmem": {
      "url": "https://acme.kmem.app/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Replace acme with your org's subdomain, in the server name and in the endpoint. Replace YOUR_TOKEN with the token of your connection. The Connect screen fills in these values for you.

The server name is <your-org>-kmem, for example acme-kmem. Each org has its own server name, so one computer can hold the kmem of more than one org.

A JSON file must stay valid. Check that each entry in mcpServers has a comma after it, except the last entry.

Turn on kmem in Cursor

  1. Open the MCP settings of Cursor.
  2. Find acme-kmem in the list of servers.
  3. Check the switch of acme-kmem. Turn it on if it is off.

Check the connection

  1. In Cursor, open Agent.
  2. Send the check prompt:
Use kmem to list the docs I can access. If there are none, say so.
  1. In kmem, select Check connection. The three checks must show Seen.

If Cursor shows an error for acme-kmem, check the file. The url must end with /mcp, and the Authorization value must be Bearer, a space and the token.

Keep the token out of a shared project

Cursor also reads a project file, .cursor/mcp.json, inside a project folder. Do not put kmem in that file. A team can commit project files to a shared repository, and the file would then show your token to other people.

Use ~/.cursor/mcp.json in your home folder. That file stays on your computer.

If a token reaches a shared place by mistake, revoke the connection at once, and create a new one. Read Revoke a connection.

Next steps