Grove

Grove — AI Plugin

Connect Claude, Codex, or Cursor to your firm in Grove. Once installed, your AI assistant can read your returns, summarize fact sheets, generate "still missing these documents" emails, and import Drake / Lacerte backups directly — all scoped to your firm via OAuth (no API keys to paste).

Prerequisite for all install paths: your firm needs the MCP feature enabled. Contact Grove support ([email protected]) to turn it on for your firm.

Install in Claude Code (bundled — connector + skill in one step)

This repo is a Claude Code plugin marketplace. One command adds the marketplace; one more installs Grove (skill + MCP connector together):

/plugin marketplace add grove-tax/grove-mcp
/plugin install grove@grove

After install, run /reload-plugins. Grove's MCP tools and the grove skill are now available. First tool call triggers OAuth in your browser.

Install in Claude.ai / Claude Desktop

Claude.ai and the Desktop app don't have a bundled "connector + skill" install path today. You install the two pieces separately:

1. Connector (required)

1. Go to Settings → Connectors → Add custom connector (direct link)
2. Paste the URL: https://app.grove.tax/api/mcp
3. Name it grove
4. Save. Claude opens a browser for OAuth sign-in.

2. Skill (recommended)

Upload plugins/grove/skills/grove/ from this repo via Settings → Capabilities → Skills in Claude.ai or Claude Desktop. The skill teaches Claude how to use the connector well (when to import vs. read, how Drake and Lacerte backups differ, how to phrase a client follow-up email). Without the skill the connector still works, but Claude will ask more clarifying questions.

Install in Codex (bundled — connector + skill in one step)

This repo is also a Codex plugin marketplace. One command:

codex plugin marketplace add https://github.com/grove-tax/grove-mcp.git
# Then open the Plugins panel in Codex and install "Grove"
# (or use the CLI install flow)

First tool call triggers OAuth in your browser.

Direct clone (alternative)

If you'd rather skip the marketplace and drop the plugin into Codex's plugins directory directly, clone the repo somewhere and symlink just the plugin subdirectory in:

git clone https://github.com/grove-tax/grove-mcp.git ~/grove-mcp
ln -s ~/grove-mcp/plugins/grove ~/.codex/plugins/grove
# Restart Codex

(The plugin lives in plugins/grove/ inside the repo — not at the repo root — so the link points at the inner directory. The marketplace install above does the equivalent automatically.)

Connector-only (no plugin)

If you'd rather skip the plugin layer and just configure the MCP server directly, add this block to ~/.codex/config.toml:

[mcp_servers.grove]
type = "http"
url = "https://app.grove.tax/api/mcp"

This gives you the MCP tools without the skill (instructions). The skill is the part that teaches Codex how to use Grove well; the tools alone work but Codex will ask more clarifying questions.

Install in Cursor

Cursor reads the same skill format. Drop plugins/grove/skills/grove/ into ~/.cursor/skills/ (or your project's .cursor/skills/). For the connector itself, add the MCP server in Cursor's settings using the same URL:

https://app.grove.tax/api/mcp

Endpoint

Production MCP endpoint: https://app.grove.tax/api/mcp

Pointing at a different endpoint (for local development)

If you're testing against a local Grove dev server (e.g. behind a Cloudflare tunnel like https://your-tunnel.trycloudflare.com), edit plugins/grove/.mcp.json in your installed copy of the plugin and replace the URL:

{
  "mcpServers": {
    "grove": {
      "type": "http",
      "url": "https://your-tunnel.trycloudflare.com/api/mcp"
    }
  }
}

Restart Codex (or your client). The OAuth flow will run against whatever auth server the dev instance advertises in its protected-resource metadata.

Verify it's working

Once installed, ask your assistant:

What Grove MCP tools are available?

You should see five tools: list_returns, read_fact_sheet, get_checklist, request_upload_url, upload_return. If the list comes back empty, the OAuth flow either didn't run or got cached as failed — restart the client and try again.

What's in this repo