capa.sh

mx

ns

ns-879.awsdns-45.net

ns-1483.awsdns-57.org

ns-1625.awsdns-11.co.uk

ns-326.awsdns-40.com

caa

txt

google-site-verification=pZdV1xBPG5fd38n5clQ3E5c4nnEM0zx16ih-OuhwcrY

dmarc

User-agent: *
Allow: /

User-agent: GPTBot
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

Sitemap: https://capa.sh/sitemap-index.xml

# capa

> Open-source CLI that installs skills, MCP servers, and tools from one capabilities.yaml into Cursor, Claude Code, Codex, and 35+ coding agents.

Capa is an agentic capabilities manager by Infragate. If a skill, server, rule, hook, or plugin is not in the capabilities file, capa will not manage it.

## Product

- [Homepage](https://capa.sh/): What capa is and how install, wrap, and the local UI fit together
- [Introduction](https://capa.sh/getting-started/introduction/): Managed, wrap, and passthrough modes
- [Installation](https://capa.sh/getting-started/installation/): Install the capa CLI on macOS, Linux, and Windows
- [Capabilities file](https://capa.sh/concepts/capabilities-file/): Schema for providers, skills, servers, tools, plugins, rules, hooks, and agents
- [Web UI](https://capa.sh/guides/web-ui/): localhost:5912 project UI

## Key facts

- One `capabilities.yaml` (or `.json`) is the source of truth
- `capa install` writes provider configs and starts the local server
- `capa wrap` runs agents from `~/.capa/workspaces` without writing provider files into the repo
- Secrets stay out of the file as `${VarName}` placeholders
- Source: https://github.com/infragate/capa
- Org: https://infragate.ai