3,400+ servers built on vurb.ts
Vinkius

Bring Corporate Cards
to Claude Code

Learn how to connect Spendesk to Claude Code and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Get Payment DetailsGet Supplier DetailsList BudgetsList CardsList Expense ClaimsList InvoicesList MembersList PaymentsList Suppliers
Spendesk

What is the Spendesk MCP Server?

Bring your Spendesk financial operations natively into your AI workspace. Eliminate constant tab switching to check the finance dashboard. You can now use conversational prompts to audit real-time company expenses, verify specific payment IDs, and inspect active supplier invoices while writing your integration code or managing operational scripts.

What you can do

  • Track Cash Flow — Monitor organizational outflows by executing list_payments. Need deep details on a specific transaction? Pull exactly what happened using get_payment_details
  • Audit Invoices & Expenses — Keep track of pending vendor bills via list_invoices and review employee out-of-pocket reimbursements triggering list_expense_claims
  • Supplier Management — Check your registered vendor matrix using list_suppliers and pull contact or payment history directly calling get_supplier_details
  • Control Limits — Actively supervise remaining budget allocations calling list_budgets and watch the assigned corporate limits on issued plastic/virtual via list_cards

How it works

1. Subscribe to this AI integration server
2. Introduce your official Spendesk Access Token
3. Start using Claude, Cursor, or your terminal IDE to query financial states autonomously

Stop managing financial syncs blindly and asking accountants to pull limits. Let your local AI understand your company's real-time spending constraints directly before triggering automated actions.

Who is this for?

  • Finance Engineers — test accounting webhooks or integrations reading live Spendesk data intuitively through pure conversational chat formats
  • Operation Managers — use an agent to build quick markdown summaries on active budgets or compile how much a specific team spent on software this month
  • Founders & Admins — query team members (list_members) or verify immediately if a virtual card (list_cards) has enough cap for a high-value purchase without logging in

Built-in capabilities (9)

get_payment_details

Get detailed information about a specific payment

get_supplier_details

Get detailed information about a specific supplier

list_budgets

List all budgets and their spending status

list_cards

List all virtual and physical cards issued

list_expense_claims

List all employee expense claims and reimbursement requests

list_invoices

List all invoices pending or processed

list_members

List all team members with Spendesk access

list_payments

List all payments in the Spendesk account

list_suppliers

List all registered suppliers

Why Claude Code?

Claude Code registers Spendesk as an MCP server in a single terminal command. Once connected, Claude Code discovers all 9 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Spendesk data drives decisions without human intervention.

  • Single-command setup: claude mcp add registers the server instantly. no config files to edit or applications to restart

  • Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks

  • Claude Code runs headlessly, enabling unattended batch processing using Spendesk tools in cron jobs or deployment scripts

  • Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features

See it in action

Spendesk in Claude Code

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Spendesk and 3,400+ other MCP servers. One platform. One governance layer.

Teams that connect Spendesk to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

3,400+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself3,400+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Spendesk in Claude Code

The Spendesk MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 9 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Spendesk
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Spendesk for Claude Code

Every tool call from Claude Code to the Spendesk MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can the AI perform destructive actions like making a real payment or deleting invoices?

No. The integration focuses strongly on extraction via READ endpoints (e.g. list_payments, list_budgets, list_expense_claims). It is designed to act as an advanced analytical viewing lens allowing you to query, organize, and monitor financial positions without executing operational mutations like transferring money.

02

How can the AI help me understand a specific expense claim?

You can provide the Expense ID from your list_expense_claims search and ask natural questions. The AI will pull the structured data and explain explicitly who submitted the reimbursement, the exact amount, the associated spending currency, and the current processing status, formatting it all into an easily digestible summary.

03

How deep is the Spendesk token scoped? Is it secure?

The integration is secure. Your Vinkius Agent runs strictly client-side on your PC. It queries the API using the explicit Bearer Token you manage. Spendesk's token access capabilities can also be carefully constrained natively from your Organization's Integration Settings to further enforce least privilege.

04

How do I add an MCP server to Claude Code?

Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.

05

Can Claude Code run MCP tools in headless mode?

Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.

06

How do I list all connected MCP servers?

Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.

07

Command not found: claude

Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code

08

Connection timeout

Check your internet connection and verify the Edge URL is reachable