# Introduction

> Connect Claude, Cursor, VS Code, Windsurf and ChatGPT to Grovs through the Model Context Protocol.

Source: https://docs.grovs.io/docs/ai/mcp/introduction

Grovs runs a [Model Context Protocol](https://modelcontextprotocol.io/) server. If your AI assistant supports MCP, you can point it at Grovs and ask it to create deep links, pull analytics, or change project settings without opening the dashboard.

The server is open source. Code, issues, and contributions live at [github.com/grovs-io/mcp](https://github.com/grovs-io/mcp).

## What the assistant can do

Once it is connected, the assistant has 16 tools. The most common things people ask for:

- Create, update, search, and archive deep links
- Group links into campaigns and pull aggregated metrics
- Read project-wide analytics or per-link analytics for a date range
- Set platform fallback URLs and SDK configuration (bundle IDs, package names, App Store ID)
- Spin up new projects without leaving the chat

The server does not cover segments, push campaigns, in-app messages or journeys yet. Manage those in the dashboard.

For the full list of tools and parameters, see the [Tools Reference](https://docs.grovs.io/docs/ai/mcp/tools-reference). For example prompts and what they actually do, see [Examples & Recipes](https://docs.grovs.io/docs/ai/mcp/examples).

## Supported clients

| Client                       | Setup                                                                           |
| ---------------------------- | ------------------------------------------------------------------------------- |
| Cursor                       | One-click install, or [manual setup](https://docs.grovs.io/docs/ai/mcp/cursor)  |
| VS Code (Copilot agent mode) | One-click install, or [manual setup](https://docs.grovs.io/docs/ai/mcp/vs-code) |
| Claude Code                  | [One command](https://docs.grovs.io/docs/ai/mcp/claude-code)                    |
| Claude Desktop and Claude.ai | [Custom connector](https://docs.grovs.io/docs/ai/mcp/claude-desktop)            |
| ChatGPT                      | [Developer mode connector](https://docs.grovs.io/docs/ai/mcp/chatgpt)           |
| Windsurf                     | [Guide](https://docs.grovs.io/docs/ai/mcp/windsurf)                             |

The one-click buttons are on [Build with AI](https://docs.grovs.io/docs/ai#connect-the-mcp-server) and in the page menu of every docs page, under **Connect the grovs MCP server**.

All clients connect over Streamable HTTP at the `/mcp` endpoint.

## Server URL

```
https://mcp.grovs.io/mcp
```

If you self-host Grovs, run the MCP server yourself; see [Self-hosted MCP](https://docs.grovs.io/docs/ai/mcp/self-hosted).

## Authentication

Grovs uses OAuth 2.1 with PKCE. The first time you connect, your AI tool registers with Grovs, opens a browser, and asks you to approve the connection from the Grovs dashboard. After that, tokens refresh automatically.

## Revoking access

You can disconnect any AI tool from your Grovs account at any time. Revoking access invalidates the token immediately — the tool will need to go through OAuth again to reconnect.

### 1. Open Connected Apps

Sign in to the [Grovs dashboard](https://app.grovs.io) and go to **Account Settings → Connected Apps**.

You'll see every AI tool that currently has access to your account, including when it was added and when it was last active.

### 2. Revoke the token

Find the tool you want to disconnect and click **Revoke**. Confirm the dialog.

The token is invalidated on the server immediately. Any in-flight requests from that tool will fail with a 401, and the tool will either prompt for a fresh OAuth login or silently stop working until you reconnect it.

### 3. Reconnect if needed

If you revoked by accident, just start a new session in the AI tool — it will detect the missing token and trigger the OAuth flow again. No reinstall required.

### When to revoke

- You're no longer using the tool and want to clean up access
- You suspect a device or account has been compromised
- You want to rotate credentials after a team member leaves
- You're moving from one AI tool to another and want to make sure the old one can't keep calling the API

> **Note:** Revoking on the Grovs side is the nuclear option — it cuts access immediately. Most AI tools also let you remove the MCP server from their side (via their own settings), but that alone doesn't invalidate the token. Always revoke from **Connected Apps** if you want to be sure.

## Next steps

- [Cursor](https://docs.grovs.io/docs/ai/mcp/cursor), [VS Code](https://docs.grovs.io/docs/ai/mcp/vs-code), [Claude Code](https://docs.grovs.io/docs/ai/mcp/claude-code), [Claude Desktop](https://docs.grovs.io/docs/ai/mcp/claude-desktop), [ChatGPT](https://docs.grovs.io/docs/ai/mcp/chatgpt), [Windsurf](https://docs.grovs.io/docs/ai/mcp/windsurf)
- [Example prompts](https://docs.grovs.io/docs/ai/mcp/examples)
- [Tools reference](https://docs.grovs.io/docs/ai/mcp/tools-reference)