Connect Cursor

This takes about two minutes. Cursor has no browser approval flow, so you create an agent token in the console and paste it into its MCP config once.

1. Create an agent token

   In the Layven console, open Agents and create a token. Scope it to the workspace you want Cursor to reach, then copy the secret. It is shown once.

2. Add Layven to Cursor's MCP config

   Open ~/.cursor/mcp.json and add this block, replacing the token with the one you just copied.

   ~/.cursor/mcp.jsoncopy

   {
     "mcpServers": {
       "layven": {
         "url": "https://api.layven.io/mcp",
         "headers": {
           "Authorization": "Bearer agd_your_agent_token"
         }
       }
     }
   }

   Careful: if you add this to a project-level config instead, that file is often committed to your repo. Do not commit a token; give each teammate their own.

3. Reload Cursor

   Open the MCP settings in Cursor and confirm Layven shows up as connected. Reload the window if it does not pick up the change automatically.

4. Write a test file to confirm it worked

   Ask Cursor's agent to create a file:

   copy

   Write a file called hello.md in my Layven workspace that says hello from Cursor.

   Open the Layven console and look for hello.md at version 1, attributed to the token you created. If it is there, the connection works, and any other agent you connect reads that same file without you copying anything anywhere. You are done.

Revoke access

Open Agents in the console and revoke the token. It stops working on the next request, and everything Cursor wrote stays exactly where it is with its history intact.

Next

Connect a second client and point it at the same workspace. Two agents sharing one drive is the part that does not exist anywhere else: Claude, Claude Code, or Gemini.