Skip to content
Back to search

vexo

MarketplaceWorks with Claude CodeGitHub

Vexo's official Claude Code plugin marketplace.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/vexotech--vexo-mcp-plugin/badge.svg)](/listings/vexotech--vexo-mcp-plugin)

HTML

<a href="/listings/vexotech--vexo-mcp-plugin"><img src="/api/listings/vexotech--vexo-mcp-plugin/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Add this marketplace, then install the plugin:

/plugin marketplace add vexotech/vexo-mcp-plugin
/plugin install vexo@vexo

The plugin registers the `vexo` MCP server. To sign in:

1. Run `/mcp`. 2. Select **vexo**, and choose **Authenticate**. A browser window opens. 3. 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).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 21 lines
  1. {
  2. "name": "vexo",
  3. "description": "Vexo's official Claude Code plugin marketplace.",
  4. "version": "0.2.0",
  5. "owner": {
  6. "name": "Vexo",
  7. "email": "support@vexo.co",
  8. "url": "https://www.vexo.co"
  9. },
  10. "plugins": [
  11. {
  12. "name": "vexo",
  13. "source": "./plugins/vexo",
  14. "description": "Query your Vexo analytics, session replays, and errors from Claude Code via MCP, and triage errors with write access.",
  15. "version": "0.2.0",
  16. "author": { "name": "Vexo", "url": "https://www.vexo.co" },
  17. "homepage": "https://www.vexo.co",
  18. "keywords": ["analytics", "react-native", "mcp", "session-replay", "vexo"]
  19. }
  20. ]
  21. }
README.md · README · 110 lines
  1. # Vexo MCP
  2. Ask your AI coding tools about your [Vexo](https://www.vexo.co) analytics, session replays, and errors. The Vexo MCP
  3. server is at `https://api.vexo.co/mcp` and speaks the Model Context Protocol over HTTP (protocol version
  4. `2025-06-18`). Every tool works only on the apps your account can access: the apps you own and the apps a team shares
  5. with you.
  6. ## Tools
  7. Read tools work with every connection:
  8. | Tool | What it does |
  9. | --- | --- |
  10. | `list_apps` | Lists the apps you can access, with the id every other tool takes as `app_id`. |
  11. | `query_events` | 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. |
  12. | `get_stats` | Returns an app's total events, distinct users, and distinct sessions in a time window. |
  13. | `list_replays` | Lists session replays, newest or longest first, with filters for errors, rage taps, user, screen, app version, and OS. |
  14. | `get_session_timeline` | Reads one session's events in time order: screens, taps, custom events, network requests, logs, and errors. |
  15. | `list_error_groups` | Lists deduplicated errors with counts, app versions, triage status, and assignee. |
  16. | `get_error_group` | Returns one error's newest occurrence with its stack trace, and the sessions that hit it with their replays. |
  17. | `list_dashboards` | Lists dashboards and the saved insights (trends and funnels) on each. |
  18. | `get_insight` | Runs a saved insight over a time window and returns the numbers the dashboard shows. |
  19. | `get_funnel` | Returns a saved funnel's conversion per step, optionally broken down by OS, app version, country, or an event property. |
  20. | `list_cohorts` | Lists saved cohorts and their definitions. |
  21. | `count_cohort` | Counts the users in a saved cohort over a time window. |
  22. | `list_heatmap_screens` | Lists heatmap screens with their tap counts. |
  23. Write tools need the `mcp:write` scope (see [Allow changes](#allow-changes)):
  24. | Tool | What it does |
  25. | --- | --- |
  26. | `set_error_group_status` | Sets an error group to `OPEN`, `RESOLVED`, or `IGNORED`. Needs write access to the app. |
  27. | `add_session_comment` | Adds a comment to a session, optionally pinned to a playback position. |
  28. Tools that read events take a time window as `from` and `to` in milliseconds since the Unix epoch. It defaults to the
  29. last 28 days and can span at most 366 days. For every parameter, see the
  30. [MCP tool reference](https://docs.vexo.co/settings/mcp-server#tool-reference).
  31. ## Install in Claude Code
  32. Add this marketplace, then install the plugin:
  33. ```
  34. /plugin marketplace add vexotech/vexo-mcp-plugin
  35. /plugin install vexo@vexo
  36. ```
  37. The plugin registers the `vexo` MCP server. To sign in:
  38. 1. Run `/mcp`.
  39. 2. Select **vexo**, and choose **Authenticate**. A browser window opens.
  40. 3. Sign in to Vexo, and on **Authorize access**, click **Approve**.
  41. Then ask questions in plain language, or run `/vexo:connect` to see your apps and example prompts.
  42. The plugin's connection is read-only. To let Claude Code change data, see [Allow changes](#allow-changes).
  43. ## Allow changes
  44. The write tools need an OAuth token with the `mcp:write` scope. Claude Code asks for the scopes in a server's
  45. `oauth.scopes` setting, so add a second, write-enabled server for your user:
  46. ```
  47. claude mcp add-json --scope user vexo-write '{"type":"http","url":"https://api.vexo.co/mcp","oauth":{"scopes":"mcp mcp:write"}}'
  48. ```
  49. Then run `/mcp`, select **vexo-write**, and choose **Authenticate**. The **Authorize access** screen says that the
  50. connection can make changes. Without the scope, a write tool returns an error that names `mcp:write`.
  51. ## Install in Claude Desktop or Cursor
  52. These clients connect with a static config entry. Create a
  53. [personal access token](https://docs.vexo.co/settings/api-tokens) in the Vexo dashboard, then add the server to your
  54. MCP config (`claude_desktop_config.json` for Claude Desktop, or your Cursor MCP settings), and replace
  55. `YOUR_VEXO_TOKEN` with your token:
  56. ```json
  57. {
  58. "mcpServers": {
  59. "vexo": {
  60. "type": "http",
  61. "url": "https://api.vexo.co/mcp",
  62. "headers": {
  63. "Authorization": "Bearer YOUR_VEXO_TOKEN"
  64. }
  65. }
  66. }
  67. }
  68. ```
  69. A personal access token is read-only: it can call every read tool but no write tool.
  70. ## MCP Registry
  71. [`server.json`](./server.json) lists the Vexo MCP server in the
  72. [Official MCP Registry](https://registry.modelcontextprotocol.io) as `io.github.vexotech/vexo-analytics`, a remote
  73. server at `https://api.vexo.co/mcp` over Streamable HTTP. MCP clients that read the registry connect to it and sign in
  74. with OAuth, the same as the Claude Code plugin.
  75. To change the listing, edit `server.json`, set a new `version` (the registry never changes a published version), and
  76. publish it with [`mcp-publisher`](https://github.com/modelcontextprotocol/registry/blob/main/docs/modelcontextprotocol-io/quickstart.mdx).
  77. ## Support
  78. - Docs: [MCP server](https://docs.vexo.co/settings/mcp-server)
  79. - Website: https://www.vexo.co
  80. ## License
  81. MIT. See [LICENSE](./LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.