Power your agent
पब्लिशर का इंस्टॉल। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
रजिस्ट्री में अभी कोई पैकेज्ड रिलीज़ नहीं है। रिपॉज़िटरी का README देखें.
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्चपब्लिशर से
https://github.com/user-attachments/assets/200a8cf9-7236-4cc0-a9e4-332bb6664b41
Agent config today is scattered across CLAUDE.md, .cursor/rules/, , MCP JSON, hooks, and skill folders. No two teammates match. Nothing is pinned. Cloning the repo does not clone the agent setup.
One capabilities.yaml wires skills, tools, rules, sub-agents, MCP servers, and plugins into Cursor, Claude Code, Codex, Windsurf, GitHub Copilot, and 30+ other AI coding agents
AGENTS.mdCAPA collapses that into one version-controlled file next to your code — and a local MCP gateway in front of every tool:
capabilities.yaml — source of truth for every capabilitycapabilities.lock — SHA pins so tomorrow's clone gets the same bytesThe teammate who clones tomorrow gets the exact setup you have today.
.cursor/rules/, .claude/agents/, AGENTS.md, …)capa wrap — run Cursor, Claude, Codex, and more from a shadow workspace so provider dirs never touch your real repocapa add --passthrough — write provider-native files directly when you want unmanaged one-offsgit push toolmacOS and Linux:
curl -LsSf https://capa.sh/install.sh | sh
Windows:
powershell -ExecutionPolicy ByPass -c "irm https://capa.sh/install.ps1 | iex"
cd your-project
capa init
Creates capabilities.yaml and registers the project with the local CAPA server (default http://localhost:5912).
capa add vercel-labs/agent-skills@web-researcher
capa add --server --id brave --cmd npx --arg @brave/brave-search-mcp
capa registry search skills-sh "research"
capa install # interactive: confirms executable surface, then installs
capa install --yes # CI / scripts: skip confirmation
capa install --dry-run # preview MCP servers, hooks, and commands without changes
Resolves SHAs, fills the cache, writes per-provider files, and registers one MCP endpoint with each configured agent. Resolved SHAs land in capabilities.lock.
[!NOTE] Non-interactive shells (CI, scripts) must pass
--yes. The first install prints the executable surface (MCP stdio servers, hooks, command tools, plugins) and asks for confirmation; unchanged surfaces skip the prompt on re-run.
[!TIP] Already have skills, MCP configs, and rules in the repo? After
capa init, use the bundled/bootstrapskill — the agent scans the project and drafts the CAPA config for you.
capa sh # list every configured tool
capa sh brave # list brave subcommands
capa sh brave search --query "…" # run a tool directly
capa sh --raw brave search --query "…" # skip per-tool formatters
Every tool you define is also a CLI command under capa sh.
capa open # open this folder's project in the browser
capa open ../other # or any other project folder
capa status # prints the local URL when the server is up
Edit skills, tools, rules, hooks, plugins, and agents in the browser. Changes sync live back to capabilities.yaml.
capa wrapRun an agent without polluting your repo with .cursor/, .claude/, and friends. CAPA builds a shadow workspace under ~/.capa/workspaces/, symlinks your project (minus provider-owned paths), installs capabilities into the shadow, and launches the agent.
capa wrap cursor # Cursor GUI — stops when the window closes
capa wrap claude # Claude Code (aliases: claude-code)
capa wrap agent # Cursor CLI
capa wrap codex
capa wrap gemini-cli
capa wrap opencode
capa wrap cursor --print-dir # print shadow path, then launch
capa wrap --prune # clean stale workspaces
capa stop # stop server + active wrap sessions
Wrappable today: Claude Code, Codex, Cursor, Gemini CLI, OpenCode, iFlow CLI, Kiro CLI, Qwen Code, Kimi CLI.
[!NOTE] On Windows, creating the shadow workspace may require Developer Mode (or an elevated shell) for symlinks. GitHub Copilot is not wrappable yet — it owns shared
.github//.vscode/trees that need subpath exclusions.
The embedded React UI (served by the local server) covers the full project lifecycle:
Activity is powered by system hooks and the MCP proxy tracer — MCP failures show as error rows, shell tools from capa sh are labeled correctly, and secrets in args/results are redacted.
Plugins are not opaque blobs. CAPA clones the repo, reads Claude (.claude-plugin/) or Cursor (.cursor-plugin/) manifests, and merges skills, MCP servers, rules, sub-agents, and hooks into the same install pipeline as everything else.
capa add owner/repo --plugin --install
capa add cursor-marketplace:some-plugin --plugin
capa registry list
capa registry add anthropics/claude-plugins-official --type claude-marketplace
capa registry search skills-sh "typescript"
[!IMPORTANT] Most registry adapters are executable TypeScript fetched into
~/.capa/registries-managed/. Review the source before enabling a third-party registry. Claude marketplaces are JSON catalogs only — safer by design.
Need a one-off native write without CAPA managing the file?
capa add owner/repo@skill --passthrough --provider cursor
capa add --rule --id ts-strict --inline "Always use strict TypeScript" --passthrough
capa install --passthrough
Passthrough skips capabilities.yaml, the lockfile, and managed-file tracking. Tool aliases, defaults, and formatters still require managed mode (capa add --tool … --passthrough is refused).
capabilities.yaml ──► capa install ──► provider files (.cursor/, .claude/, AGENTS.md, …)
│ │
│ ├── capabilities.lock
│ ├── ~/.capa/cache/ (content-addressed snapshots)
│ └── ~/.capa/db.sqlite (projects, variables, activity)
│
└──► Web UI editor ◄──► file watcher ◄──► disk
Agent ──MCP──► capa gateway (:5912) ──proxy──► upstream MCP (stdio / HTTP / SSE)
│
├── on-demand tools (setup_tools / call_tool)
├── per-sub-agent filtered endpoints
└── ToolCallTracer → activity feed
capa init # create capabilities.yaml + register project
capa add <source> [--plugin] [--install]
capa add --server|--tool|--rule|--hook …
capa install [-p <provider>] [-e .env] [--no-cache] [--yes] [--dry-run]
capa wrap <provider> [--project <path>]
capa sh [tool] [args…] [--raw]
capa registry search|add|list|refresh|remove …
capa start|stop|restart|status
capa clean # remove managed artifacts
capa auth github|gitlab
capa cache | capa cache clean
capa upgrade [--yes] # pin GitHub release + verify installer checksum
Guides, the full schema reference, and the registry catalog:
Maintainer-oriented internals (install pipeline, provider matrix, lockfile semantics) live in docs/.
Questions or bugs? Open an issue.
One capabilities.yaml wires skills, tools, rules, sub-agents, MCP servers, and plugins into Cursor, Claude Code, Codex, Windsurf, GitHub Copilot, and 30+ other AI coding agents
टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Capa stdio पर लोकल चलता है।
पिछली जाँच 2026-11-05 को हुई। One capabilities.yaml wires skills, tools, rules, sub-agents, MCP servers, and plugins into Cursor, Claude Code, Codex, Windsurf, GitHub Copilot, and 30+ other AI coding agents