Connect Your AI Assistant to ExpenseBot

What is the ExpenseBot MCP server?

MCP — the Model Context Protocol — is an open standard that lets AI assistants plug into outside tools and data using one consistent interface. Instead of every product building a one-off Claude plugin or ChatGPT plugin, the product publishes an MCP server and any MCP-compatible client speaks to it. Anthropic introduced the protocol in late 2024; it now ships natively in Claude Desktop, Cursor, Continue, and a growing list of clients.

ExpenseBot publishes two MCP servers on npm. The first, @expensebot/mcp-server, is read-only and unauthenticated — it exposes the public knowledge base and feature documentation so an AI assistant can answer "what is ExpenseBot?" or "does it work with Sage 50 Canada?" without any login. Useful for evaluation and for AI agents that want to cite our capabilities. The second, @expensebot/mcp-server-auth, is the full account-scoped version: 21 tools across search, capture, Gmail scan, reports, and analytics, all gated behind a personal access token you generate in Settings. This is the one most users want — it talks to your actual receipts, your actual Google Sheet, and your actual spending history. Both are listed on the official MCP Registry and ship under the verified publisher namespace.

What can my AI assistant do?

Once connected, you can ask in plain English. Some example prompts that all work today:

• "Find every Uber receipt I expensed last quarter."
• "Submit this photo as a $42 client lunch yesterday." (drag a photo into Claude)
• "Scan my Gmail for new receipts from the last 30 days."
• "What were my top 5 software vendors in Q1?"
• "Generate a Schedule C report for 2025 and share it with my accountant."
• "I paid $80 cash for parking at the airport — log it."
• "Run a deep analytics report and surface anything unusual."

Behind the scenes, those prompts route to one of 21 tools exposed by the authenticated server, grouped into six categories:

You don't call these tools by name — Claude picks the right one based on what you ask. The list is here so you know what's possible. Power users link the MCP from their freelancer workflow so their AI assistant becomes the front-end for bookkeeping.

How to connect it (3 minutes)

1. Generate a token. In ExpenseBot, go to Settings → AI Assistant Tokens → Generate. Copy the token — it's shown once. Tokens are scoped to your account and can be revoked any time.
2. Add to Claude Desktop config. Open the config file in any text editor:
   • Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json

   Paste this block (replace the token):

   {
     "mcpServers": {
       "expensebot": {
         "command": "npx",
         "args": ["-y", "@expensebot/mcp-server-auth"],
         "env": {
           "EXPENSEBOT_TOKEN": "your-personal-access-token-here"
         }
       }
     }
   }

   Just want the read-only docs server? No token needed:

   {
     "mcpServers": {
       "expensebot-docs": {
         "command": "npx",
         "args": ["-y", "@expensebot/mcp-server"]
       }
     }
   }

3. Restart Claude Desktop and test. Fully quit and reopen Claude. Try "show me my top 5 software vendors last quarter". Claude will ask permission to run the get_spending_summary tool — approve once, and the integration is live.

Why use AI Assistant access?

• Faster than the dashboard for ad-hoc questions. "What did I spend at Costco last month?" is one sentence in Claude versus four clicks in the UI.
• No app switching. If you live in Claude or Cursor for writing and code, your expense answers come to you.
• Conversational receipt submission. Drag a photo into chat, say what it was for, and it lands as a row in your sheet — categorized, with vendor and total extracted.
• Complex analytics in natural language. get_deep_analytics surfaces top vendors, anomalies, month-over-month deltas and unusual spend without you writing a single SQL query or pivot table.
• Cash entry by description. "$80 cash for airport parking yesterday" becomes a properly tagged cash expense with date, amount, category, and notes.

Security & token model

Personal access tokens (PATs) are the one credential the MCP server cares about. Each token is scoped to your account only — it can't read another user's data, even if leaked. Tokens have a configurable expiry you choose at issue time, and you can revoke any token from Settings → AI Assistant Tokens with immediate effect (the next request fails 401). Token issuance, use, and revocation are audit-logged in Firestore against your account so you can review what was used when. Tokens themselves are stored hashed (SHA-256) — even ExpenseBot staff can't read the original string out of the database.

Your underlying expense data never moves. Receipts stay in your Google Drive, your sheet stays in your Drive, and each MCP tool call reads or writes those files using your existing OAuth grants. The only data that flows through your AI provider is the specific tool result your assistant asked for — same trust model as any LLM tool-use call. If you're inviting an accountant later, the share happens through Google Drive sharing, not through the MCP token.

Compatible AI assistants

MCP support is growing quickly. Today the ExpenseBot MCP works out of the box with:

• Claude Desktop — Mac, Windows, Linux. Native MCP support since 2024.
• Cursor IDE — Mac, Windows, Linux. Add via Settings → MCP.
• Continue (VS Code / JetBrains extension) — open-source MCP client.
• ChatGPT — paid plans with native MCP support.
• Custom agents built on the Anthropic, OpenAI, or open-source MCP SDKs.

If your client follows the MCP wire format (JSON-RPC over stdio), ExpenseBot works. The official and constantly-updated client list lives at modelcontextprotocol.io/clients.

Why this matters

Most expense apps see receipts. The ExpenseBot MCP lets your AI act on them — search, submit, scan Gmail, generate a tax report, share it with your accountant — using your actual Google Sheet as the source of truth. There's no separate mirror database to drift, no proprietary ledger to escape from, no "export to CSV" step. Your AI assistant reads the same sheet you read, writes the same rows you'd write, and triggers the same Gmail scanner you'd trigger from the dashboard.

That's the Gmail-Sheets-native angle. ExpenseBot was built from day one around the data your life already runs on — receipts in Gmail, ledger in Google Sheets, files in Drive — instead of on a closed app database. The MCP server inherits that. When you ask Claude to scan Gmail for new receipts, it triggers the same scanner that runs nightly. When it submits a receipt, the row lands in the sheet you already own. We're listed on the official MCP Registry at io.github.TotesMagotes/mcp-server-auth so registry-aware clients can find us automatically.

See pricing plans for full feature breakdown. The MCP servers are public on npm; account-scoped tools require an active ExpenseBot account.

Frequently asked questions