Most of what a Grover partner does in a week is small and repetitive. Check which knowledge bases are linked to which rig assistant. Look at what customers actually asked their assistant about. Fix a number in a rig template. Schedule a message to your Circle before a holiday weekend.
All of that lives in your dashboard at admin.getgrover.ai, and the dashboard is not going anywhere. But if your team already works in Claude, you can do the same things by asking for them in plain language instead of clicking through screens. That connection is called MCP, and Grover runs a server for it.
This post covers what MCP is, what Grover's connector actually does, and the two ways to add it. Setup is genuinely short. One of the two paths is a single command.
What MCP Actually Is
MCP stands for Model Context Protocol. It is an open standard for connecting AI applications to outside systems, so a tool like Claude can read real data and take real actions instead of guessing from whatever you paste into a chat window.
The official documentation describes it as a USB-C port for AI applications, which is a good way to hold it. Every integration used to be custom work on both ends. With MCP, a company builds one server and any client that speaks the protocol can use it. Claude speaks it. So do ChatGPT, VS Code, Cursor, and a growing list of others.
If you want the source material rather than our summary, these are the official ones:
- modelcontextprotocol.io for the plain-language introduction to what MCP is and why it exists
- The architecture overview for how clients, servers, and tools fit together
- The specification if you or your developer want the actual protocol
- Claude Code's MCP documentation for the client side, including every command in this post
- Custom connectors in the Claude apps for adding a server in Claude on the web or desktop
The short version. An MCP server hands an AI client a list of tools it is allowed to call. Grover's server hands Claude a list of things you are allowed to do with your own company's data, and nothing else. Your role decides that list, not the AI.
What Grover's Connector Does
Grover's MCP server lives at https://ops.getgrover.ai/mcp. It is the same backend your dashboard talks to, reached a different way. There is no separate data, no export, no copy of your account sitting somewhere else.
When you connect, Claude gets access to the companies your Grover account already covers. If you are a company owner at one van shop, you see one company. Nothing about the connector widens what you can reach. It reads the same permissions record your dashboard login uses, on every single request, which matters for the revoking part further down.
What that looks like in practice is asking for the thing instead of navigating to it. "Which knowledge bases are linked to my Sprinter assistant?" "Summarize what customers asked about last month." "Update the fresh water capacity on the 144 template to 21 gallons." Claude calls the matching tool, you see the result, and the change lands in the same place a dashboard edit would.
Two Ways to Add It
Both paths end in the same place. Pick based on which Claude you use.
Option 1: The plugin, from GitHub
We publish Grover as a Claude Code plugin, and the repository serves as its own marketplace. That means two commands and you are done. Run these inside Claude Code:
/plugin marketplace add GoCode-Overland/grover-claude-marketplace
/plugin install grover@grover-marketplace
The first command points Claude Code at our repository. The second installs the plugin, which carries the connector's address with it. You never type a URL, and when we change something on our end, you get it by updating the plugin rather than by editing config.
The repository is public and small enough to read in a minute: github.com/GoCode-Overland/grover-claude-marketplace. Two manifest files and a README. Nothing is hidden in it, which is the point of putting it on GitHub instead of mailing you a config blob.
Option 2: Straight from the URL
You do not need the plugin. The connector is a standard remote MCP server, so any client that supports one can add it directly.
In Claude Code, that is one command:
claude mcp add --transport http grover https://ops.getgrover.ai/mcp
Add --scope user on the end if you want it available in every project rather than the current one.
In the Claude apps on web or desktop, go to Customize > Connectors, click the + button, choose Add custom connector, and paste the same URL. Team and Enterprise accounts work a little differently: an owner adds it once under organization settings, then each member connects individually to sign in.
Signing in
Either way, the first time you use the connector your browser opens and you sign in to Grover. That is OAuth, the authentication method built into the MCP standard. There is no API key to generate, paste, or store anywhere. Claude handles the token itself and refreshes it on its own, so there is nothing to rotate later.
If the browser does not open on its own, run /mcp inside Claude Code and start the sign-in from there. The same menu shows whether the server is connected and lets you clear the authentication when you want to.
What You Can Actually Do With It
The connector covers most of the partner surface. Reads are open to anyone on your team with dashboard access. Writes need a role that could make the same change in the dashboard, which means a viewer account can look at everything and change nothing.
| Area | What you can do from Claude |
|---|---|
| Rig templates and specs | Read a rig template or an individual customer's spec sheet, and update either one |
| Assistants | List them, read their configuration, create one, update one |
| Knowledge bases | See what exists, see what is linked to which assistant, link and unlink them, check processing status |
| Chat activity | List chat sessions, open one, or ask for a summary of what your customers have been asking about |
| Circles | Read members, pins, and the feed, and update Circle details |
| Notifications | Schedule a one-time message to your Circle, cancel one, and pause or resume a recurring one |
| Invites and builder codes | List, create, and revoke, for company owners |
| App users and company | See who from your company is on Grover, read your company record, update it |
The summary tool is the one partners tend to underestimate. Your customers are asking their rig assistant questions all day, and those questions are the clearest signal you will get about what your documentation is missing. Asking Claude for a summary of last month's sessions takes about ten seconds and reads like a support report you did not have to write.
Access, Limits, and Revoking
A few honest boundaries, because a connector that quietly does less than you expect is worse than one with a clear edge.
It needs a dashboard account. The connector authenticates against the same permissions record your dashboard login uses. A customer with the mobile app and no dashboard account gets nothing from it. If someone on your team should have access, add them in the dashboard first.
Your role still decides everything. Company owners can do the most, company admins slightly less, viewers can read only. Some actions are owner-only by design, including linking a knowledge base, editing a rig template, and creating or revoking invites and builder codes. Claude will tell you plainly when your role does not allow something rather than half-doing it.
Adding documents is still a dashboard job. You can link and unlink knowledge bases from Claude, and you can check whether a file finished processing. Uploading the file itself happens in admin.getgrover.ai, one file at a time. Do the upload there, then wire it up from wherever you prefer.
Recurring messages get managed, not created. You can schedule a one-time notification from Claude, and you can list, pause, and resume recurring ones. Setting up a new recurring schedule happens in the dashboard.
Edits do not force a re-match. This is the same caveat that applies to dashboard edits. Changing a rig template or a customer's spec sheet does not immediately redo that customer's document recommendations. Those catch up overnight, or sooner if the customer edits their own specs in the app.
Revoking is immediate. The server re-reads your permissions on every request instead of trusting whatever was true when the token was issued. Remove someone's dashboard access and their connector stops working on the next call. There is no window where a stale token keeps working, and there is no separate key to hunt down and delete.
Worth saying out loud. This is the same account, the same permissions, and the same data as your dashboard. The connector is a second door into the room you already have keys to. It is not a new room.
Where to Start
If you have Claude Code, run the two plugin commands, sign in when the browser opens, and ask it to summarize your chat sessions from the last thirty days. That one request will tell you more about whether this is useful to you than any more reading will.
If you use Claude on the web or desktop instead, paste https://ops.getgrover.ai/mcp into a custom connector and do the same thing.
And if you would rather have someone walk you through it, book a success call. We will get the connector installed and go through your knowledge bases and your rig template while we are in there.
Want a Hand Setting It Up?
Grab a slot and we will install the connector together, then go through your knowledge bases and rig template. Takes a few minutes.
Schedule a Success CallYour Customers' Side of This
Everything you manage through the connector shows up in one place: the app your customers already have. If you have not looked at it from their side lately, it is worth the download.