What is Spendesk MCP?
Spendesk MCP (Model Context Protocol) is a capability that connects your Spendesk financial data directly to the AI tools your team already uses — through a simple, secure, read-only interface.
No more manual exports. No more switching between dashboards. Just ask a question in natural language and get instant, accurate answers about your financial operations.
In one sentence: Get all your Spendesk data, anywhere you need it, the way you want it — through a prompt.
Instead of navigating Spendesk to pull a report, you can simply ask your AI assistant:
"Show me spend by cost center for Q1 2026"
"What invoices from supplier X haven't been exported to our ERP yet?"
"What are our top 10 suppliers this quarter?"
And get a precise, real-time answer — directly in your AI tool of choice.
Who is this for?
Spendesk MCP is designed for anyone in your organization who needs fast, accurate access to financial data — without needing to navigate Spendesk manually:
Persona | What they can do |
Account Owners & Admins | Full access to spend analytics and financial reporting |
Controllers | AP aging, cash flow forecasting, payment schedules |
Accountants | Invoice tracking, VAT breakdown, audit trails |
CFOs & FP&A | Cross-period comparisons, supplier analysis, department budgets |
Role & Access:
Only AO/Admin can activate Spendesk MCP
Only AO/Controller can query data from MCP — Employees cannot query MCP.
MCP access is read-only. MCP lets you query and analyze your data — you cannot yet create or modify records through it.
MCP is now available to all customers at no cost. To activate, use this link — you'll be up and running within 24 hours.
Multi-Entity Support
If your organization has multiple entities in Spendesk, MCP respects your entity structure out of the box. You can query data scoped to your organization — across entities — without any additional configuration.
Without MCP: If your group has 3 entities (e.g. France, Germany, UK), getting a consolidated view of spend means logging into each entity separately, exporting the data, and manually combining everything in a spreadsheet — every single time.
With Spendesk MCP: Simply ask "What is the total spend across all our entities in Q1 2026?" and get a consolidated answer instantly — no export, no spreadsheet, no manual reconciliation.
This makes Spendesk MCP especially powerful for groups and multi-subsidiary companies.
Organisation-level MCP: Multi-entity accounts can enable the organisation-level MCP option when generating credentials. This allows MCP to access data across all your entities, enabling consolidated multi-entity reports and dashboards in a single prompt — no manual aggregation needed.
Supported AI Tools
Spendesk MCP is currently available with:
AI Tool | Status |
Dust | ✅ Available now |
Claude (Anthropic) | ✅ Available now |
ChatGPT (OpenAI) | ✅ Available now |
Gemini (Google) | Coming soon |
How to Activate Spendesk MCP
Prerequisites
Before connecting, make sure:
You are an Account Owner or Admin on your Spendesk account
You have an active account on Dust, Claude, or ChatGPT
Step 1 — Access the MCP connection page
Log in to your Spendesk account
Go to Settings → Integrations → AI Connections OR If you have the multi-entity Hub Go to Multi-entity Hub-> MCP
Click Connect MCP
If you don't see this option, use this link to request access — you'll be up and running within 24 hours.
Step 2 — Generate your MCP credentials
Click Generate Credentials
Your OAuth Client ID and OAuth Client Secret are generated automatically — copy them, you will need them in the next step
Store these credentials securely. They will not be shown again.
What are OAuth credentials? Your OAuth Client ID and OAuth Client Secret are unique to your organization and used to authenticate the MCP connection securely. Keep them safe — treat them like a password.
Step 3 — Connect to your AI tool
If you are using Dust
Requires workspace Admin access.
In your Dust workspace, go to Spaces → Tools
Click Add Tool
In the panel that opens, click Add MCP Server
Enter the MCP Server URL:
https://public-api.spendesk.com/v1/mcpFor Authentication, select Static OAuth
For Connection type, select Personal accounts
Fill in the OAuth fields:
Field | Value |
OAuth Client ID | Generated in Step 2 (in-product flow) |
OAuth Client Secret | Generated in Step 2 (in-product flow) |
OAuth Token Endpoint | |
OAuth Authorization Endpoint |
Click Setup connection
Once confirmed, the Spendesk MCP tools are immediately available to all agents in your Dust workspace.
Shared vs Personal accounts: Choose "Personal accounts" if you want each team member to authenticate individually with their own Spendesk credentials.
If you are using Claude (Claude.ai or Claude Desktop)
Open Claude's Settings → Connectors → Customize
Click Connectors → + → Add custom connector
Paste the MCP Server URL:
https://public-api.spendesk.com/v1/mcpEnter your OAuth Client ID and OAuth Client Secret — generated in Step 2 (in-product flow)
Click Add — Claude will now have access to your Spendesk data
Click on Spendesk MCP in the Connectors list and click Connect
If you are using ChatGPT
Requires workspace Admin access on ChatGPT.
In your ChatGPT workspace, go to Settings → Apps
Click Advanced Settings and toggle on Developer mode
Click the Create app button that appears at the top
Name your tool, e.g. "Spendesk MCP"
Paste the MCP Connection URL:
https://public-api.spendesk.com/v1/mcpClick Advanced OAuth settings → find the Callback URL section
Paste your OAuth Client ID and OAuth Client Secret — generated in Step 2
⚠️ Important: Copy and paste the credentials carefully — avoid adding spaces or editing the values. The Client Secret is shown only once: paste it into ChatGPT before closing the Spendesk page.
On the left side of the modal, check the box labeled "I understand and want to continue"
Click Create → Sign in with Spendesk MCP
ChatGPT will redirect you to Spendesk. In the modal, click Authorise. You will then be redirected back to ChatGPT.
You're set!
Step 4 — Verify the connection
Once connected, test the integration with a simple prompt in your AI tool:
"What is the total spend for my company in Q1 2026?"
If you receive a structured response with actual data from your Spendesk account, you are all set.
Dust Screen
Claude Screen
Examples of what you can do with Spendesk MCP
The following examples illustrate some of the ways you can query your Spendesk data. This list is not exhaustive — you can ask anything related to your financial operations in natural language.
Capability | What it helps you do | Use cases | Filters & grouping available | Example prompts |
Check wallet funding | Check wallet balance, available funds, allocated funds, and wallet top-ups. | Check funds, Review top-ups, Track allocation | Date range, top-up method, amount, currency | "What is our current available wallet balance?" "Show recent wallet top-ups." "How much was added to the wallet this month?" "Were there any wallet top-ups by wire transfer last week?" "Do we have enough available balance for upcoming payments?" |
Track payables and settlements | Review payable and settlement details, such as due dates, statuses, and supporting documents. Understand what is unpaid, overdue, upcoming, or already settled. | Track spend, Find documentary evidence | Date range, due date, status, supplier, amount, currency, payable type, settlement status, settlement date | "Show all overdue payables by supplier." "Which payables are due in the next 30 days?" "List unpaid invoices over €5,000." "Find the attachment for this payable." "Which payables were settled this month?" |
Review purchase orders | Track purchase orders, amounts, dates, items, suppliers, and other details. Understand what has been requested or ordered. | Track POs, Review delivery | Date range, status, supplier, requester, amount, currency, item, purchase order ID | "Show purchase orders created this month." "List open purchase orders over €10,000." "Which purchase orders are linked to this supplier?" "What items were included in this purchase order?" "Summarize purchase order activity for Q1." |
Look up suppliers and users | Look up company users and suppliers for reporting, ownership, approval context, supplier analysis, and spend investigations. | Supplier analysis, Spend investigations | User name, user role, user status, supplier name, supplier status | "Find this supplier in Spendesk." "Show supplier details for Acme Ltd." "List suppliers paid this quarter." "Which users are linked to spend in this period?" |
Analyse spend dimensions | Break down spend by reporting dimensions such as cost centres, expense categories, and analytical fields. | Break down spend, Analyse top suppliers | Cost centre, expense category, analytical field, analytical field value, active or inactive status | "Show total spend by supplier in Q1." "Break down spend by cost centre for last month." "Show the top 10 suppliers by spend this year." "Compare travel spend by department." |
What MCP Cannot Do (Yet)
Spendesk MCP is currently read-only. This means:
Not available yet | Coming soon |
Creating or approving expenses | ✓ Planned |
Modifying invoices or payments | ✓ Planned |
Managing users or roles | ✓ Planned |
Triggering approval workflows | ✓ Planned |
Write capabilities (action tools) are on the roadmap for future releases.
Security & Data Privacy
Read-only access: MCP cannot modify, create, or delete any data in your Spendesk account
Authenticated: All requests are authenticated via OAuth — your data is never shared with other accounts
Scoped to your organization: The MCP connection only exposes data belonging to your Spendesk organization
You stay in control: You can revoke your MCP credentials at any time from Settings → Integrations → AI Connections
Frequently Asked Questions
Who needs to activate MCP on the Spendesk side?
The Spendesk Account Owner (AO) or Admin must initiate the activation from within Spendesk: Settings → Integrations → AI Connections → Connect MCP → Generate Credentials.
Who needs to complete the setup on the AI tool side?
Once the AO has generated credentials in Spendesk, a workspace Admin on your AI tool (Dust, Claude, or ChatGPT) must complete the MCP server setup via the tool's interface using the provided credentials.
How does each user connect individually?
Once the MCP server is activated on the LLM, each Controller or Account Owner can start using it. On their first connection (or reconnection), the AI tool will prompt them to log in to their Spendesk account to establish their individual connection.
Can I use Spendesk MCP without Dust, Claude, or ChatGPT?
Currently, only Dust, Claude, and ChatGPT are supported. Gemini will be added soon.
Is there a cost for using MCP?
No. MCP access is free for all customers. To activate, use this link — you'll be up and running within 24 hours.
Does everybody in my company have access to MCP data?
Once MCP is activated, Account Owners & Controllers will be able to retrieve data. If you want more granular control over what data can be accessed by certain users, you can use the built-in permission groups from your AI tool (Dust, Claude, ChatGPT,...).
What data can MCP access?
MCP has access to your company's financial data in Spendesk: wallet balances, payables, settlements, purchase orders, suppliers, users, cost centres, expense categories, and analytical fields. It respects your existing entity and permission structure.
How does multi-entity work with MCP?
Multi-entity accounts can enable the organisation-level MCP option when generating credentials. This allows MCP to access data across all your entities and generate consolidated multi-entity reports and dashboards in a single prompt — no manual aggregation needed.
Why does Dust ask me to approve the connection multiple times when I have several entities?
When you set up Spendesk MCP in Dust with a multi-entity organisation, you may be prompted to approve a connection for each entity separately — so with 7 entities, you'll see 7 approval prompts. This is because the default configuration issues one authorisation per entity.
To approve all entities in a single step, you need to enable the Organisation-level MCP option. This generates a single token that covers all your entities at once, so you only need to authenticate once.
If you do not see the "All my companies" option during the Spendesk authorisation screen, contact Spendesk support to request activation of organisation-level access for your account. Once enabled, disconnect your existing Spendesk MCP tool in Dust and reconnect — you will only be prompted once.
How can I avoid approving each MCP tool call individually in Claude?
By default, Claude asks for your approval each time it wants to use an MCP tool (e.g. "Allow Claude to call get_wallet_summary?"). You can remove these prompts by setting tools to Always allow.
To configure this: go to Customize → Connectors in Claude, click on your Spendesk MCP connector, open Tool permissions, and switch each tool from Needs approval to Always allow. Claude will then call Spendesk tools automatically without asking for confirmation each time.
💡 For Claude Team or Enterprise plans: Organisation Owners can configure these permissions centrally so they apply to all members — individual users cannot override org-level settings. On individual plans (Free, Pro, Max), each user needs to configure this in their own Claude account.
What is the difference between approving a connection in Dust vs. approving tool calls in Claude?
These are two different types of approvals that serve different purposes:
| Dust | Claude |
What is approved | The OAuth connection to Spendesk (granting Dust access to your data) | Each individual MCP tool call (e.g. querying wallet data) |
When it happens | Once at setup — or once per entity if organisation-level is not enabled | Every time Claude uses a tool, unless set to "Always allow" |
How to skip it | Enable organisation-level MCP to approve all entities in one step | Set tools to "Always allow" in Connector settings |
Once Dust is connected, it calls MCP tools automatically in the background — there are no per-call approval prompts in Dust.
What are Claude skills and how do I install them?
Skills are pre-built instruction files that tell Claude exactly which Spendesk MCP tools to call for specific financial tasks — no coding required. You download a skill from the library, place it in your Claude project folder, and Claude uses it automatically. → See Chapter 1 of the Advanced Usage Guide
Can I automate recurring financial reports with MCP?
Yes. Using Claude's routine feature, you can schedule any question (daily payment priority, weekly cash forecast, monthly closing checklist) to run automatically — without manual intervention each time. → See Chapter 3 of the Advanced Usage Guide
Can I receive Slack alerts based on my Spendesk data?
Yes — by combining a Claude routine with the Slack connector, you can automatically push summaries (overdue invoices, blocked approvals, missing invoices) to any Slack channel on a fixed schedule. → See Chapter 4 of the Advanced Usage Guide
My question returned unexpected results — what should I do?
Try rephrasing your question with more specific parameters (e.g. include a date range, currency, supplier name, or entity). If the issue persists, contact support.
How do I disconnect MCP?
Go to Settings → Integrations → AI Connections and click Revoke credentials. This immediately cuts off the connection.
🚀 Go further with Claude & Dust
Once MCP is connected, discover how to install skills, automate reports, build Slack alerts, and use Claude as a financial thinking partner.
→ Advanced MCP Usage Guide — Claude & Dust
Need Help?
In-app chat: Click the chat bubble in the bottom right of your Spendesk account
Email support: support@spendesk.com