Toolstile

npx add-mcp 'https://toolstile.com/mcp'

Your MCP servers behind one endpoint. Every agent on its own terms.

Toolstile is a managed MCP gateway between your agents and remote MCP servers. Connect a server once, point each agent at the same endpoint, and choose which tools, resources and prompts each one may use. Explicit blocks always win.

Create your account · See how access works

Pick an agent and a request in the demo to see an access decision and its activity record. This is an example workspace, not live traffic.

Connect a server once. Every agent gets the same endpoint.

Add a remote MCP server to your workspace and Toolstile keeps the connection: its sign-in, token refresh and status. Agents talk to the gateway, never to the server directly, so server credentials stay in Toolstile rather than in client configuration. When an upstream account needs a fresh sign-in, you reconnect it once in Toolstile.

Personal and team workspaces keep separate catalogs. Each agent authorization belongs to one workspace, so use separately labeled gateway configurations for personal and team work.

Toolstile connects to public HTTPS MCP servers, and the server still decides what its connected account can do. Setup steps are available for Claude Code, Codex, Cursor and Claude Desktop.

Set up your first connection

Example connections, including one account waiting for a fresh sign-in.

Decide per agent, per server. Blocks win.

Each agent gets its own grant on each connection: full access, a selected list of tools, resources and prompts, or nothing. Adding a server does not give any agent access. Full access includes capabilities the server adds later. An explicit block overrides every grant, direct or by policy, and a blocked tool never appears in the agent's list.

Devices group the agents that authorized from them. Remove a laptop and every agent on it stops, in every workspace. Team admins can remove agents only within their own workspace.

Understand agent permissions

An example agent with full server access and one explicitly blocked tool.

Share approved accounts with your team.

In a team workspace, members contribute their own upstream accounts to a shared MCP entry, and an admin approves them. Agents with a grant can use an approved account without anyone copying its credentials into a client.

An admin picks the workspace default and each member can prefer their own approved account. If the selected account becomes unavailable, calls to that entry stop. Toolstile does not fall back to someone else's identity. When a contributor leaves, their account leaves with them unless they first hand it over to another member.

Activity shows which agent called what, on which server, with the outcome and timing. It records metadata by default; storing request arguments and results requires optional debug capture.

Read about shared accounts · Review data handling

Example shared accounts and activity in a team workspace.

Start with your next agent.

Create an account, connect a remote MCP server, and choose what the agent may use. Your personal workspace starts on the Free plan.

Create your account · Sign in

New to the category? Learn what an MCP gateway does. Check the Free plan and paid-plan availability, or read the FAQ.