The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Avo listing page.
mcp-name: io.github.avohq/avo
The Avo MCP server (https://mcp.avo.app/mcp) lets Claude, Codex, Cursor, Gemini, and other MCP clients read and edit your Avo tracking plan. This repo also ships Agent Skills and a Claude Code plugin that guide effective use of the server.
Each skill is a self-contained directory with a SKILL.md (instructions + metadata) and bundled resources. Claude loads them automatically when relevant to guide effective use of the Avo MCP server's tools (search, get, save_items, workflow, and the branch tools).
The Avo MCP server is a remote, OAuth-protected HTTP server at https://mcp.avo.app/mcp. Add it to your MCP client:
Claude Code (CLI)
You'll sign in through the browser on first use. The first time you make a change, you'll also get a one-time read → write re-auth prompt.
Claude.ai / Claude Desktop
Add a custom connector pointing at https://mcp.avo.app/mcp (Settings → Connectors → Add custom connector). Authenticate when prompted.
Cursor and other MCP clients
Add a remote (streamable HTTP) MCP server to your client's config:
If you install the Claude Code plugin (below), it registers this server for you — these steps are for connecting the server directly (other clients, or Claude Code without the plugin).
data-designer — Work with an existing Avo tracking planExplore, search, and design against an existing Avo tracking plan: look events / properties / metrics up by name, id, meaning, or structural filter; review, prioritize, and implement branches; design tracking for a new feature or PRD against what already exists; make small branch edits; and combine Avo with a connected data MCP (Amplitude, Mixpanel, PostHog, BigQuery, Snowflake, Databricks, Redshift) to diagnose tracking gaps.
skills/data-designer/data-designer-new-plan — Bootstrap a brand-new Avo tracking planBootstrap a tracking plan from scratch in an empty or near-empty workspace: run a purpose meeting (problems, goals, metrics, key funnels), agree a naming convention, and seed the first categories and start → milestone → complete events with event / user / system properties and constraints — then create a branch.
This repo is also a Claude Code plugin marketplace. Installing the avo plugin bundles both skills and registers the Avo MCP server (https://mcp.avo.app/mcp) in one step:
The plugin's layout:
.claude-plugin/marketplace.json — the marketplace manifest (lists the avo plugin).claude-plugin/plugin.json — the avo plugin manifest.mcp.json — registers the Avo MCP serverskills/ — the two skills, auto-discovered when the plugin is installedTo use the skills without the plugin / MCP registration, copy a skill directory into your personal or project skills folder:
All writes happen on a branch, never on main; the MCP never merges — merging a branch into main is always a human step in the Avo web app.
This repo is the source of truth for these skills. Avo's internal tooling syncs them from here (there's no build step to run in this repo). For the canonical, always-current Avo MCP tool list, see the Avo MCP tools reference.
The contents of this repository — the data-designer and data-designer-new-plan Agent Skills and the plugin manifest and configuration — are released under the MIT License.
This covers only the files in this repository. It grants no rights to the Avo MCP server (https://mcp.avo.app/mcp), the Avo web application, Avo SDKs, or any other Avo software or service — these are separate works, governed by Avo's Terms of Service and your agreement with Avo.