Share a toolset with your team
On a personal account, every prompt, resource, custom tool, and Agent definition you build is yours alone. With an organization, you can keep them in Team or organization spaces that members' agents draw from over MCP — no copy-pasting definitions into each person's setup, and no drift as people tweak their own copies.
Why a shared catalogue
- One source of truth. Shared prompts, resources, custom tools, and Agent definitions live in one place. Fix one, and every agent that uses it gets the fix.
- No per-person duplication. A new teammate connects with an organization credential and their agent can reach the shared content allowed for that credential.
- Scoped by team. Team ownership keeps content in a team's space, while credential bindings determine which team spaces an agent can draw from.
The four ownership spaces
Every customer prompt, resource, custom tool, and Agent definition has exactly one owner:
| Space | What it contains |
|---|---|
| Personal | Items you own outside any organization |
Personal-in-org (me/) | Items you own within an organization |
Team ({team}/) | Items owned by one team |
| Organization | Items owned by the organization in its catalogue |
Prompts, resources, and custom tools can move outward by promotion: a personal draft can become Team-owned, and a Team item can become organization-owned. Agent-definition ownership is fixed after creation, so create an Agent directly in the personal, Team, or organization space where it should live. See Organizations & Teams.
Setting it up
- Create an organization, add teams, and invite members in the dashboard — organizations, teams, members, and roles are managed there.
- Build the content. Author any of the four content types in the dashboard, or let an agent create them in a Team space over MCP (see Let your agent manage its own content). An agent acting on behalf of a member can work in that member's personal-in-org space; Team-space work requires a bound Team and the matching permission.
- Publish what's proven. Promote a solid prompt, resource, or custom tool into the Team or organization catalogue for centralized reuse; organization-catalogue promotion remains a deliberate dashboard action. Agent definitions cannot be promoted, so create them directly in their intended ownership space and use the dashboard for an organization-catalogue definition.
How members' agents consume it
A member connects with an organization credential — an org-scoped API key or an OAuth client (see Authentication). From then on their agent discovers the shared catalogue on each surface granted to that credential:
tools/list/tools/call— custom tools the credential can reach from the organization catalogue, plus those owned by its bound teams, alongside the built-ins.prompts/list/prompts/get— shared customer prompts, named by space ({team}/…, or unprefixed for organization-catalogue prompts), plus platform prompts.resources/list/resources/read— shared resources.list_agents/get_agent/bootstrap— visible Agent definitions, addressed by the same caller-relative names and read from their current active version.
Each customer-content list is computed per credential from org-wide items and items made available through that credential's team bindings. If the credential acts on behalf of a member, the list can also include that member's personal-in-org items. The access model narrows the result further; a credential cannot reach another team's private content.
Hand each agent a credential that reaches only what it should — see Scope an agent to least privilege.