financeapi_key

Chaser

Chaser is an accounts receivable automation software that helps businesses automate invoice reminders and get paid faster.

Verdict

Chaser handles accounts receivable automation — tracking invoices, credit notes, and customer payment status. @mention it in Switchy to pull overdue balances, create invoices on the fly, or update customer records without leaving the conversation. Finance teams use it to answer "who owes us money?" questions during planning calls, while ops folks create credit notes when a client disputes a charge. You'll need a Chaser API key with read/write access; the MCP can't send payment reminders or access Chaser's email automation features, only the core invoice and customer data.

Common use cases

  • Pull overdue invoice list during finance standup
  • Create credit note when client disputes charge
  • Update customer email after account handoff
  • Check payment status before renewing contract
  • Generate invoice for ad-hoc project work

Integration

Vendor
Chaser
Category
finance
Auth
API_KEY
Tools
9
Composio slug
chaser

Tools

  • Create Credit Note

    Tool to create a new credit note record in the organization. use after confirming invoice adjustments.

  • Create Customer

    Tool to create a new customer record in chaser. use after obtaining basic auth credentials.

  • Create Invoice

    Tool to create a new invoice record in the organization. use after ensuring the customer exists in chaser.

  • Get Credit Notes

    Tool to retrieve a list of credit notes. use after authenticating this detail.

  • Get Customer by ID

    Tool to retrieve details for a specific customer by their external (source system) id. use after obtaining the external id when you need specific customer information.

  • Get Customers

    Tool to retrieve a list of all customers associated with the organization. use when you need to display or process complete customer contact and status information.

  • Get Organization

    Tool to retrieve information about the connected organizations. use when you need organization ids, currency, timezone, or legal details before other operations.

  • Update Customer

    Tool to update an existing customer's information using their unique externalid. use after confirming the customer's externalid. e.g., "update contactemailaddress for externalid cust abc123."

  • Update Invoice

    Tool to update an existing invoice's information using its unique identifier. use after confirming the invoice exists when you need to modify fields like status, amounts, or dates.

Setup

Setup guide

  1. 11. In Switchy, open Settings > Integrations > MCP Servers and click Add Server. 2. Select Chaser from the list. 3. Log into your Chaser account, navigate to Settings > API Keys, and generate a new key with Invoice and Customer scopes enabled. 4. Paste the API key into Switchy's connection form and click Connect. 5. Switchy will fetch your organization details to confirm the link works. 6. Open any Space, type '@Chaser get customers' and send — you should see a list of customer records appear in the response. 7. If the list is empty or you see an auth error, return to Settings > Integrations, delete the Chaser connection, and repeat steps 2-4 with a fresh API key.

What teammates see: by default, memories from Chaser are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

List Overdue Invoices

@Chaser get all customers, then show me which ones have overdue invoices and the total amount owed by each.
Open in a Space →

Create New Invoice

@Chaser create an invoice for customer external ID 'CUST-5678' with line item 'Consulting services' for $2,500, due in 30 days.
Open in a Space →

Issue Credit Note

@Chaser create a credit note for invoice INV-1234 in the amount of $150 with reason 'Duplicate charge correction'.
Open in a Space →

Update Customer Contact

@Chaser update the contact email for customer external ID 'CUST-9012' to 'billing@newdomain.com'.
Open in a Space →

Check Customer Balance

@Chaser get details for customer external ID 'CUST-3456' and summarize their current balance and last payment date.
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@chaser show me all customers with overdue invoices and their outstanding balances

Output

Based on the customer list retrieved from Chaser, here are accounts with overdue balances: • Acme Corp (ID: ACME-001): £12,450 overdue, last payment 45 days ago • BuildRight Ltd (ID: BUILD-789): £8,200 overdue, last payment 62 days ago • Tech Solutions Inc (ID: TECH-456): £3,100 overdue, last payment 31 days ago This represents £23,750 in total overdue receivables across 3 customers. Would you like me to draft follow-up messages or create credit notes for any disputed amounts?

Notes

This example uses Get Customers to retrieve account data. The MCP returns customer records with payment status, but filtering by 'overdue' requires the AI to interpret payment dates and invoice states. Requires API key with read access to customer and invoice data. Response time depends on total customer count in your Chaser organization.

Prompt

@chaser create an invoice for customer ACME-001 for £5,400 due in 30 days for Q1 consulting services

Output

Invoice created successfully in Chaser: • Invoice Number: INV-2024-0847 • Customer: Acme Corp (ACME-001) • Amount: £5,400.00 • Due Date: March 15, 2024 (30 days from today) • Description: Q1 consulting services • Status: Awaiting payment The invoice is now visible in your Chaser dashboard and will be included in automated payment reminder workflows according to your organization's chase schedule. The customer will receive their first reminder 7 days before the due date unless you've customized the timing.

Notes

This example uses Create Invoice after confirming the customer exists via their external ID. The MCP creates the invoice record but does NOT automatically send it to the customer—that happens through Chaser's scheduled reminder workflows. Requires API key with write permissions. If the customer ID doesn't exist in Chaser, the operation fails and you'll need to create the customer first.

Prompt

@chaser review our organization's payment terms and draft a policy update email explaining our new 15-day payment window to all active customers

Output

I've retrieved your organization details from Chaser. Current settings show: • Default payment terms: Net 30 • Currency: GBP • Active customers: 47 • Timezone: Europe/London Here's a draft policy update email: **Subject: Updated Payment Terms – Effective April 1, 2024** Dear Valued Customer, We're updating our payment terms from Net 30 to Net 15, effective April 1st. This change helps us maintain the quality service you expect while managing cash flow more effectively. All invoices issued after this date will reflect the new 15-day payment window. If you have questions or need to discuss payment arrangements, please contact our accounts team at [your contact details]. This change affects 47 active customer accounts. Would you like me to segment this by customer payment history before sending?

Notes

This example combines Get Organization (to retrieve current terms and customer count) with the AI's drafting capability. The MCP provides factual organization data, but the AI synthesizes it into customer communication. This is read-only—the MCP cannot send emails or update payment terms directly. You'll need to manually implement the policy change in Chaser's settings and distribute the message through your own email system.

Use-case deep-dives

Month-end invoice reconciliation

When Chaser MCP speeds up close for finance teams under 10

A 6-person finance team at a B2B SaaS company closes books on the 5th of each month. They spend 4 hours reconciling invoices across Xero and their CRM, then another 2 hours issuing credit notes for disputed charges. The Chaser MCP wins here because it centralizes invoice and credit note creation in one workspace—your AI can pull customer records, create invoices, and issue credits without switching tabs. The 9-tool scope covers the full AR workflow: get customers, create invoices, handle credit notes. The trade-off: if your AR volume exceeds 500 invoices per month, you'll want dedicated automation (Zapier, Make) instead of ad-hoc AI commands. Below that threshold, Chaser MCP cuts reconciliation time in half and keeps the entire finance team in sync on one shared workspace.

Customer onboarding for agencies

How Chaser MCP handles new-client setup in under 5 minutes

A 3-person creative agency signs 8-12 new clients per quarter. Each onboarding involves creating a customer record, setting payment terms, and issuing the first invoice—usually a 20-minute task split across email, accounting software, and a spreadsheet. The Chaser MCP collapses this into a single AI conversation: your team member pastes the client's details, the AI creates the customer record, confirms the org currency and timezone, then generates the first invoice. The API key auth means setup takes 2 minutes, and the Create Customer and Create Invoice tools handle 90% of onboarding. The boundary: if you're onboarding more than 20 clients per month, you need a dedicated onboarding pipeline, not an AI workspace. For agencies at this scale, Chaser MCP turns onboarding from a context-switch into a 5-minute chat.

Support ticket credit resolution

When Chaser MCP closes disputed-charge loops in customer support

A 12-person support team at a subscription business handles 40-60 billing disputes per week. Each dispute requires pulling the invoice, confirming the customer's account status, and issuing a credit note—then updating the ticket. Without Chaser MCP, this is a 4-tab workflow (helpdesk, accounting, CRM, Slack). With it, the support agent asks the AI to retrieve the invoice, verify the customer record, and create the credit note in one thread. The Get Credit Notes and Create Credit Note tools close the loop without leaving the workspace. The catch: if your dispute volume is under 10 per week, the overhead of setting up the MCP isn't worth it—just handle it manually. Above that, Chaser MCP saves 15 minutes per dispute and keeps your support team from bouncing between tools.

Frequently asked

What does the Chaser MCP let me do in Switchy?

It connects Switchy to your Chaser account so you can create invoices, credit notes, and customer records, plus retrieve customer lists and organization details. You can ask the AI to draft an invoice for a customer, update contact emails, or pull a list of outstanding credit notes without leaving the chat. It's built for teams that want to manage receivables workflows conversationally instead of clicking through Chaser's UI.

Do I need admin access to connect Chaser MCP?

You need a Chaser API key, which typically requires admin or billing-level permissions in your Chaser account. The MCP uses API_KEY authentication, so whoever connects it must be able to generate or retrieve that key from Chaser's settings. Once connected, the key lives in Switchy's encrypted vault and the whole team can use the integration without needing their own Chaser logins.

Can the Chaser MCP send payment reminders or chase overdue invoices?

No. The MCP focuses on creating and retrieving records—invoices, credit notes, customers—but it doesn't trigger Chaser's automated chasing workflows or send reminder emails. If you need to kick off a chase sequence, you'll still do that in Chaser's app. Think of the MCP as a read-write layer for your receivables data, not a replacement for Chaser's dunning engine.

How is this different from using Chaser's web app or API directly?

The web app requires manual form-filling; the API requires writing code. The MCP sits in between: you describe what you want in plain English, and Switchy translates that into the correct API calls. It's faster for ad-hoc tasks like "create an invoice for Acme Corp" or "show me all customers in London" because you skip the UI navigation and the API docs.

Who on the team should connect the Chaser MCP?

Whoever owns your Chaser account and can safely generate an API key—usually your finance lead or operations manager. Once connected, anyone in the Switchy workspace can use the integration to create invoices or look up customers, so you don't need to share the API key around. Just make sure the person connecting it understands that the key grants write access to your Chaser data.

Data last verified 607 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.