@randomfact/taz-mcp
v0.1.0
Published
Model Context Protocol server for the Transaction Analyzer API. OAuth 2.0 + PKCE; tools derived at startup from the published OpenAPI spec.
Downloads
18
Readme
@randomfact/taz-mcp
Model Context Protocol server for the Transaction Analyzer. Lets an MCP-aware client — Claude Desktop, Claude Code, MCP Inspector, anything that speaks MCP — read your transactions and create or edit categorization rules on your behalf.
Add one line to your MCP client config. The first time a tool needs data, the server pops your default browser to sign in with Google; once you've signed in, tokens are cached locally and the chat just keeps going.
Install
Claude Desktop
Add to claude_desktop_config.json (%APPDATA%\Claude\ on Windows,
~/Library/Application Support/Claude/ on macOS, ~/.config/Claude/ on
Linux):
{
"mcpServers": {
"transaction-analyzer": {
"command": "npx",
"args": ["-y", "@randomfact/taz-mcp"]
}
}
}Quit and reopen Claude Desktop (in-app reload won't pick up edits). Ask the chat "list my transaction categories". A browser tab pops on the first tool call, sign in with Google, the chat continues.
Claude Code
Register the server with claude mcp add. Scope it to your user so it's
available in every project:
claude mcp add transaction-analyzer --scope user -- npx -y @randomfact/taz-mcp(Drop --scope user to limit it to the current project, or use
--scope project to write a .mcp.json you can check into your repo.)
In a new Claude Code session, run /mcp to confirm transaction-analyzer is
connected, then ask the agent something. Same flow: browser pops once, you
sign in, the chat continues with results.
Other MCP clients
Anything that follows the MCP stdio transport protocol works the same way —
point it at npx -y @randomfact/taz-mcp with no other configuration.
Headless / SSH
For environments without a browser (SSH, containers, CI), pass --manual-code:
npx -y @randomfact/taz-mcp --manual-codeThe CLI prints the authorize URL to stderr — open it on any machine with a browser, sign in, then paste the resulting code on stdin.
Token cache
After the first sign-in, your access + refresh tokens are persisted to:
| Platform | Path |
|---|---|
| Linux | $XDG_CONFIG_HOME/transaction-analyzer-mcp/tokens.json (defaults to ~/.config/...) |
| macOS | ~/Library/Application Support/transaction-analyzer-mcp/tokens.json |
| Windows | %APPDATA%\transaction-analyzer-mcp\tokens.json |
The file is chmod 0600 on POSIX. Delete it to force a fresh sign-in —
useful if you've signed in with the wrong Google account.
What's NOT available via MCP
By design, two REST surfaces are not exposed as MCP tools:
- File upload (CSV / PDF bank statements). Upload via the SPA at
https://transaction-analyzer-prod.web.app. - CSV report download. Use the SPA's export menu, or call the list- transactions tool and format the rows yourself.
Everything else — list / create / update / delete categories and rules, search and override transactions, preview a rule, fetch the uncategorized report — is available as a tool. Your MCP client's tool picker shows the live list.
