Grovs IO MCP

What grovs-io/mcp MCP server does

grovs-io/mcp MCP server gives AI assistants access to Grovs operations for mobile-app growth workflows. Grovs supports deep links that can route users across iOS, Android, and web, along with install attribution, revenue analytics, and campaign organization. The MCP interface lets an assistant manage these functions without requiring the developer to leave an MCP-compatible editor or client.

The server exposes 16 tools. Account and project administration includes status, usage, and project creation operations. Link management covers creation, lookup, updates, searching, and irreversible archiving. Analytics tools return project-level metrics such as views, installs, opens, and revenue, as well as daily per-link data and rankings for top links. Campaign tools group links and report aggregated metrics. Configuration tools handle per-platform redirects and iOS or Android SDK settings.

How it works

The hosted service is available at https://mcp.grovs.io/mcp. MCP clients communicate with the server over HTTP. Internally, the application registers tool schemas, validates inputs, runs authenticated handlers, formats API responses, and makes HTTP requests to the Grovs backend.

On first use, the client starts an OAuth flow and opens a browser for Grovs account authentication. The README states that API keys are not needed for the hosted setup. The server can also be run locally for a self-hosted Grovs backend, with the MCP endpoint exposed at the local server URL.

Setup and configuration

For a hosted connection, add https://mcp.grovs.io/mcp to an MCP client. Cursor uses an MCP server URL, while Windsurf uses the equivalent serverUrl setting. Claude Code provides a Grovs plugin installation flow. Other clients can connect if they support the MCP HTTP configuration required by the client.

A local deployment can be built from the repository with npm install, npm run build, and npm start, or built and run with Docker. The PORT variable controls the listening port and defaults to 8080. GROVS_API_URL selects the Grovs backend and defaults to https://mcp.grovs.io; it can be changed for self-hosted deployments. PUBLIC_URL identifies the MCP server’s public address for OAuth callbacks and defaults to http://localhost:8080.

Tools and capabilities

The grovs-io/mcp MCP server includes these tool groups:

• Inspect account status, instances, projects, domains, usage, and subscription status.
• Create an instance with production and test projects.
• Create, inspect, update, search, and archive deep links.
• Attach link metadata, tags, custom data, and redirect settings.
• Review project metrics, daily link analytics, and top links by views.
• Create, list, and archive campaigns; archiving a campaign also deactivates its links.
• Set App Store, Play Store, and web redirect behavior.
• Configure iOS and Android SDK values such as bundle IDs and team IDs.

Limitations and notes

Archiving a link is irreversible according to the tool description. Archiving a campaign also deactivates its associated links, so these operations should be used with care.

The hosted configuration depends on Grovs account authentication through OAuth. Self-hosting the MCP application does not by itself describe how to provision or operate the separate Grovs backend; the README points to Grovs’s backend repository for that use case. The project is licensed under MIT.

The grovs-io/mcp MCP server manages Grovs resources and settings, but the provided material does not describe tools for editing mobile application source code or implementing the platform SDKs themselves.