MCP MCP Server

MCP server for managing deep links, attribution, analytics, campaigns, and app configuration on Grovs — an open-source, privacy-first alternative to

Remote serverstreamable-httpTypeScript

What is the MCP MCP server?

MCP server for managing deep links, attribution, analytics, campaigns, and app configuration on Grovs — an open-source, privacy-first alternative to Branch and AppsFlyer. That is what the mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

Grovs is an open-source, privacy-first growth platform for mobile apps — a self-hostable alternative to Branch.io and AppsFlyer. It provides:

The tools it exposes

The server publishes 14 tools. What each one is for:

  • get_status — Account info, instances, projects, and domains
  • get_usage — Usage metrics and subscription status for an instance
  • create_project — Create a new instance with production and test projects
  • create_link — Create a deep link with metadata, tags, and custom data
  • get_link — Get full details of a link by path
  • update_link — Update a link's metadata, tags, or redirects
  • archive_link — Deactivate a link (irreversible)
  • search_links — Search and list links with pagination and filters
  • get_analytics_overview — Project-level metrics: views, installs, opens, revenue
  • get_link_analytics — Per-link daily metrics
  • get_top_links — Top performing links ranked by views
  • create_campaign — Create a campaign to group related links

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

What it needs from you

Configuration is passed through the environment: GROVS_API_URL, PUBLIC_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — get_status, get_usage, create_project and 11 more — is a fair guide to whether it matches your workflow. It is maintained by grovs-io; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
get_statusAccount info, instances, projects, and domains
get_usageUsage metrics and subscription status for an instance
create_projectCreate a new instance with production and test projects
create_linkCreate a deep link with metadata, tags, and custom data
get_linkGet full details of a link by path
update_linkUpdate a link's metadata, tags, or redirects
archive_linkDeactivate a link (irreversible)
search_linksSearch and list links with pagination and filters
get_analytics_overviewProject-level metrics: views, installs, opens, revenue
get_link_analyticsPer-link daily metrics
get_top_linksTop performing links ranked by views
create_campaignCreate a campaign to group related links
list_campaignsList campaigns with aggregated metrics
archive_campaignArchive a campaign and deactivate its links

How to install the MCP MCP server

{
  "mcpServers": {
    "grovs": {
      "url": "https://mcp.grovs.io/mcp"
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
GROVS_API_URLEndpoint or connection string the server talks to.Yes
PUBLIC_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use MCP to get status.
  • Use MCP to get usage.
  • Use MCP to create project.

Frequently asked questions

It connects MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (get_status, get_usage, create_project, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP directly.