Connect MCP servers once. Choose what each AI app can use.
Use the AI apps you already work in without setting up every MCP server again. Choose their tools in one place and keep server credentials out of their configs.
- Free plan
- 5,000 operations a month
- No card required
Toolstile, step by step
Connect MCP servers, authorize your AI apps (agents), choose their tools and see what they did. Example workspace, not live traffic.
Different teams. Access that fits the work.
Engineering
Move from issue to pull request with the context at hand.
Let Codex on a Mac mini use the issue and repository tools it needs, and nothing else.
Explore engineering use casesMarketing
Build the brief from your team's actual context.
Pull campaign data and working docs into the brief, with only the read tools the job needs.
Explore marketing use casesSupport
Find the history before writing the reply.
Pull conversation history and help articles into the reply, with only the tools support needs.
Explore support use cases
Example workflows using compatible remote MCP servers. Available tools and data depend on the services and accounts you connect.
Bring the AI app you already use.
On your laptop, a Mac mini or a hosted computer: connect a remote MCP client with OAuth sign-in or a Toolstile token.
Add to Claude Codeclaude mcp add --transport http toolstile https://mcp.toolstile.com/mcpOther clients use the same address. Sign in once and your connections are already there.
Stop setting up the same server in every app.
Code and issues, campaign data, customer conversations: connect the remote MCP servers for the services your team uses. Keep their sign-ins and connection status in one workspace, ready for the apps you authorize.
Each app uses the same Toolstile address. OAuth tokens refresh automatically, and when an account needs a fresh sign-in you reconnect it here instead of in every client.
- Airtable
- Atlassian
- Calendly
- Canva
- ClickUp
- Datadog
- GitHub
- GitLab
- Granola
- Hugging Face
- Intercom
- Linear
- Miro
- monday.com
- Neon
- Netlify
- Notion
- PayPal
- PostHog
- Sentry
- Square
- Stripe
- Supabase
- Vercel
- Webflow
- Zapier
- +132 more integrations
https://github.example.com/mcphttps://linear.example.com/mcphttps://db.example.com/mcpAdding a server does not grant agent access.
Let Codex open a pull request. Keep the deletion tool blocked.
For example, let Codex use GitHub's pull-request tools while blocking delete_repository. Give Claude Desktop just the issue-search tools it needs. A blocked tool leaves that app's list, and calls to it through Toolstile are refused even when a wider rule allows access.
Retiring a laptop or Mac mini? Remove its device entry to revoke all Toolstile app authorizations grouped under it, across your workspaces.
See how access rules workSelect a cell to edit access. Explicit blocks always win.
| Agent | GitHub | Linear | Postgres |
|---|---|---|---|
| CodexBuild Mac mini | Full accessWith explicit blocks | No access | Selected accessWith explicit blocks |
| Claude DesktopMara's MacBook | Selected access | Selected access | No access |
| Claude CodeCI runner | Selected access | No access | No access |
delete_repositoryShare useful access without passing tokens around.
Let teammates use approved accounts from their own AI apps. Members connect their service accounts, an admin approves them for sharing, and authorized apps can use them without anyone copying server tokens.
See which app called what, with the outcome and timing. Activity stores metadata by default; request arguments and results require optional debug capture. If a selected account becomes unavailable, calls to that connection stop instead of silently switching to someone else's account.
Read about shared accounts| Time | Agent / MCP | Operation | Outcome | Duration |
|---|---|---|---|---|
| 14:02:11 | Claude DesktopLinear | search_tools/call | Allowed212 ms | 212 ms |
| 14:01:48 | CodexGitHub | create_tools/call | Allowed640 ms | 640 ms |
| 13:59:30 | CodexGitHub | delete_tools/call | Blocked3 ms | 3 ms |
| 13:58:07 | Claude CodeLinear | create_tools/call | Blocked18 ms | 18 ms |
Adding an app doesn't mean giving it everything.
New app authorizations start with no access. Each request is checked against current permissions before forwarding. Your connected account's own permissions still apply.
Read security and data handlingServer tokens stay out of app configs
MCP credentials are encrypted before storage. Your apps use their own Toolstile authorization instead.
Private networks stay out of scope
Connect public HTTPS MCP servers on port 443. Private-network and localhost destinations are rejected.
Personal and team work stay separate
Each app authorization belongs to one workspace, with its own connections and access rules.
Bring your team without adding seat fees.
Paid plans start at $29 per workspace; eligible trials last seven days.
Free
$0/month
5,000 operations a month
For a personal workflow or a team trying the gateway.
Starter
$29/month
50,000 operations a month
Adds reusable permission policies.
Team
Best for teams$99/month
250,000 operations a month
Adds custom roles, 90-day history and activity export.
Scale
$299/month
1,000,000 operations a month
Everything in Team with 180-day history, SSO and SCIM.
Try it with one server and one app.
New to the category? Learn what an MCP gateway does or read the FAQ.