Connect your agent

On this page

Every AI app connects to the same Toolstile gateway URL. Add it to your client as a remote MCP server, sign in through the browser and choose a workspace. Then grant the new agent access to MCP connections in Toolstile; sign-in alone gives it no tools.

Text

https://mcp.toolstile.com/mcp

Use this URL in your client, not an upstream server's URL or an /app/… dashboard address. Devices & agents → Connect an agent shows the same setup for your chosen app. Before starting, add an MCP connection in the workspace you want to use.

Claude Code

Add the gateway from a terminal, then run /mcp inside Claude Code and sign in. Use --scope user to make it available in every project.

Shell

claude mcp add --transport http toolstile 'https://mcp.toolstile.com/mcp'

Full Claude Code guide: scopes, permission rules, SSH sign-in and troubleshooting.

Codex

Register the URL and start browser sign-in. The entry is stored in ~/.codex/config.toml and shared by the Codex CLI, IDE extension and app.

Shell

codex mcp add toolstile --url 'https://mcp.toolstile.com/mcp'
codex mcp login toolstile

Full Codex guide: TOML configuration, approval modes and troubleshooting.

Cursor

Add this entry to .cursor/mcp.json in a project or ~/.cursor/mcp.json for all projects, restart Cursor and sign in from Customize → MCPs.

JSON

{
  "mcpServers": {
    "toolstile": {
      "url": "https://mcp.toolstile.com/mcp"
    }
  }
}

Full Cursor guide: file precedence, approvals and troubleshooting.

Claude Desktop and claude.ai

Add Toolstile as a custom connector under Customize → Connectors with the gateway URL, and choose a sign-in option rather than No sign-in. Availability depends on your Claude plan and role.

Full Claude Desktop and connectors guide: team setup, tool permissions and troubleshooting.

Set up a whole machine from the terminal

On any machine, including one you reach over SSH or a server without a browser, the Toolstile CLI can set up every agent at once:

Shell

npx toolstile auth login
npx toolstile mcp setup

auth login prints a link and a code; open the link in a browser on any device, sign in and approve the code. mcp setup lists the agents it finds on that machine (Claude Code, Claude Desktop, Cursor, Codex, VS Code, Windsurf, Gemini CLI and Cline) and lets you turn each one on or off. Each enabled agent appears under that machine in Devices & agents, ready for you to grant access. Run mcp setup again to change the selection; it removes the agents you turn off. The agents' configs run the CLI as a local relay, and their tokens stay in the CLI's owner-only credentials file instead of the configs.

Grant access and check

Find the new agent under Devices & agents in the workspace you approved. In Access, set each tool to Allow, Require approval or Block, then save. Team admins grant each agent individually. See permissions.

Test tool loads the agent's permitted tools without running one. For a full check, ask the client for one read-only lookup and look for it in Activity.

Other MCP clients

Other clients that support remote MCP servers with browser (OAuth) sign-in can use the same URL, though MCP support alone does not guarantee every client's auth flow works. For a script or an app that only accepts a bearer token, use Connect an agent → Create an agent token in the intended workspace, keep the token (shown once) in a private secret store, and send it as Authorization: Bearer <TOOLSTILE_AGENT_TOKEN>. It is not an OAuth client secret.

Each authorization belongs to one workspace; use a separately named client entry for each. Remove agent revokes one agent's access; Remove device stops every agent grouped under it. If tools are missing, see troubleshooting.