What are toolkits
Bundle tools from multiple MCP servers into a single custom endpoint.
A toolkit is a custom collection of tools pulled from multiple MCP servers. Instead of connecting to each server separately, you can bundle exactly the tools you need, from any combination of your connected servers, into a single MCP endpoint.
Why use a toolkit?
Toolkits are useful in a few specific situations:
- You only need specific tools from multiple servers. Rather than expose all tools from several servers, you can pick just the ones you need.
- You want a focused set of tools for a particular workflow. For example, a "content-creation toolkit" with writing tools from one server and image generation from another.
- You want to restrict what tools your teammates and agents can call. Expose only a read-only subset of an MCP server, instead of every tool it ships with.
How toolkits work
A toolkit has a name, a slug, and a set of sources (MCP server deployments) it pulls tools from. You pick the specific tools you want from each source and can give them aliases for clarity. The toolkit exposes a single MCP endpoint. The tools stay linked to their original sources, so if a source changes or goes away, the toolkit reflects that.
Workspace and personal toolkits
- Workspace toolkits are managed by admins. Admins assign them to members or share them with everyone, and they are how members get access to MCP servers and shared skills. Admins and owners can use every enabled workspace toolkit. Disabling a toolkit removes access for everyone.
- Personal toolkits belong to one person and only organize what that person can already use. They never grant access. You can add your own personal skills. Only admins add MCP tools, and which shared skills you can add depends on your account.
Members can't edit or copy workspace toolkits. See Roles and permissions for what each role can use.