ReferenceAvo MCPOverview

Avo MCP (Alpha)

The Avo MCP (Model Context Protocol) server exposes your Avo tracking plan to AI coding assistants. With it, tools like Claude, ChatGPT, Cursor, Codex, and other MCP-compatible clients can read your tracking plan, explore branches, and generate correct analytics instrumentation — without you having to copy-paste event specs into the chat.

🚧

The Avo MCP is currently in alpha and is read-only. We are actively working on write functionality. Let us know what write capabilities you’d like to see — your feedback shapes what we build next.

What you can do with the Avo MCP:

  • Browse tracking plan branches and see what changed
  • Get implementation guides and code diffs for a specific source
  • Search for events and properties by meaning
  • Discover available sources in your workspace

Setup

Claude Code (CLI)

Run this command to add the Avo MCP server:

claude mcp add avo --transport http https://mcp.avo.app/mcp

Claude Desktop app

  1. Open Claude Desktop and go to Customize → Connectors
  2. Click Add custom connector
  3. Set the name to Avo and the remote MCP server URL to https://mcp.avo.app/mcp
🔒

Adding connectors in Claude Desktop requires admin permissions in your organization.

Other MCP clients

Point your client at https://mcp.avo.app/mcp. Your client must support both HTTP transport and the browser-based OAuth authorization flow described in the Authentication section below — the first tool invocation will open a browser window to complete authorization, after which the token is cached. Clients that cannot complete the OAuth flow will not work with the Avo MCP server.

Authentication

The MCP server uses OAuth to authenticate you with Avo. The first time you invoke a tool, your MCP client will prompt you to complete an authorization flow in your browser. Once authenticated, the token is cached for subsequent requests.

Getting started

Most tools are workspace-scoped (health_check and list_workspaces are global exceptions). The typical first-use sequence is:

1. Discover your workspaces

Call list_workspaces to see which Avo workspaces you have access to and find your workspace ID.

2. Save your workspace

Call save_workspace with your workspace ID. This persists the selection in your mcp’s configuration so every subsequent tool call uses it automatically — you won’t need to pass workspaceId each time.

save_workspace also returns the exact config snippet or environment variable needed to make the workspace selection permanent across sessions for your specific MCP client.

3. Use any tool

Once a workspace is saved, you can browse branches, look up sources, search for events, and get implementation guides directly in your AI session.

Common workflows

Implementing a tracking plan branch

  1. list_branches — find the branch you’re working on
  2. get_sources — discover available sources (e.g. “iOS App”, “Web App”)
  3. get_branch_implementation_guide with a branchId and a sourceId — get a summary of what changed and what to implement on a specific branch
  4. get_branch_code_snippets with a branchId and a sourceId — get implementation snippets for each changed event (exact diffs for Codegen sources, pseudocode for manual sources) on a specific branch

Searching for an event

Use search to find events by meaning, not just exact name. The tool uses vector similarity search, so queries like “user signed up” will match events named Account Created or Registration Completed.

🔒

Semantic search requires Avo Intelligence Smart Search to be enabled in your workspace. Workspace admins can enable it in Workspace Settings. If you don’t have admin access, ask a workspace admin to enable it.

Tools

See the Tools reference for the full list of available tools and their parameters.

Import Tracking PlanTools reference