Revinho

Revinho MCP server

Revinho gives AI agents read-only access to the business intelligence in a Revinho workspace. It combines Google Analytics 4, Stripe, and optionally Google Search Console to answer what changed, what matters, what makes money, what is underperforming, and where to focus next.

This repository is the public discovery, connection, and support home for Revinho's hosted MCP server. The production server is operated by Revinho and is not deployed from this repository.

• MCP endpoint: https://www.revinho.com/api/mcp
• Transport: Streamable HTTP
• Authentication: workspace-scoped bearer token
• Documentation: revinho.com/docs
• Registry metadata: server.json

What it exposes

The server provides six focused tools:

Tool	Use it for
get_overview	Headline performance, period comparisons, trends, acquisition context, freshness, and deterministic signals
get_growth	Channels, sources, campaigns, countries, organic queries, and acquisition segments
get_funnels	Saved GA4 journeys and step-by-step funnel performance
get_pages	Page traffic, key events, conversion, search demand, classifications, and associated impact
get_revenue	Stripe-sourced revenue, MRR, subscriptions, customers, refunds, plans, and currency metadata
get_opportunities	Ranked deterministic opportunities with evidence and attribution provenance

Clients that support MCP prompts can also invoke investigate_business. It guides the agent through a bounded, evidence-led investigation and stops once the available facts answer the question.

Every tool is read-only, non-destructive, idempotent, and closed-world.

Connect

1. Sign in to Revinho and open Setup your agent.
2. Create a named workspace token. Tokens begin with rv_live_ and are shown once.
3. Add the hosted endpoint and token to an MCP-compatible client.

Generic configuration:

{
  "mcpServers": {
    "revinho": {
      "type": "streamable-http",
      "url": "https://www.revinho.com/api/mcp",
      "headers": {
        "Authorization": "Bearer rv_live_REPLACE_WITH_YOUR_TOKEN"
      }
    }
  }
}

Client configuration formats differ. Use the client's secret or environment-variable mechanism when it supports one. Do not commit the token to a repository.

Example questions

• What changed in the business over the last 30 days?
• Which acquisition channel deserves attention first?
• Did MRR growth coincide with a change in traffic or conversion?
• Where does the purchase funnel lose the most users?
• Which pages attract demand but underperform commercially?
• What is the highest-confidence opportunity right now?

Evidence boundaries

Agents using Revinho should preserve these product rules:

• Stripe is the source of truth for revenue.
• Revenue attached to acquisition or behavior retains its verified, modeled, or associated attribution label.
• Non-deterministic relationships are described as coinciding or associated, never causal.
• Provider freshness fields determine data freshness. Response generation time does not.
• Missing or partial data is not silently treated as zero.
• Opportunities come from deterministic rules and stored evidence.

Token safety

Revinho API tokens are read-only, workspace-scoped, stored as cryptographic hashes, and revocable.

• Create a separate token for each agent or environment.
• Keep tokens in a secret manager or private client configuration.
• Never place a token in a URL, prompt, screenshot, issue, log, or repository.
• Revoke a token immediately if it may have been exposed.

See SECURITY.md for reporting security issues.

Support

• Product and connection help: [email protected]
• Security reports: [email protected]
• Documentation: revinho.com/docs
• Repository issues: use GitHub Issues for public, non-sensitive documentation or compatibility problems

License

The documentation and metadata in this repository are available under the MIT License. Revinho's hosted service, product code, name, and brand assets are not granted under this license.