Everywhere your MCP client looks. The canonical ExpenseBot server is published across the major discovery surfaces, and they all point at the same production endpoints — so it doesn't matter which directory your client uses.
The listings
- Official MCP Registry — published as
io.github.TotesMagotes/mcp-server-auth, advertising both the remote OAuth endpoint (https://mcp.expensebot.ai/mcp) and the npm stdio package. This is the protocol-level source registries and catalogs consume. - Smithery — full metadata listing for Smithery-connected clients.
- Cursor's plugin directory — listed for Cursor users; install from the directory or use the npm stdio setup below.
- GitHub — the open-source client package, README, and
server.json. - npm —
@expensebot/mcp-server-auth, the stdio package for Claude Desktop, Cursor, and other local clients.
ExpenseBot is also in the ChatGPT app directory (Settings → Apps → search ExpenseBot) and Claude's connector directory — those hosted paths need no package at all: connect and sign in with OAuth.
Which one should you use?
You don't choose a directory — you choose a connection type, and the connection chooser picks the right path for your client:
- Hosted (ChatGPT, Claude.ai): install from the host's own directory, sign in, done.
- Remote OAuth (Gemini Spark, Zapier's MCP Client, custom agents): add
https://mcp.expensebot.ai/mcpand approve access in the browser — no client secrets, no token pasting. - Local stdio (Claude Desktop, Cursor): the npm package plus a revocable AI Assistant Token stored as an environment secret — never pasted into chat.
Whichever surface you start from, it's the same server, the same account, and the same Google Sheet you own. Revoke access anytime from AI Assistant Tokens or by disconnecting the OAuth grant.
Related
- What is an MCP connector? — the category explainer.
- Using ExpenseBot from AI assistants — capabilities and setup for every client type.