Quipu

Getting credentials

1. Sign in to Quipu and open the developer area (developers.getquipu.com) to register an application against your account.
2. You receive a client id (app_id) and client secret. Quipu's API uses the client-credentials grant, so there is no browser consent step for your own account's data.
3. Set QUIPU_CLIENT_ID and QUIPU_CLIENT_SECRET. AnythingMCP fetches and refreshes the access token on its own.

JSON:API, not plain JSON. Quipu follows the JSON:API specification: rows arrive as {"data": [{"id": …, "type": "invoices", "attributes": {…}, "relationships": {…}}]}. The interesting fields are inside attributes, and relationships are ids that need an include to resolve. This is why include appears on the tools below.

The Accept header is application/vnd.api+json, which Quipu requires; a plain application/json gets a 406. The adapter sends it.

Issued vs received. invoices are what you issue; expenses are what you receive and record. A revenue question wants invoices; a cost question wants expenses. Both carry the Spanish tax fields — IVA and IRPF retention — separately from the totals.

Paging is page[number] and page[size], JSON:API style, with the totals in the response's meta.

Unverified. The paths and field names below follow the vendor's published documentation and have not been exercised against a live tenant. Treat a 404 as a docs-versus-reality gap and check the developer portal before concluding that the credential is wrong. A correction from anyone running this against a real system is genuinely welcome.

Cloud reachability: getquipu.com is public with a valid certificate.