Connect Claude or Codex to your firm.
Install the open-source Grove plugin in Claude, Codex, or Cursor. Your assistant lists returns, reads fact sheets, pulls document checklists, and imports Lacerte / Drake backups against your firm.
~/Downloads/smiths-2024.zip — what should I ask them to send me for 2025?
- W-2 · Publix Super Markets Inc
- 1099-DIV · Charles Schwab 3656 (Teresa)
- 1098 mortgage · Wells Fargo
- + 8 more rolled forward from last year
One click in your assistant.
Grove ships as an open-source plugin at grove-tax/grove-mcp. Sign in to Grove once on first use and the plugin is wired to your firm.
The plugin is in private beta. It installs once we've enabled your firm — we approve new firms manually, usually the same business day.
Add to Cursor
Cursor opens, registers Grove as an MCP server, and prompts a browser sign-in on first tool call. Drop the matching skill into ~/.cursor/skills/ from the repo for the best experience.
Open in Claude
Opens Claude's Connectors settings. Click Add custom connector, paste the URL https://app.grove.tax/api/mcp, name it grove, save. Sign in opens in your browser.
Plugin marketplace
Two slash commands inside a Claude Code session install the marketplace plus Grove (MCP + skill bundled). First tool call opens a browser sign-in.
/plugin marketplace add grove-tax/grove-mcp /plugin install grove@grove
Plugin marketplace
Add the marketplace, then install Grove from the Codex plugins panel. Browser sign-in on first use.
codex plugin marketplace add \ https://github.com/grove-tax/grove-mcp.git
Imports today: Lacerte and Drake backups. More tax software is on the way.
Prefer to configure the MCP server manually? Point any MCP-aware client at https://app.grove.tax/api/mcp (transport: http) — the sign-in flow is auto-discovered.
How to ask.
The plugin gives your assistant five tools against your firm. You don't address them by name — you just say what you want. Below: what each tool does, and six prompts to try.
-
list_returnsList the firm's returns. Filter by tax year or workflow status.
-
read_fact_sheetRead a return's basics — taxpayer, dependents, filing status, contact.
-
get_checklistPull the document checklist for one return, item by item.
-
request_upload_urlSigned URL for uploading a local Lacerte or Drake backup.
-
upload_returnRun the import; returns the new return IDs and Grove URLs.
Try asking
Each of these works today. Paste any of them into Claude or Codex once you're connected.
Roll one client forward
Drop a client's prior-year backup. The assistant imports the return and hands back this year's document checklist, derived from what they filed last year.
Roll a whole firm forward
Drop a multi-client backup. Every return that imports is yours to work with in the same conversation — pull a checklist, draft a reminder, compare two.
Cross-reference your book
Plain-English questions across every return your firm has. The assistant lists what it can see and answers without you naming a single client.
Catch up the late clients
Filter for returns still awaiting documents, then draft a personalized reminder per family — naming each specific employer, payer, or property.
Triage what's ready to prepare
Sort the book by what's missing. Pick the week's work without clicking into every return.
Compare two clients
Useful for sanity-checking a complex return against a reference family, or spotting changes from prior year.
Things that come up.
I installed the plugin but sign-in fails.
Your firm probably isn't enabled for MCP yet. Email support@grove.tax with your firm name and we'll flip it on — usually the same business day.
Which assistants are supported?
Anything that speaks the Model Context Protocol over Streamable HTTP — Claude Code, Claude Desktop, Claude.ai, the OpenAI Codex CLI, Cursor, and anything you build yourself. The plugin repo at grove-tax/grove-mcp documents each setup path.
Should I install the skill too, or just the connector?
The skill teaches the assistant how to use Grove well — when to import vs. read, how Drake and Lacerte backups differ, how to phrase a follow-up email. Without it the connector still works, but the assistant will ask more clarifying questions. Claude Code and Codex bundle both via the plugin marketplace; Claude Desktop and Cursor need the skill uploaded separately.
An import came back as "Import failed."
The backup couldn't be decoded — usually a corrupt or incomplete Lacerte / Drake export. Re-export the backup and try again. If it still fails, send the file to support@grove.tax.
What does "partially completed" mean on an import?
It means at least one return in the backup failed to import — the ones that succeeded are still in the response. Open the imported returns in Grove and email support@grove.tax about the missing ones.
Does the assistant see my client data?
Return information lives in Grove. The MCP currently sends a small subset to your assistant — names, contact info, last-4 SSN, and the document checklist. Document bytes also stay out of the chat — they go directly from your machine to Grove's storage via a one-time pre-signed URL.
How do I disconnect or revoke access?
Remove the plugin from your assistant (e.g. /plugin uninstall grove@grove in Claude Code, or remove the connector from Claude.ai). To kill an active session server-side, email support@grove.tax and we'll revoke the firm's access.
Ready to wire up your firm?
The MCP is rolling out one firm at a time. Join the waitlist and we'll be in touch, usually the same business day.