- Home
- Skills
- Finance & Accounting
- ZenMoney Receipt Categorization with MCP
Works with the AI Agents you already use
ZenMoney Receipt Categorization with MCP
Match receipts to ZenMoney expenses, preview category splits, and verify approved changes through your own MCP connector.
$5
/moSubscription · cancel anytime
Secure checkout via Stripe
- Always the latest version
- Delivered live to your agent via MCP
- Cancel anytime, access ends at period end
ZenMoney Receipt Categorization with MCP
Example session with this skill installed
Synthetic example — no personal financial data:
Categorize this example receipt in ZenMoney. It is dated 2026-01-10, paid from my confirmed EUR Demo account, and contains bread €3.00, fruit €5.00 and dish soap €2.00. Total €10.00, no discount. Show the exact preview before writing. Assume the demo connector has no matching expense and already has Food and Household categories.
- Read your context and instructions
- Compiled the zenmoney receipt categorization
Synthetic example: preview before approval
This is an illustrative output using fictional receipt facts and a demo connector, not a recording of a customer's account or proof of a live write.
The example receipt totals €10.00. The demo search has no matching expense. The confirmed account is Demo (EUR), and both proposed categories already exist.
| Date | Account | Category | Receipt items | Expense |
|---|---|---|---|---|
| 2026-01-10 | Demo (EUR) | Food | Bread €3.00; fruit €5.00 | €8.00 |
| 2026-01-10 | Demo (EUR) | Household | Dish soap €2.00 | €2.00 |
| Total | €10.00 |
The proposed action creates two expenses, one per supported category. No expense has been created yet. No new category or transaction comment is proposed.
In this example, receipt memory is disabled, so no local purpose groups will be retained. Enabling it is a separate setting with its own preview and retention choice.
Next step
Confirm this exact account, date and category split to apply it, or ask for a correction. After approval, the connector checks for concurrent changes and verifies the resulting expenses before reporting success. If an apply is interrupted, inspect its durable operation record before retrying.
Subscription · always the latest version
- Secure checkout via Stripe
- Cancel anytime
- Delivered live via MCP
About this skill
Turn receipts into reviewable ZenMoney entries
Attach a receipt image or PDF and let your agent check existing expenses, identify supported categories, and prepare an exact preview. Review the account, date, currency, amounts and categories before an approved write. Missing expenses are created as one expense per supported category.
What is included
- A focused SKILL.md workflow for matching, categorizing and reconciling receipts.
- Setup instructions for the separately installed open-source zenmoney-receipts MCP server.
- Storage/privacy guidance, synthetic examples and the MIT license.
- Recovery guidance for interrupted operations and verification before reporting success.
Optional evidence memory
Opt-in memory keeps narrow approved purpose groups, counts, subtotals, month and category references. It is off on fresh installations. The agent reports its actual storage location and retention. Local mode stores evidence on the MCP machine; hosted mode uses server tenant storage. Receipts and OCR are not retained by this memory feature. Your agent provider still processes the files you give it under its own policies.
Before you start
Install and configure zenmoney-receipts with Node.js 20.11+, npm, Git and your own ZenMoney account. Your agent must support MCP and reading your image/PDF. This skill does not include an OCR engine, a ZenMoney subscription, or a public hosted connector.
Amounts written to ZenMoney are kept distinct from optional full-price evidence. Pre-discount evidence requires a connector that advertises evidencePricing; older versions must report that limitation instead of dropping items.
Control and limitations
Ambiguous matches and unreadable amounts need clarification. Category changes are scoped and previewed; no generic transaction deletion or unrestricted patch tool is exposed. Matching reduces duplicate risk but cannot guarantee bank sync completeness. Host/model receipt extraction can make mistakes: inspect the preview.
Free and MIT-licensed. Source and setup. Report bugs in the repository with synthetic examples; never post personal receipts or credentials.
Requires separate connector installation and ZenMoney credentials; no public hosted service or OCR engine is included. Receipt extraction depends on the host and needs review. Ambiguous matches need clarification. Other agent hosts are not verified. Complete full-price evidence above paid total requires the additive evidencePricing capability, which older connector versions may lack. Local evidence does not sync by cloning the repository.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 1 month ago
Requires
Permissions
Allowed Hosts
Reads only receipt files supplied by the user. Network access is through the configured connector to ZenMoney for bounded reads and explicitly approved writes. Shell access is for local connector installation/diagnostics. Connector writes its operation journal and, if enabled, minimal receipt evidence in its application-data directory; personal data must not be stored in the source checkout. Credentials are configured privately by the user, never pasted into prompts. Browser access is not required for normal receipt handling.