OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
MCP & Tooling

Capa

Capa is an open-source TypeScript package manager and local MCP gateway for AI coding agents. It uses a project-level capabilities.yaml manifest to declare skills, tools, rules, sub-agents, MCP servers, hooks and plugins, installs them into supported agents, and proxies MCP requests through a local endpoint.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Capa — OpenViST project profile in MCP & Tooling.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Capa when a project needs a shared, version-controlled source for coding-agent setup, especially across multiple supported agents or when MCP access needs per-sub-agent scopes.

Who it is for

  • Developers and teams maintaining AI coding-agent configuration alongside a codebase.
  • Users coordinating capabilities across supported agents such as Cursor, Claude Code, Codex, Windsurf and GitHub Copilot.
  • Teams that want to route MCP tools through a local gateway and scope tool access for sub-agents.

Documented uses

  • Declare agent capabilities once and install them into provider-native configuration formats.
  • Pin resolved capability versions for more consistent project checkouts.
  • Proxy upstream MCP servers through one local endpoint for configured agents.
  • Filter MCP tools by sub-agent and load tools on demand.
  • Edit project capabilities in a local browser UI or invoke configured tools from the CLI.
Before you choose

Requirements & limits

The README documents CLI installation for macOS, Linux and Windows. The repository specifies an MIT license.

  • Capa combines capability installation with a runtime MCP gateway; these are distinct parts of its role.
  • The manifest and lockfile provide a project-centered configuration and record resolved SHA pins.
  • The first install asks for confirmation of executable components; scripts and CI need the documented --yes flag.
  • A dry-run option previews MCP servers, hooks and commands before installation.
  • The local web UI edits project configuration and syncs it to YAML; it is not presented as a hosted service.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Initialize and install project capabilities

Create a Capa manifest and install its declared capabilities into configured coding agents.

Before you start

  • A project directory
  • Capa installed using the documented platform-specific installation method

Steps

  1. From the project directory, run capa init to create capabilities.yaml and register the project with the local Capa server.

  2. Add capabilities to the manifest, or use the documented capa add commands for skills and MCP servers.

  3. Run capa install; review and confirm the executable surface when prompted.

  4. For CI or scripts, use capa install --yes; use capa install --dry-run to preview MCP servers, hooks and commands.

Expected outcome

Capa resolves SHA pins, caches capabilities, writes provider-specific files and registers a local MCP endpoint with each configured agent; resolved pins are recorded in `capabilities.lock`.

Guide limitations

  • Non-interactive shells must pass --yes.
  • The documented install flow confirms executable components on the first install.
Documentation 1 ↗
Source-based practical guide

Edit a project manifest in Capa’s local web UI

Open a project in the browser and edit its configured capabilities through the local interface.

Before you start

  • Capa initialized for the project
  • The local Capa server running

Steps

  1. Run capa open from the project folder.

  2. Edit skills, tools, rules, hooks, plugins or agents in the browser.

  3. Use the UI’s live YAML sync to update capabilities.yaml.

Expected outcome

The project’s capability configuration is edited in the browser and synced back to its YAML manifest.

Guide limitations

  • The documented UI is local and depends on the local Capa server being up.
Documentation 1 ↗
COMPARE OPTIONS

Compare options for AI coding assistance

These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.

ProjectDocumented purposePlatformAccess and requirements
CapaDeclare agent capabilities once and install them into provider-native configuration formats.CLI, DesktopThe README documents CLI installation for macOS, Linux and Windows. The repository specifies an MIT license.
OvertureInspect a coding agent’s planned steps and branches before code is written.Self-hosted, Server, WebOpen-source software under the MIT license. The documented setup runs the MCP server locally and opens its web interface at `http://localhost:3031` by default.
WigoloSearch the web and fetch pages for an agent’s research task.CLI, Self-hosted, ServerThe quickstart lists macOS, Linux and Windows, and requires Node.js 20 or later with about 1.5 GB of free disk space. The repository labels the project public beta.
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
13 October 2026
Original website title
infragate/capa · Official homepage title · retained in its source language
How we review sourcesSuggest a correction