Set it up once
Keep the skills and tool connections your team relies on in a shared catalog.
Capability management
Give AI the right tools for the job
Set up your team’s skills, tool connections, and plugins in one place. Choose what each assistant, agent, or workflow step can use.
Decide what runs where
Give each assistant or workflow step the tools it needs and require the ones it can’t work without.
See what was allowed
Check which capabilities a run could use, which ones were left out, and why.
One catalog, from setup to session
A capability can teach AI how your team works or give it a tool it can call. The catalog lets you decide where each one belongs.
Bring your tools together
Add skills, MCP servers, and plugins in Settings → Capabilities. Search the catalog to find what your team already uses, or add from a supported directory, repository, pasted configuration, or bundle URL.
Set the rules for each job
Attach capabilities to assistants, agents, workers, and workflow steps. Mark a tool required to block the run when it’s unavailable, or optional if the run can continue. Disable inherited tools where they don’t belong.
Give access to the right people
Choose who can attach or use each capability. Connect personal or workspace credentials as the server supports, and control whether assistants can use built-in workspace tools and web search.
Bring the same setup to your editor
Connect supported coding tools in Desktop. Assign capabilities across repositories or to selected ones, add exceptions, and preview what a repository will load. Set a workspace policy for capabilities discovered in workflow repositories.
Review updates on your schedule
Inspect the source and version before approving it. Check for updates without replacing the approved version. Host supported skills or MCP servers as packages or release feeds, with authentication when needed.
Know what the run had access to
Open Capabilities on a session to see which managed tools were available, which local tools were detected, and what was excluded. In the catalog, see which assistants or workflows use a capability before you change it.
Put your team’s rules to work
Give people the same starting point in Chat, in a workflow, and in the coding tools they open themselves.
Standardize code review
Require your review skill on the review step so every run starts with the same checklist.
Scope a team assistant
Give a support assistant the tools it needs to find approved answers and limit who can attach them.
Roll out a skill update
Review the new version in the catalog before you make it available to your team.
See how to set up your catalog
Bring a tool your team uses today. We’ll walk through who can use it and where it should run.