ExpenseBot

How do I give a desktop or custom AI agent access to ExpenseBot through MCP?

Use the connection method your AI client supports. The full public chooser is at expensebot.ai/mcp#choose-connection.

Use the connection method your AI client supports. The full public chooser is at expensebot.ai/mcp#choose-connection.

ChatGPT or Claude.ai

Install ExpenseBot from the assistant's directory, click Connect, then complete ExpenseBot sign-in and consent. These hosted connectors use OAuth. Do not generate or paste a personal token.

Viktor or another remote/custom agent

If the agent supports remote HTTP MCP with OAuth, add this server URL:

https://mcp.expensebot.ai/mcp

The agent should open ExpenseBot's browser sign-in and consent flow. Leave manual OAuth client-ID and client-secret fields blank when the client supports Dynamic Client Registration. Approve only the scopes the agent needs, then verify the connection with a read-only expense question before allowing writes.

If the agent does not support remote OAuth MCP, use the local/stdio setup below.

Claude Desktop, Cursor, or another local/stdio agent

  1. Sign in to ExpenseBot and open AI Assistant Tokens.

  2. Generate a new token named for that agent or device. The token is shown once and can be revoked at any time.

  3. Configure the client to run:

    npx -y @expensebot/mcp-server-auth
    
  4. Store the token as the EXPENSEBOT_TOKEN environment secret in the client's MCP configuration. Do not put it in command arguments or paste it into an AI conversation.

  5. Restart the client. Confirm ExpenseBot appears in its tool list, then ask a read-only question such as: "Show my top five expense categories this month."

Example configuration:

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

Prompt an AI can use to help configure itself

Paste this prompt only into an AI that can inspect or guide its own MCP configuration. It must still leave sign-in, consent, and secret entry to you:

Help me connect this AI client to ExpenseBot through MCP.

1. First determine whether this client supports remote HTTP MCP with OAuth, or only local stdio MCP.
2. For remote OAuth MCP, add https://mcp.expensebot.ai/mcp and let me complete ExpenseBot sign-in and consent in the browser. Do not ask for a client secret.
3. For local stdio MCP, use: npx -y @expensebot/mcp-server-auth. Tell me where this client's MCP configuration lives, then have me store a newly generated ExpenseBot token as the EXPENSEBOT_TOKEN environment secret.
4. Never ask me to paste the token into chat. Never print, log, or save it in command arguments.
5. Verify the connection by listing tools and running one read-only request: "Show my top five expense categories this month."
6. Do not run any write action unless I explicitly approve it.

An AI without access to its own client settings cannot install the connection by itself; it can only guide you. Never send a token by email or chat.

Revoke or rotate access

Open AI Assistant Tokens, revoke the old token, generate a new one, update the client's EXPENSEBOT_TOKEN, and restart the client. Remote OAuth connections are managed from the assistant's connector settings and ExpenseBot's authorization screen.

For practical questions to try after setup, use the ExpenseBot AI prompt guide.

Share:

Try ExpenseBot Free

AI extracts every receipt into a Google Sheet you own. Gmail scan, mileage, tax reports, profit-by-client. No credit card needed.

No credit card required · Setup in 30 seconds