ChaserHQ MCP integration for AI agents.
Connect AI agents to ChaserHQ through 8 structured actions, including get customer, get invoice, and get invoice history. Review authentication, inputs, work…
- ACTION CONTRACTS
- 8
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the ChaserHQ integration exposes
The ChaserHQ Agent App exposes 8 provider-backed actions for finance work. Its current contract lets an authorized agent get one chaser customer by id or ext_ external id, get one chaser invoice by id, and get history for one chaser invoice. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected ChaserHQ account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ChaserHQ capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_customerREADGet one Chaser customer by ID or ext_ external ID.
INPUTS: customerId / additionalFields
get_invoiceREADGet one Chaser invoice by ID.
INPUTS: invoiceId
get_invoice_historyREADGet history for one Chaser invoice.
INPUTS: invoiceId
get_organisationREADGet the Chaser organisation attached to the API credentials.
get_statusREADGet ChaserHQ API status.
list_customersREADList Chaser customers with optional filters and pagination.
INPUTS: limit / page / filters / additionalFields
list_invoice_historyREADList Chaser invoice history records with optional filters and pagination.
INPUTS: limit / page / filters / additionalFields
list_invoicesREADList Chaser invoices with optional filters and pagination.
INPUTS: limit / page / filters / additionalFields
INPUT CONTRACTS
Know what the action needs before it runs.
get_customer
customerIdREQUIRED- The Chaser customer id, or an external id prefixed with ext_.
additionalFieldsOPTIONAL- Optional customer fields to include in the response.
get_invoice
invoiceIdREQUIRED- The Chaser invoice identifier.
get_invoice_history
invoiceIdREQUIRED- The Chaser invoice identifier.
list_customers
limitOPTIONAL- The number of items per page. Chaser allows at most 100.
pageOPTIONAL- The zero-based page number to request.
filtersOPTIONAL- Chaser filters keyed by field name.
additionalFieldsOPTIONAL- Optional customer fields to include in the response.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Customer
Get one Chaser customer by ID or ext_ external ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_customerVerify with Get Invoice
Get one Chaser invoice by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_invoiceSAFETY BOUNDARY
Operate ChaserHQ with explicit limits
- Authorize ChaserHQ with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned ChaserHQ data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in ChaserHQ rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ChaserHQ task completed successfully.
CONNECTION MODEL
API key
Chaser API key used with the API Secret through HTTP Basic authentication. Find both values in Chaser under Organisation Settings > Integrations > Get API keys: https://my.chaserhq.com/settings/integrations
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 8
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by ChaserHQ.