Connect any MCP client

Layven speaks Streamable HTTP MCP over a single endpoint, so any client that supports MCP can mount it. This is the generic version of the other guides, for a client that does not have one of its own.

1. Create an agent token

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

2. Point your client at Layven

   If your client takes a JSON config, this is the shape most clients expect. If it instead just asks for a server URL and headers, use the URL on its own and set the Authorization header separately.

   copy

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

   Two keys vary by client. Some require the transport spelled out alongside the URL, as "type": "http" or "streamable-http"; a client that reads a URL-only entry as a local command needs it. Gemini CLI instead renames the URL key itself to httpUrl. Layven serves Streamable HTTP only, so anything that picks SSE or stdio will fail to connect at all rather than degrade.

   Careful: do not commit this token to a shared config file. Give each teammate or script its own token instead of sharing yours.

3. Confirm the client lists Layven's tools

   Most MCP clients show connected servers somewhere in settings, along with the tools they expose. Layven registers fourteen: list, read, write, edit, request_upload, finalize_upload, move, delete, history, grep, restore, lock, unlock and activity.

4. Write a test file to confirm it worked

   Ask your client to create a file:

   copy

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

   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 written with it stays exactly where it is with its history intact.

Next

If your client has its own guide, it will be more specific than this one: Claude Code, Cursor, or Gemini.