Skip to content
Sign inGet started
Sign inCreate account

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.

Create free accountConnect your AI
  • Free plan
  • 5,000 operations a month
  • No card required

Toolstile, step by step

toolstile.com/app/acme/connectionsExample data
MCP servers4 connected

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.

Keep the tools and context your teams need within reach, in the AI apps they already use.

  • 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. Keep specific tools, such as repository deletion, blocked on that connection.

    Issue context and code, without handing over every tool.

    Explore engineering use cases

  • Marketing

    Build the brief from your team's actual context.

    Bring campaign data and working docs into the AI app you already use. Share approved MCP accounts with your team instead of passing server tokens around.

    Campaign context for a brief, report or next planning session.

    Explore marketing use cases

  • Support

    Find the history before writing the reply.

    Let your AI app retrieve conversation context and help articles through your support MCP connections. Choose the tools that connection can use and trace requests in activity.

    Customer context for a reply draft or a clear handoff.

    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.

Setup guides
More remote MCP clients

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. When an account needs a fresh sign-in, reconnect it here instead of revisiting every client. Server credentials stay in Toolstile, outside your app configs.

Browse all integrationsSet up your first connection
toolstile.com/app/acme/connectionsExample data
MCP connections
Remote servers this workspace's agents can reach
GitHubhttps://github.example.com/mcp
Connected
Linearhttps://linear.example.com/mcp
Needs sign-in
Postgreshttps://db.example.com/mcp
Connected

Adding a server does not grant agent access.

Example connections in a demo workspace. One account needs a fresh sign-in.

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 work
toolstile.com/app/acme/accessExample data
Access
What each agent may use on each server

Select a cell to edit access. Explicit blocks always win.

AgentGitHubLinearPostgres
CodexBuild Mac miniFull accessWith explicit blocksNo accessSelected accessWith explicit blocks
Claude DesktopMara's MacBookSelected accessSelected accessNo access
Claude CodeCI runnerSelected accessNo accessNo access
Configure accessCodex on GitHub
Full accessAll capabilities are allowed except explicit blocks, including future additions.
Explicitly blocked toolsdelete_repository
Build Mac miniAuthorized
CodexToken · last request 3 min ago
Demo access for Codex on a Mac mini: full GitHub access with delete_repository blocked.

Share 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
toolstile.com/app/acme/settings/membersExample data
Workspace
Members, shared MCP accounts and what their agents did
GitHubShared MCP with accounts from three contributors
Mara's accountWorkspace default
Jonas's accountYour preference
Priya's accountApproved
TimeAgent / MCPOperationOutcomeDuration
14:02:11Claude DesktopLinearsearch_issuestools/callAllowed212 ms212 ms
14:01:48CodexGitHubcreate_pull_requesttools/callAllowed640 ms640 ms
13:59:30CodexGitHubdelete_repositorytools/callBlocked3 ms3 ms
13:58:07Claude CodeLinearcreate_issuetools/callBlocked18 ms18 ms
Example shared accounts and activity in a team workspace.

Start with one service and one app.

  1. Step 1: Connect your tools once

    Add a remote MCP server and sign in to its account. Keep the connection in your workspace instead of setting it up in every app.

    https://mcp.example.com/mcp

  2. Step 2: Connect your preferred AI app

    Add the Toolstile URL in each app and sign in. Your server connections are already in your workspace.

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

  3. Step 3: Choose what the app can use

    Allow a selected set of tools, all tools or no access to each connection. Add a block for any tool you want to keep out of reach.

    tools/call delete_repository → blocked

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 handling

  • Keep server tokens out of app configs

    MCP credentials are encrypted before storage. Your apps use their own Toolstile authorization instead.

  • Reconnect in one place

    For OAuth connections, tokens refresh automatically. If a fresh sign-in is needed, reconnect the account in your workspace.

  • Keep private networks out of scope

    Connect public HTTPS MCP servers on port 443. Private-network and localhost destinations are rejected.

  • Keep personal and team work separate

    Each app authorization belongs to one workspace, with its own connections and access rules.

Bring your team without adding seat fees.

Start free with 5,000 operations a month. 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.

Compare plans

Start with the app you already use.

Connect one remote MCP server and choose what your app can use. Your personal workspace starts free with 5,000 operations a month.

Create free accountConnect your AI

New to the category? Learn what an MCP gateway does or read the FAQ.