Connect and authenticate agent to agentleFS
The agent establishes a secure, authorized connection to the agentleFS MCP server, enabling it to browse, search, and read files based on its specific permissions.
How it works
Changes data in your accountsOperations and infrastructure
The agent reads the connection documentation to understand the setup process. It identifies the necessary steps for either browser-based sign-in for human-driven clients or token-based authentication for headless agents. It then executes the connection command or configures the HTTP endpoint with the appropriate bearer token to establish the session.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Prompt for Connect and authenticate agent to agentleFS
Read the /connect.md file or the documentation page to understand how to connect to agentleFS. If setting up a headless agent, configure the MCP server to use the afs_ token in the Authorization header. If setting up for a human user, initiate the /agentlefs:connect command to trigger the browser sign-in flow.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
The MCP server exposes tools like browse , search and read , and enforces every call against the same grants you set in Permissions.Connect Claude or Cursor over MCP — agentleFS