OpenRevenue

com.openrevenuePublished by openrevenue.comOfficial publisherv1.0.1Updated Oct 24, 2026

OpenRevenue analytics MCP: projects, stats, visitors, funnels, and goals via API key or OAuth.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

OpenRevenue is a remote analytics MCP server that lets an assistant read projects, stats, visitors, funnels and goals from an OpenRevenue account.

What you can do
Inspect projects and their analytics data through the OpenRevenue API, including statistics, visitor information, funnels and goals. Access is authenticated with an API key or an OAuth access token, so the assistant works within the connected account. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to answer questions about OpenRevenue web analytics, such as project performance, visitor numbers, funnel conversion or goal results, without leaving the chat.
Requirements
A remote streamable HTTP endpoint at mcp.openrevenue.com. An OpenRevenue account and authentication are required: either an API key sent as a Bearer token in the Authorization header, or an OAuth access token obtained through consent. Network access is needed.
Before you install
The Authorization header carries a secret API key or OAuth token; keep it private and grant only the access you intend. The server reads account analytics data, which is sent to the assistant and its model provider during use. No write, send or delete actions are described in the available information.

Installation

In SourceWeft

  1. Open OpenRevenue 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/com.openrevenue%2Fmcp/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": {
    "openrevenue": {
      "type": "http",
      "url": "https://mcp.openrevenue.com/mcp"
    }
  }
}

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.1LatestSep 16, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.