Claude Code & agents

Two native ways to bring AgentStack into your agent: add the whole catalog to Claude Code as a plugin marketplace, or point an agent at the discovery MCP so it can search and install tools on its own.

Add AgentStack as a Claude Code marketplace

One command registers the entire AgentStack catalog as installable plugins:

/plugin marketplace add agentstack.voostack.com/marketplace.json

Then browse and install from the /plugin menu, or install by name:

/plugin install github-mcp@agentstack
/plugin install pdf-skills@agentstack --scope project

Managing the marketplace

/plugin marketplace list             # marketplaces you've added
/plugin marketplace update agentstack # pull the latest catalog
/plugin marketplace remove agentstack # remove it

Install scopes: user (default, all projects), project (shared via your repo), or local (just you, git-ignored).

Hosted & paid listings

Free, open-source listings install directly from their source. Hosted listings run behind the AgentStack gateway: the plugin points at mcp.agentstack.voostack.com with your per-entitlement token, which Claude Code prompts you to enter once (stored securely). Every call is authenticated against your entitlement and metered: so usage-priced servers bill per successful tool call. Buy a listing on the web, then install it like any other plugin.

Agent discovery MCP

Give an agent the ability to find and install AgentStack tools by itself. Add the discovery MCP as an HTTP server:

claude mcp add --transport http agentstack https://mcp.agentstack.voostack.com/discovery

It exposes three tools the agent can call:

• search_listings(query): find MCP servers, skills, and toolkits by keyword.
• get_listing(slug): full details for one listing (rating, installs, verified status).
• how_to_install(slug): the exact commands to install it.

This is the marketplace agents shop from: an agent can discover a capability it's missing, look it up, and tell you (or itself) exactly how to add it: all security-reviewed.

Machine-readable payments Preview

So an autonomous agent can decide whether to unlock a paid tool on its own, each listing's discovery record is growing a machine-readable payment block. This is a preview of the contract, fields are rolling out through the gateway and may be absent until then.

{
  "slug": "premium-search-mcp",
  "pricing_model": "usage",        // "free" | "one_time" | "subscription" | "usage"
  "cost_per_call": { "amount": 0.002, "currency": "USD" },
  "purchase_token": null            // present once the caller holds an entitlement
}

• pricing_model: how the listing is billed, so an agent knows if a call costs anything.
• cost_per_call: the metered price per successful tool call (usage-priced listings).
• purchase_token: the entitlement/wallet token the agent presents to authorize a paid call, subject to your spending limits.

Paired with agent wallets (also in preview), this lets an agent discover, price, and unlock a paid tool within a budget you set: no human in the loop per call.

Also: the CLI

Prefer the terminal? agentstack add <slug> writes the right config for Claude Code or Cursor automatically. See the CLI reference →.

Frequently asked questions