Gro

co.usegroPublished by usegro.coOfficial publisherv1.0.0Updated Oct 24, 2026

Manage subscriptions, customers and email campaigns in your Gro account.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant manage subscriptions, customers and email campaigns in a Gro account through a hosted remote endpoint.

What you can do
Gro exposes a remote MCP endpoint that connects an assistant to a Gro account so it can work with subscriptions, customers and email campaigns. The registry description states it is for managing those records in your Gro account. No individual tools are listed in the supplied manifest, so the exact operations are not documented here.
When to use it
Worth adding when you already use Gro for subscriptions, customer records or email campaigns and want an assistant to read or manage that data without leaving the chat. It is less useful if you do not have a Gro account or do not need campaign or subscriber management.
Requirements
A remote MCP endpoint at api.usegro.co over streamable HTTP, reachable from the client. Authentication is OAuth and is required; no environment variables or headers are declared. A Gro account is implied by the account-scoped description.
Before you install
The server is account-scoped and authenticated by OAuth, so granting it access exposes your Gro customer, subscription and campaign data to the assistant. Campaign and customer management can change or send data; the manifest lists no tools, so confirm the exact write and send actions before authorizing.

Installation

In SourceWeft

  1. Open Gro in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/co.usegro%2Fgro/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 17, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.