# Connect this agent to agentleFS agentleFS holds the documents a team and its AI agents search, read and write over MCP. Folders carry permissions and every write is kept as a version, so an agent reads exactly what the person behind it may see. You are reading the setup instructions. Find the section for the client you are running in, run its install yourself, then hand the last step to the person you are working with. Add exactly one agentleFS server. ## 1. Install (you do this) ### Claude Code ```bash claude mcp add --transport http --scope user agentlefs https://agentlefsmcp-server-dev.up.railway.app/mcp ``` Then stop. A server added from a tool call is not in the session that added it, so tell the user to restart Claude Code, run `/mcp`, and choose agentlefs to sign in through the browser. Do not try to sign them in yourself: a tool call has no terminal, so OAuth cannot complete from one. ### Codex ```bash codex mcp add agentlefs --url https://agentlefsmcp-server-dev.up.railway.app/mcp ``` Then stop, and tell the user to sign in by running `codex mcp login agentlefs` in their own terminal, then start a new Codex session. ### Cursor Add this entry under `mcpServers` in `~/.cursor/mcp.json`, keeping any servers already there: ```json { "mcpServers": { "agentlefs": { "url": "https://agentlefsmcp-server-dev.up.railway.app/mcp" } } } ``` Then tell the user to open Cursor's MCP settings and sign in to agentlefs through the browser. ### Any other MCP client The endpoint is `https://agentlefsmcp-server-dev.up.railway.app/mcp`, over streamable HTTP. Most clients sign in through the browser, with no token to mint or paste. Cline is the exception. It authenticates remote servers with a request header, so ask the user to sign in to the console, mint an agent token under Permissions, and give it to you for Cline's server settings. Do not write the token into any other file. ## 2. Check it worked Once the user has signed in, call `list_org_folders`. It returns the folders this user reaches. An empty result on a new account is the expected answer. A 401 before they have signed in is normal too. Signing up is free and starts a personal workspace, so there is no organization to create first. ## 3. If it did not work Tell the user to ask whoever runs this deployment, with what you tried and what came back.