OpenRevenue MCP lets AI agents access website analytics directly from OpenRevenue, including projects, traffic statistics, visitors, funnels, goals, and revenue attribution for analyzing website performance and conversions.
Hermes is Nous Research's command-line agent. MCP servers are declared in its YAML config and reloaded without a restart.
This guide connects OpenRevenue MCP to Hermes through MewCP, so Hermes can use OpenRevenue MCP's 24 tools, like get_profile, list_projects and create_project, without your OpenRevenue MCP credentials ever reaching the app.
OpenRevenue MCP signs in through managed OAuth. MewCP stores the token encrypted, refreshes it before it expires and injects it only at call time. Your agent never holds it, so it can never leak it.
More apps
Full Google Search Console control for search analytics, sitemaps, sites, and URL inspection, directly from your AI workflows. This MCP server exposes the Google Search Console API for querying search traffic data, managing sitemaps and site properties, and inspecting the indexing status of any URL. It is built for SEO teams monitoring search performance, developers automating sitemap and property management, and analysts pulling search traffic data into reporting pipelines.
Access AI-powered MSP market intelligence with company profiles, technographics, technology stacks, reputation, hiring signals, SEO performance, security exposure, market sizing, revenue estimates, and competitive benchmarks.
MoSPI MCP Server provides AI agents access to official Indian government statistics from the Ministry of Statistics and Programme Implementation, covering 500+ indicators across employment, prices, industry, national accounts, health, education, trade, and more.
The Statsig MCP Server lets AI agents manage feature flags, create and analyze A/B experiments, inspect dynamic configs and metrics, query logs, and review audit history within Statsig projects.
Other clients
OpenRevenue MCP works the same way in every client below. Pick yours for its own guide.
Free to start.
Scope access to the exact OpenRevenue MCP tools and accounts you allow, work and personal side by side. Anything outside that scope is refused at call time, even when the model asks for it.
Each call is logged: what ran, on which account, and whether it worked. Failures come back structured, so the agent knows whether to retry instead of guessing.
Every app sits behind one secure MCP URL, and there is no server for you to deploy or keep running. Add an integration in the dashboard and it is live on the next call, with no config to change and no new credentials to wire up. Tools load only when a task needs them, so your agent stays fast and focused however many apps you connect.
Edit config.yaml in your Hermes config directory (~/.hermes).
Put this under the top-level "mcp_servers:" key.
Run /reload-mcp in Hermes, or start a fresh session. Sign in when the browser window opens.
Start a new chat and ask: "List the tools you can use from MewCP." You should see your connected apps.
Return the OpenRevenue profile for this connection’s credentials. Use to label multi-account links; id is stable across reconnects.
Use when the user wants to see which sites/projects they can access, or before asking which domain to analyze.
Use when the user wants to add a new analytics project (site) to their account.
Use when the user wants to rename a project or change its time zone (owner/admin).
Use for headline metrics (pageviews, visitors, sessions, avg duration) for a domain and period.
Use when the user wants a day/hour chart of pageviews and visitors over a period.
Use for top pages by pageviews for a domain and period.
Use for traffic sources / referrers for a domain and period.
Use for visitors broken down by country.
Use for visitors broken down by city.
Use for visitors broken down by browser.
Use for visitors broken down by operating system.
Use for device / browser / OS breakdown for a domain and period.
Use when the user wants recent anonymous visitor rows for a project.
Use for a single visitor profile and journey by visitor id.
Use for Core Web Vitals averages (LCP, CLS, INP, etc.) for a period.
Use when the user wants to see funnels defined on a project before asking for a report.
Use for conversion and drop-off for a named funnel over a period.
Use when the user wants to create a funnel (owner/admin). Requires at least 2 steps.
Use when the user wants to change a funnel’s name or steps (owner/admin).
Use only after the user explicitly approves deleting a funnel (owner/admin). Requires confirm: true.
Use when the user wants to see goals configured on a project.
Use when the user wants to create a goal (owner/admin). Types: event, page, pageviews, visitors, visits, bounce_rate, visit_duration, views_per_visit, revenue.
Use only after the user explicitly approves deleting a goal (owner/admin). Requires confirm: true.
