# Finexio MCP connector The Finexio connector brings counterparties, invoices, payments, drawdowns and supplier contacts into Claude, ChatGPT, Cursor and the Elaichi Agent, so your team can ask about supplier payments and keep Finexio records current from one governed endpoint. Source: https://elaichi.ai/connectors/finexio/ ## Facts | | | | --- | --- | | Application | Finexio | | Category | Payment Gateway | | AI tools | 26 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Finexio is connected - Show Finexio invoices created for Acme this month. - List Finexio payments over 10,000 awaiting settlement. - Which Finexio counterparties have no invoices this quarter? ## Connect Finexio in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Finexio. 2. Optionally set Share with, then press Connect. 3. Paste a Finexio API key. One person generates a token in Finexio and pastes it once. Everyone else works through Share with, and never sees it. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Finexio tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Finexio to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Connect Finexio to ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## Connect Finexio to Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Finexio to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Finexio tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Finexio through Elaichi ### Check where a supplier payment stands Accounts payable. When a supplier calls asking about an invoice, ask which Finexio payments cover it and whether they have gone out, then read the answer back without opening another screen. ### Load a batch of invoices at once Accounts payable. Hand over the approved invoices from the weekly run and have them created in Finexio in a single pass, then confirm the list matches what was approved. ### Reconcile drawdowns against payments before close Finance. Pull the drawdowns for the period alongside the payments they funded and spot anything that does not add up while there is still time to fix it. ### Set up a new supplier as a counterparty Procurement. Create the counterparty in Finexio and add the remittance contact from the onboarding form, so the first payment reaches the right person with the right details. ### Answer a payment inquiry with the image Treasury. When a supplier says a check never arrived, pull the payment image for that payment and send it along as proof of what was issued and when. ### Get told when payment status changes Finance operations. Set up a webhook in Finexio so the team hears when payments move, and update or retire it later as your process changes. ## Frequently asked questions ### How do I connect Finexio to Claude? Connect Finexio in Elaichi first, which asks for your Finexio API key and nothing else, so there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in as yourself and Finexio counterparties, invoices and payments are available in the conversation. ### Does Finexio work with ChatGPT and Cursor as well as Claude? Yes. Once Finexio is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Finexio once and every client picks it up. ### What can an AI agent actually do with my Finexio data? With Finexio connected, an agent can look up counterparties, invoices, payments, payment images and drawdowns and answer questions like which supplier payments went out this week or which invoices are still open. It can also create and update counterparties, load invoices in bulk, add or change supplier contacts, and manage the webhooks that tell your other systems when something in Finexio changes. ### Does connecting Finexio give the AI access to all of our payments? An agent working through Finexio sees only what the Finexio API key you connected can see, and Elaichi can narrow that further but never widen it. Restrictions decide which actions on counterparties, invoices, payments and contacts are allowed at all, and every request is made in the name of the person who signed in. Nothing about connecting Finexio grants access that did not already exist. ### Can my team share one Finexio connection? Yes. One person connects Finexio in Elaichi with the API key and shares the connection with a team, and nobody else on that team ever sees or handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log records exactly who looked up a payment or created a counterparty in Finexio. ### Can I stop an agent from deleting or changing things in Finexio? Yes. Restrictions in Elaichi apply per action, so you can allow reading Finexio invoices and payments while blocking the creation or updating of counterparties, the removal of supplier contacts, or any change to webhooks. A blocked action is never advertised to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it. ### What happens to a Finexio connection when someone leaves? When you offboard someone in Elaichi, their access to Finexio through the endpoint ends at once, in every client they had set up. A shared Finexio connection keeps working for everyone else on the team, because the API key was held by Elaichi rather than by the person leaving. If you ever want to remove Finexio entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together. ## All 26 Finexio tools Every tool below is callable through https://api.elaichi.ai/mcp once Finexio is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Finexio counterparties** (List). List all Finexio counterparties (buyers and suppliers). Returns: id, name, type, internal_id, created, updated, payment_method, country, address_1, and additional contact, banking, and 12-month spend fields. - **Create a Finexio counterparty** (Create). Create a new Finexio counterparty (Supplier). Returns: id, name, type, internal_id, created, updated, payment_method, ineligible_for_conversion, remit_data, and address and contact fields. Required: name, type, internal_id. - **Get single Finexio counterparty by ID** (Get). Get a single Finexio counterparty by id. Returns: id, name, type, internal_id, created, updated, address fields, payment_method, contact details, ineligible_for_conversion, and issue_one_disbursement_per_invoice. Required: id. - **Update a Finexio counterparty by ID** (Update). Fully replace an existing Finexio counterparty by id. Returns: id, name, type, internal_id, created, updated, address, payment_method, contact details, ineligible_for_conversion, and issue_one_disbursement_per_invoice. Required: id, name, type, internal_id. - **Finexio counterparties partial update** (Update). Partially update an existing Finexio counterparty by id; only submitted fields are modified. Returns: id, name, type, internal_id, created, updated, address, payment_method, contact details, ineligible_for_conversion, and issue_one_disbursement_per_invoice. Required: id. - **Finexio invoices bulk create** (Create). Create one or more Finexio invoices in a single batch (up to 500 per request). Returns an array of created invoice objects each containing id, amount_cents, currency, invoice_date, payment_id, originating_counterparty_id, and created. Required per invoice: amount_cents, currency, invoice_date, originating_counterparty_id, receiving_counterparty_id. - **List all Finexio invoices** (List). List all Finexio invoices. Returns each invoice record including id, amount_cents, currency, invoice_date, payment_id, originating_counterparty_id, receiving_counterparty_id, and created. - **Get single Finexio invoice by ID** (Get). Get a single Finexio invoice by id. Returns the full invoice object including id, amount_cents, currency, invoice_date, payment_id, status, originating_counterparty_id, receiving_counterparty_id, can_be_resubmitted, and created. Required: id. - **Get single Finexio payment image by ID** (Get). Get the check image URL for a Finexio payment. Returns: check_image_url (empty array when no image exists for the payment). Required: payment_id. - **List all Finexio payment images** (List). List check image URLs associated with a Finexio payment. Returns: check_image_url. Returns an empty array when no check image exists for the payment. Required: payment_id. - **Get single Finexio payment by ID** (Get). Get a single finexio payment by id. Returns the full payment object including id, amount_cents, currency, status, payment_method, tracking_id, events (full lifecycle history), invoices, created, updated, funding_drawdown_request_id, and refund/reissue metadata. Required: id. - **List all Finexio payments** (List). List finexio payments with optional filtering. Returns a paginated collection of payment records, each including id, amount_cents, currency, status, payment_method, tracking_id, events, invoices, created, updated, and refund/reissue metadata. Pages contain up to 100 items. - **Get single Finexio drawdown by ID** (Get). Get a finexio drawdown payment detail record by id (processor_request_id). Returns: id, supplier_name, amount_cents, status, payment_method, delivery_method, tracking_id, invoices, originating_counterparty_id, receiving_counterparty_id, supplier_ref_id, payment_group_id, and supplier address fields. Required: id. - **List all Finexio drawdowns** (List). List finexio reconciliation drawdowns. Returns: processor_request_id, bank_account_last_four, created, status, amount_cents, funding_complete_date, buyer_ref_id, buyer_name, originating_counterparty_id, and trace_id. At least one filter query parameter is recommended for performance. - **Create a Finexio supplier contact** (Create). Add one or more contacts to an existing finexio supplier. Returns: id, external_reference_id, name, email, phone, primary, payment_notification. Required: supplier_id, primary. - **Delete a Finexio supplier contact by ID** (Delete). Delete a finexio supplier contact by id. Returns a boolean true on successful deletion. Required: supplier_id, id. - **List all Finexio supplier contacts** (List). List all contacts for a finexio supplier. Returns: id, external_reference_id, name, email, phone, primary, payment_notification. Required: supplier_id. - **Update a Finexio supplier contact by ID** (Update). Update an existing finexio supplier contact by id. Returns: id, external_reference_id, name, email, phone, primary, payment_notification. Required: supplier_id, id, primary. - **Create a Finexio webhook** (Create). Create a new webhook subscription in Finexio for the currently logged-in user. Returns: id, event, url, created_at, updated_at, and subscription. Required: event, url, username, password. - **Delete a Finexio webhook by ID** (Delete). Delete a Finexio webhook subscription by id. Returns an empty 204 response on success. Required: id. - **Get single Finexio webhook by ID** (Get). Get details for a specific Finexio webhook subscription by id. Returns: id, event, url, created_at, updated_at, and subscription. Required: id. - **List all Finexio webhooks** (List). List all Finexio webhook subscriptions for the currently logged-in user. Returns items including id, event, url, created_at, updated_at, and subscription. - **Update a Finexio webhook by ID** (Update). Fully replace a Finexio webhook subscription by id. Returns: id, event, url, created_at, updated_at, and subscription. Required: id, event, url, username, password. - **Finexio webhooks partial update** (Update). Partially update a Finexio webhook subscription by id, sending only the fields to change. Returns: id, event, url, created_at, updated_at, and subscription. Required: id. - **List all Finexio counterparty history** (List). List the change history (changelog) of counterparties in Finexio. Returns each history entry as a counterparty record including id, name, type, created, updated, payment_method, internal_id, address fields, contact details, bank details, and ineligible_for_conversion reflecting the counterparty state at the time of each change. - **List all Finexio drawdown payments** (List). List individual payment records for a finexio drawdown identified by processor_request_id. Returns: id, supplier_name, amount_cents, status, payment_method, delivery_method, tracking_id, invoices, and supplier address fields for each payment in the drawdown. Required: processor_request_id.