Avo

io.github.avohqPublished by GitHub account avohqv1.0.0Updated Nov 2, 2026

Define, ship & query your analytics tracking from one source of truth, trusted by humans and agents.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowData & Analytics

Overview

AI-generated overview

Avo's remote MCP server lets an assistant read and edit your Avo analytics tracking plan: search, inspect and save events, properties and metrics.

What you can do
  • Search and look up events, properties and metrics by name, id, meaning or structural filter
  • Read and inspect the contents of an existing tracking plan
  • Save and edit tracking plan items, including small edits on a branch
  • Run guided workflows and branch operations for designing tracking
  • Bootstrap a new plan with categories, events, properties and constraints
  • Combine plan data with a connected data MCP to diagnose tracking gaps
When to use it
Useful when your team keeps its analytics tracking plan in Avo and you want an assistant to explore it, design tracking for a new feature or PRD, or bootstrap a first plan without leaving the chat client.
Requirements
A remote streamable HTTP endpoint at mcp.avo.app; no local package. An Avo account with OAuth sign-in through the browser on first use, plus a one-time read-to-write re-authorization prompt before the first change.
Before you install
The server can write to your tracking plan, though writes go to a branch and never to main; merging a branch into main is a manual step in the Avo web app. Sign-in is OAuth, so the client holds access to your Avo workspace. The README suggests pairing it with third-party data MCPs, which would send plan context to those services.

Installation

In SourceWeft

  1. Open Avo in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.avohq%2Favo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "avo": {
      "type": "http",
      "url": "https://mcp.avo.app/mcp"
    }
  }
}

README

Avo 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)

bash
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:

json
{  "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.

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:

bash
claude plugin marketplace add avohq/avo-mcpclaude plugin install avo@avo-mcp

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 server
  • skills/ — 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:

bash
cp -R skills/data-designer ~/.claude/skills/data-designercp -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.

Source: README.md at commit 0bcc52c

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts