The Debitura MCP server lets you use Debitura from an AI assistant such as Claude, Cursor, or VS Code Copilot. This page explains what it is, what you can do with it, and how it protects your data.
What it is
The MCP server is a hosted connector that gives an MCP-compatible AI assistant direct access to your Debitura account through the Customer API. Once it is connected, you can manage your collection portfolio in plain language, without opening the web app or writing code. MCP (Model Context Protocol) is an open standard that AI assistants use to connect to outside tools.
To set it up, see Clients: How to connect your AI assistant to Debitura (MCP server).
What you can do
The server provides 14 tools. Eleven let the assistant read your data, and three let it make changes.
Read your account and cases
Check the connection and see which account you are connected as
List your cases and open a single case in full detail
Follow a case timeline of status changes, partner actions, and payments
Read the chat between you and your collection partner
See the payments recovered on a case
Check which contracts are signed or still blocking a case
List the documents attached to a case
See a portfolio overview of how many cases sit in each stage
Preview pricing and eligibility before creating a case
Make changes
Submit a new collection case
Upload a document to a case
Send a message to your collection partner
Actions that need your confirmation
Submitting a case is a legal and financial action: a collection partner begins recovery, and a success fee applies if money is recovered. Because of this, the assistant first previews the pricing, the assigned partner, and any contracts that need signing, and then asks for your explicit confirmation before it submits. Submission is protected against duplicates, so a repeated request cannot create the same case twice.
Messages to a partner are attributed to a named member of your team, so the partner can always see who wrote each message.
Test and production
Debitura runs two endpoints: a production endpoint that acts on your live account, and a separate test endpoint that runs against the test environment. Most users connect the production endpoint with their own API key.
How it protects your data
Your API key identifies exactly one Debitura account, and it is the boundary for everything the assistant can see or do: the server can only ever reach the single account that owns the key. The server is stateless and stores nothing - it does not save your API key or your case data. The key is read from each request, passed to the Customer API, and discarded when the request finishes. Traffic is protected at the network edge by a web application firewall and rate limiting.
What is not included
The MCP server covers the actions that are most useful from an AI assistant, not everything in the platform. Managing divisions, managing webhooks, and lead-to-quote workflows are not available through it; for those, use the Debitura web app or the Customer API directly. Authentication is by API key only.
Related