About Avo
Avo is a tracking-plan workspace for teams designing and maintaining analytics instrumentation. Its remote MCP server supports querying and editing plans, with changes kept on branches for human review and merging.
Key features
- 01Search and retrieve tracking-plan items
- 02Edit plans through branch tools
- 03Design tracking for new features
- 04Bootstrap a tracking plan from scratch
- 05Diagnose tracking gaps with data MCPs
Use cases
- 01Find events or properties by name or meaning
- 02Draft instrumentation for a feature or PRD
- 03Review and prioritize proposed tracking changes
- 04Compare tracking plans with connected data
MCP support
The remote, OAuth-protected MCP server lets clients read and edit Avo tracking plans using search, retrieval, save, workflow, and branch tools. Changes stay on branches; merging is done by a person in the Avo web app.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.avo.app/mcpclaude mcp add --transport http avohq-avo https://mcp.avo.app/mcp{"mcpServers":{"avohq-avo":{"type":"http","url":"https://mcp.avo.app/mcp"}}}Open in Cursor{"servers":{"avohq-avo":{"type":"http","url":"https://mcp.avo.app/mcp"}}}Open in VS Code{"mcpServers":{"avohq-avo":{"type":"http","url":"https://mcp.avo.app/mcp"}}}{"mcpServers":{"avohq-avo":{"serverUrl":"https://mcp.avo.app/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEAvo MCP
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).
Installing the Avo MCP server
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)
claude mcp add --transport http avo https://mcp.avo.app/mcp
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:
{
"mcpServers": {
"avo": { "type": "http", "url": "https://mcp.avo.app/mcp" }
}
}
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).
Skills
data-designer — Work with an existing Avo tracking plan
Explore, 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.
- Path:
skills/data-designer/
data-designer-new-plan — Bootstrap a brand-new Avo tracking plan
Bootstrap 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.
Use as a Claude Code plugin
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:
claude plugin marketplace add avohq/avo-mcp
claude plugin install avo@avo-mcp
The plugin's layout:
.claude-plugin/marketplace.json— the marketplace manifest (lists theavoplugin).claude-plugin/plugin.json— theavoplugin manifest.mcp.json— registers the Avo MCP serverskills/— the two skills, auto-discovered when the plugin is installed
Install skills only (no plugin)
To use the skills without the plugin / MCP registration, copy a skill directory into your personal or project skills folder:
cp -R skills/data-designer ~/.claude/skills/data-designer
cp -R skills/data-designer-new-plan ~/.claude/skills/data-designer-new-plan
Writing model
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.
Source
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.
License
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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.