Vexo MCP
OfficialThis server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
Vexo MCP
Ask your AI coding tools about your Vexo analytics, session replays, and errors. The Vexo MCP
server is at https://api.vexo.co/mcp and speaks the Model Context Protocol over HTTP (protocol version
2025-06-18). Every tool works only on the apps your account can access: the apps you own and the apps a team shares
with you.
Tools
Read tools work with every connection:
Tool | What it does |
| Lists the apps you can access, with the id every other tool takes as |
| Answers a plain-language analytics question about one app, for example "top 10 screens by errors last week". Returns rows and the SQL it ran. |
| Returns an app's total events, distinct users, and distinct sessions in a time window. |
| Lists session replays, newest or longest first, with filters for errors, rage taps, user, screen, app version, and OS. |
| Reads one session's events in time order: screens, taps, custom events, network requests, logs, and errors. |
| Lists deduplicated errors with counts, app versions, triage status, and assignee. |
| Returns one error's newest occurrence with its stack trace, and the sessions that hit it with their replays. |
| Lists dashboards and the saved insights (trends and funnels) on each. |
| Runs a saved insight over a time window and returns the numbers the dashboard shows. |
| Returns a saved funnel's conversion per step, optionally broken down by OS, app version, country, or an event property. |
| Lists saved cohorts and their definitions. |
| Counts the users in a saved cohort over a time window. |
| Lists heatmap screens with their tap counts. |
Write tools need the mcp:write scope (see Allow changes):
Tool | What it does |
| Sets an error group to |
| Adds a comment to a session, optionally pinned to a playback position. |
Tools that read events take a time window as from and to in milliseconds since the Unix epoch. It defaults to the
last 28 days and can span at most 366 days. For every parameter, see the
MCP tool reference.
Related MCP server: PostHog MCP
Install in Claude Code
Add this marketplace, then install the plugin:
/plugin marketplace add vexotech/vexo-mcp-plugin
/plugin install vexo@vexoThe plugin registers the vexo MCP server. To sign in:
Run
/mcp.Select vexo, and choose Authenticate. A browser window opens.
Sign in to Vexo, and on Authorize access, click Approve.
Then ask questions in plain language, or run /vexo:connect to see your apps and example prompts.
The plugin's connection is read-only. To let Claude Code change data, see Allow changes.
Allow changes
The write tools need an OAuth token with the mcp:write scope. Claude Code asks for the scopes in a server's
oauth.scopes setting, so add a second, write-enabled server for your user:
claude mcp add-json --scope user vexo-write '{"type":"http","url":"https://api.vexo.co/mcp","oauth":{"scopes":"mcp mcp:write"}}'Then run /mcp, select vexo-write, and choose Authenticate. The Authorize access screen says that the
connection can make changes. Without the scope, a write tool returns an error that names mcp:write.
Install in Claude Desktop or Cursor
These clients connect with a static config entry. Create a
personal access token in the Vexo dashboard, then add the server to your
MCP config (claude_desktop_config.json for Claude Desktop, or your Cursor MCP settings), and replace
YOUR_VEXO_TOKEN with your token:
{
"mcpServers": {
"vexo": {
"type": "http",
"url": "https://api.vexo.co/mcp",
"headers": {
"Authorization": "Bearer YOUR_VEXO_TOKEN"
}
}
}
}A personal access token is read-only: it can call every read tool but no write tool.
MCP Registry
server.json lists the Vexo MCP server in the
Official MCP Registry as io.github.vexotech/vexo-analytics, a remote
server at https://api.vexo.co/mcp over Streamable HTTP. MCP clients that read the registry connect to it and sign in
with OAuth, the same as the Claude Code plugin.
To change the listing, edit server.json, set a new version (the registry never changes a published version), and
publish it with mcp-publisher.
Support
Docs: MCP server
Website: https://www.vexo.co
License
MIT. See LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Lets AI agents analyze API metrics, request logs, and traces, and manage apps and alerts.
Product analytics, error tracking, feature flags and SaaS operations with scoped OAuth access.
Query your Logspot analytics, companies, and revenue from any AI assistant, and run your actions.
Your Expo and EAS project in natural language: up to date SDK docs, cloud builds (status, logs, trig
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI-powered analytics for OpenReplay user sessions through natural language queries. Supports session search, user journey analysis, error tracking, performance metrics, and funnel analysis to understand user behavior patterns.112MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables interaction with PostHog's product analytics platform through natural language, allowing users to manage feature flags, view errors, and access other platform features.83 npm1MIT
- AlicenseBqualityDmaintenanceEnables AI agents to query PostHog analytics data directly via tool calls, including insights, events, feature flags, trends, and persons.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables users to ask about render performance in React and React Native apps via natural language, exposing tools for listing render hotspots and explaining component re-renders.MIT