Skip to content

Connect an AI assistant

Gro runs a remote MCP (Model Context Protocol) server. Any assistant that speaks MCP can connect to it and look up subscriptions, check campaign performance, manage customers and draft email templates against your own Gro account.

https://api.usegro.co/mcp

The server uses Streamable HTTP and OAuth 2.0. You sign in with your normal Gro login. There are no API keys to copy around.

Gro is in the Claude connectors directory, so it is a one click install from Settings then Connectors. Full steps, including Claude Code, are on Connect Gro to Claude.

  1. Open Cursor Settings, then MCP, then Add new MCP server.
  2. Choose the URL transport and paste https://api.usegro.co/mcp.
  3. Cursor opens the Gro login page. Sign in, pick your store if you have more than one, and approve.

Or add it to .cursor/mcp.json:

{
"mcpServers": {
"gro": { "url": "https://api.usegro.co/mcp" }
}
}

Run MCP: Add Server from the command palette, choose HTTP, and paste the URL. VS Code handles the OAuth login in your browser. You can also drop this into .vscode/mcp.json:

{
"servers": {
"gro": { "type": "http", "url": "https://api.usegro.co/mcp" }
}
}

In ChatGPT go to Settings, then Connectors, then Create. Enter the server URL, choose OAuth, and follow the login. ChatGPT connectors are available on paid plans and may need developer mode switched on by your workspace admin.

Point it at the URL above using the Streamable HTTP transport. The server publishes standard OAuth discovery at https://api.usegro.co/.well-known/oauth-protected-resource, so any client that supports OAuth 2.1 with dynamic client registration or client ID metadata documents will find the login on its own.

  • “How are subscriptions doing this month? Active, new and churned.”
  • “Find the subscription for jane@example.com and tell me when her next delivery is.”
  • “Move Jane’s next delivery to next Thursday.”
  • “How did the Spring Sale campaign do?”
  • “Draft a win back email in our brand style using our best sellers.”

The assistant acts as you, in the store you pick when you sign in. It can reach exactly what you can reach in the dashboard, and nothing in any other store.

Tools that change data are annotated as such, so assistants know to confirm before using them. Every action is logged in the Gro activity feed under your name, the same as if you had done it yourself.

Remove the server in your assistant’s settings. Gro stops accepting requests from that connection straight away.

See the MCP tools reference.