expense_to_invoice — receipt scanner MCP Tool
expense_to_invoice
(expense to invoice) is one of 14 tools on the
receipt scanner
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call expense_to_invoice from your client
- Claude Code receipt scanner expense_to_invoice run in your project directory
- Claude Desktop receipt scanner expense_to_invoice ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor receipt scanner expense_to_invoice ~/.cursor/mcp.json
- VS Code receipt scanner expense_to_invoice .vscode/mcp.json
- Zed receipt scanner expense_to_invoice ~/.config/zed/settings.json
- Windsurf receipt scanner expense_to_invoice ~/.codeium/windsurf/mcp_config.json
- Cline receipt scanner expense_to_invoice ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI receipt scanner expense_to_invoice ~/.gemini/settings.json
- Grok receipt scanner expense_to_invoice .mcp.json (in your project root)
- ChatGPT receipt scanner expense_to_invoice Settings → Connectors → Advanced → Developer mode
- Claude.ai receipt scanner expense_to_invoice Settings → Connectors → Add custom connector
- LangChain receipt scanner expense_to_invoice pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http receipt-scanner https://mcp.zovo.one/mcp/receipt-scannerOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.