Workspace catalog
Every connected account and environment
The workspace endpoint remains available for broad agents. Toolkits publish selected connections without copying their source definitions or credentials.
Give each agent only the tools it needs.
Create a focused MCP endpoint for an agent or workflow without exposing the complete workspace catalog.
One workspace, focused views
Toolkit
Support agent
CRM production + issue tracker
Toolkit
Billing agent
Payments production + CRM production
Toolkit
Test workflow
Payments sandbox + staging API
The boundary is exact
| Surface | Endpoint | Discoverable catalog |
|---|---|---|
| Workspace | /orgs/:organizationId/mcp | All connected workspace connections |
| Toolkit | /orgs/:organizationId/mcp/toolkits/:toolkitSlug | Only connections selected by the toolkit |
A toolkit agent cannot search, describe, or invoke a tool from a connection outside that set. The catalog boundary applies before the tool reaches the runtime.
Discovery scope is not authorization
Toolkits reduce what an agent can find. They do not replace the policy engine or grant permission to invoke everything they expose.
- * The same
skills,execute, andresumetools - * The same bounded QuickJS runtime
- * The same allow, approval, and block outcomes
- * The same credential isolation and audit path