Share MCP accounts with your team

In Toolstile, a shared MCP entry can have accounts from several contributors. Team members request to share their accounts; an owner or admin approves them. Each agent also needs access to that MCP entry before it can use an approved account.

The workspace default chooses the account for members who have not set a preference. Your preferred account overrides that default for your agents in this workspace. If the selected account becomes unavailable, Toolstile stops requests to that MCP instead of silently switching accounts.

Request to share an account

In the team workspace, open Shared accounts and choose Share a personal account. Select your personal MCP account, then choose an existing shared MCP entry or create a separate entry for it. Submit the request.

You keep your personal entry and ownership of the contributed account. Sharing does not merge your personal catalog with the team's catalog. Adding an account to one team does not make it available in another workspace.

You can also add a new MCP connection from the team workspace. A regular member's contribution waits for approval. Contributions made by someone who can manage shared MCPs are approved when added. Follow Connect a remote MCP server for connection and sign-in steps.

Approve the account, then grant agent access

An owner, admin or member with permission to manage shared MCPs reviews the account under Shared accounts → Approval requests and chooses Approve account. The first approved account becomes the default if the shared entry has no default yet.

Approval makes the account available for use. It does not grant an agent access. Someone who manages agent access must grant each team agent the required permissions, directly or through an assigned policy. Authorizing an agent to join the workspace is also a separate step.

A grant to a shared MCP entry covers all its approved accounts, including accounts approved later. The member's account preference determines which one their agents use. A tool grant does not restrict an agent to one contributor's account. Review agent permissions before approving an additional account.

The connected service's own permissions still apply. Toolstile cannot give an account access that the service has not granted it.

Example: two accounts for one shared MCP

Suppose Ana contributes her account for https://projects.example.com/mcp to the team's shared entry. Sam contributes another account to the same entry. An administrator approves both and makes Ana's account the workspace default.

Sam then selects his own account as his preference. His “coding agent” needs a grant to the shared MCP entry before it can use any of its tools. With that grant, Sam's agent uses Sam's preferred account. Ana's agents use the default unless she chooses otherwise.

Now suppose Sam withdraws his account. Toolstile removes his preference, and because someone had selected the withdrawn account, it also clears the entry's workspace default. Ana's account is still approved, but nobody is moved onto it automatically. Agents without a preference cannot use that entry until an administrator sets a default again; any member can also choose a preferred account for their own agents. Other permitted MCP entries remain usable.

Choose the account your agents use

An administrator can open an approved account and choose Set workspace default. To choose for yourself, open the account and select Use as my preferred account. This changes the selection for your agents in this workspace without changing other members' preferences.

Choose Use workspace default to clear your preference. Review the default before doing so: subsequent calls will use that account.

If your preferred account loses approval, its contributor withdraws it or its authentication stops working, choose an available account or ask its owner to reconnect it. Toolstile does not try a different identity for you. See troubleshooting for missing tools and connection errors.

Withdraw an account or leave a team

You can withdraw an account you contributed with Withdraw this account. Your personal entry remains yours. Other contributors' accounts stay approved, but Toolstile does not move anyone onto them. If the withdrawn account was the default or anyone's preference, the entry's default is cleared, and members choose an account or wait for an administrator to set a new default before that MCP works again.

When you leave or are removed from a team, your agents lose their authorization there. Accounts you still own stop being available to that team. Your personal workspace remains separate.

Hand over an account before leaving

To keep a shared account available after your departure, open it and choose Transfer shared account. Select another current team member. The current contributor must explicitly approve handing over the shared account's existing authentication.

A completed transfer gives the recipient an independent team account while your personal entry stays yours. It survives your departure. It does not change ownership of the account at the connected service, and that service can still revoke the credentials or require sign-in again.

Transfer the account before ending your membership. The recipient should review the account's status and the team's default and preferred selections. A change of contributor does not give agents new permissions; existing grants still determine what each agent may do.

Next step: Check each agent's effective permissions after approving an account or completing a handover.

Related: Permissions · Operations and billing.