Use AI assistants as an
operator for your invoicing API
Space Invoices exposes a first-party MCP endpoint so Claude, Cursor, and other AI tools can work against the same invoice, customer, and document workflows you already automate through REST. AI can operate the workflow faster; the compliance model, tenant isolation, and permissions still come from Space Invoices.
Move from chat to action
Draft invoices from natural-language requests
Look up customers, items, and unpaid documents
Review account data without building a custom UI first
Operate sandbox or production entities through existing API permissions
Plug into your preferred AI surface
Configure the remote MCP endpoint and authenticate with your existing Space Invoices token.
Configure the remote MCP endpoint and authenticate with your existing Space Invoices token.
Configure the remote MCP endpoint and authenticate with your existing Space Invoices token.
Configure the remote MCP endpoint and authenticate with your existing Space Invoices token.
Built on the API and compliance model you already trust
Uses the same bearer auth and permission checks as the REST API
Supports per-tool account and entity scoping
Returns the same JSON payloads and validation errors as normal API calls
Excludes binary and internal-only endpoints from the tool list
Keep the setup details in docs
The docs page covers the endpoint, bearer auth, `entityId` and `accountId` scoping, supported clients, and example tool argument shapes. This page stays focused on where MCP fits in your developer workflow.
Start with one workflow, not a whole rewrite
Free sandbox with no time limit. Prove one entity and one invoice flow before deciding how much UI, compliance, and rollout surface you want to own.