API Tools
duebuddy.work
An MCP server for an invoice parsing API that extracts structured data from invoices and provides export links, balance checks, and top-up information.
ENDPOINT 1
https://duebuddy.work/mcp
MCP server metadata
- Name
- duebuddy
DueBuddy reads incoming supplier invoices (PDF, photo, scan, XML, QR) and returns structured data plus a file ready for accounting (DATEV EXTF category 21, CSV, Excel, JSON, UBL). Electronic invoices in XML or QR are parsed by code and are free; scans cost 0.07 EUR per page. The balance is topped up from 8 EUR via Lava. DueBuddy does NOT issue invoices, does NOT take payments and has NO DATEV API integration: it delivers a file, the booking happens in DATEV.
Known tools 4
get_resultFetch the result of a parse job: structured fields plus export links for accounting.
Inferred read-onlyget_balanceHow many scanned pages are left on this API key before the next top-up.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.duebuddy]
url = "https://duebuddy.work/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"duebuddy": {
"type": "http",
"url": "https://duebuddy.work/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: duebuddy
Remote MCP URL: https://duebuddy.work/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"duebuddy": {
"url": "https://duebuddy.work/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"duebuddy": {
"type": "http",
"url": "https://duebuddy.work/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "duebuddy",
"transport": "streamable-http",
"url": "https://duebuddy.work/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.