MCP: receipts, live data, requesters and Microsoft Copilot

The Spendesk MCP server does more since late October. It now has 67 tools: 37 that read and 30 that act.

• Attach receipts to card payments — create_payable_attachment_upload lets the assistant add a missing receipt to a card payment. It needs the Upload payable attachments permission (scope experimental:payable-attachment:write), off by default like every write permission. The upload takes two steps, the second being an HTTP request to send the file: it works with assistants that can run code or send HTTP requests. Each call adds one receipt, and the payment must not be exported yet.
• Read live data — read tools accept an optional liveRead argument. Set to true, it bypasses the API's response cache, so a change just made in Spendesk shows at once. Live reads have a stricter rate limit, a hundredth of the normal one.
• Requesters can connect — an employee with the Requester role can ask about their own card spend: their cards, card payments (declined ones included), card requests and card expenses. The MCP tool reference now lists the role each tool requires.
• Microsoft Copilot — Copilot Studio registers itself with dynamic client registration: add a Model Context Protocol tool with the server URL and OAuth 2.0 → Dynamic discovery, with nothing to create in Spendesk. The agent then works in Microsoft 365 Copilot and Teams. GitHub Copilot in VS Code is also supported, with a client created in Spendesk.

Try it with a prompt such as:

Which of my card payments from last month are missing a receipt? Check again with live data.

Set-up steps for each assistant are in Set up Claude, ChatGPT or Dust; every tool, its permission, its role and whether its action can be undone, in the MCP tool reference.