Coming soon: the first write tools for the Spendesk MCP
The Spendesk MCP is still an analysis tool today, not an execution one — but 4 write tools already exist in demo. Here's what they do, and the date and condition that gate their production rollout.
From insight to action
Until now, the Spendesk MCP answers one family of questions: the ones that start with "show me", "compare", "are there any". 23 of the 24 tools currently in production are read-only — Claude or your Dust agent query your real data, but never modify it. The one exception today is archiving a supplier.
That's starting to change. Four write tools already exist and work in our demo environment. They are not yet available to your customers in production — this post exists to lay out clearly what exists, what doesn't yet, and why.
🔒 Upcoming — the first 4 write tools
These four tools are demo-only today. Their production rollout is gated by a penetration test scheduled for the end of August 2026 — don't commit to an earlier date with a client.
archive_supplier
🔒 Upcoming — not yet available in production. Archives or reactivates a supplier. This is currently the only write action already live elsewhere in the Spendesk product — here it's exposed through the MCP too.
create_suppliers
🔒 Upcoming — not yet available in production. Creates a new supplier directly from the conversation, instead of switching over to the Spendesk interface.
mark_payable_as_ready
🔒 Upcoming — not yet available in production. Validates a payable's accounting information and marks it ready for export — one step in the month-end close flow, not the export itself.
update_payable
🔒 Upcoming — not yet available in production. Updates a payable's accounting fields: expense account, tax account, accounting date, cost center, analytical field values, amortisation dates.
Why now, why not yet
Moving from read to write changes the nature of the risk: a bad read gives a wrong answer, a bad write changes a real accounting record. That's why these 4 tools stay confined to the demo environment pending the security review scheduled for the end of August — and why they should never be presented as available to a prospect or client before that milestone.
More write tools are on the roadmap beyond these four examples. We'll add them to this page as they land — treat this as directional, not a fixed list or a guaranteed date.
Key takeaways
- The Spendesk MCP is still today an analysis and decision tool — 24 read tools in production, 4 write tools demo-only
- The first 4 write tools (
archive_supplier,create_suppliers,mark_payable_as_ready,update_payable) already exist but aren't in production yet - Their production rollout is gated by a penetration test scheduled for the end of August 2026
- In client conversations: present these tools as product direction, never as a shipped feature