Summary

Link creation and the numbers behind it, in the same place.

The pairing is what earns its keep: create a campaign, generate its links with the right per-platform redirects, then come back later and read installs and revenue against them without opening a dashboard. Setup is a URL and an OAuth prompt, and if you self-host the backend the same server points at your own instance.

What it is

The MCP server for Grovs, an open-source, privacy-first growth platform for mobile apps — deep linking, first-party attribution and revenue analytics, self-hostable as an alternative to the usual vendors. This server exposes the platform to an assistant: links, analytics, campaigns and SDK configuration.

What you get

Links: `create_link`, `get_link`, `update_link`, `search_links`, and `archive_link` — which deactivates irreversibly
Analytics: `get_analytics_overview` for views, installs, opens and revenue; `get_link_analytics` for per-link daily figures; `get_top_links` for a ranking
Campaigns: `create_campaign`, `list_campaigns` with aggregated metrics, and `archive_campaign`
Configuration: `configure_redirects` for per-platform behaviour across App Store, Play Store and web, and `configure_sdk` for bundle ID and team ID
Account level: `get_status` for instances, projects and domains; `get_usage` for metrics and subscription status; `create_project` to stand up production and test projects

Requirements

No API key. Point your client at https://mcp.grovs.io/mcp and a browser window opens for OAuth on first use — configuration snippets are given for Cursor, Windsurf, VS Code and ChatGPT Desktop, and Claude Code installs it as a plugin with skills included. Running against your own Grovs backend means `npm install && npm run build` or the Docker image, with `PORT`, `GROVS_API_URL` and `PUBLIC_URL` set; `PUBLIC_URL` is what the OAuth callback comes back to. MIT licensed.

Setup effort

One command — npx -y mcp-remote https://mcp.grovs.io/mcp