LabscoMCP early access ↗
MCP SERVER · OFFICIAL PROJECT

Billabex Receivables

Debt-collection workflows for an assistant, with reads and writes split by OAuth scope and the whole tool catalogue readable before you connect.

by billabex ↗Accounting, Invoicing & Bookkeeping✓ Official

LABSCO SUMMARY

You can see every tool, and the scope it needs, before you authorize anything.

The catalogue at /mcp/tools answers without a token, so you can check what mcp:read and mcp:write would open up before an OAuth flow starts, and every tool carries annotations such as readOnlyHint. Watch the consent step: a client that asks for no scope gets both read and write. There is no shared sandbox, so rehearse in an organization of your own, where follow-ups can be paused per account. For a product that chases customers for money, that rehearsal is not optional.

What it is

Billabex's MCP endpoint for their receivables product, at https://next.billabex.com/mcp.

What you get

Tools across the collection workflow, each carrying annotations such as readOnlyHint so a client can tell reads from writes before calling. The full current list, with schemas and scopes, is public at GET /mcp/tools and needs no credential.

Requirements

OAuth 2.1 with PKCE and standards-based discovery. If the client asks for no scope, consent covers both mcp:read and mcp:write. There is no shared sandbox, so testing needs an organization of your own.

Setup effort

Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen