# FloQast MCP connector The FloQast connector brings your close checklists, reconciliations, controls, entities and audit trail to Claude, ChatGPT, Cursor and the Elaichi Agent, so each accountant can ask about and update the close inside their own FloQast access. Source: https://elaichi.ai/connectors/floqast/ ## Facts | | | | --- | --- | | Application | FloQast | | Category | Accounting | | 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 FloQast is connected - List FloQast controls with no owner assigned - Which close checklists are still open this month - Show FloQast processes by program and user group ## Connect FloQast in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick FloQast. 2. Optionally set Share with, then press Connect. 3. Paste a FloQast API key. One person generates a token in FloQast 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 FloQast tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect FloQast 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 FloQast 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 FloQast 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 FloQast 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 FloQast 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 FloQast through Elaichi ### Find the reconciliations still open Accounting. During close, ask which reconciliations remain unprepared or unreviewed across your entities and who owns each one. Get a list you can act on without clicking through every folder in FloQast. ### Check close progress by entity Controllership. Pull checklist and reconciliation analytics for each entity and see which ones are tracking to the close calendar and which are slipping. Ask the same question every morning of close and compare. ### Pull the audit trail for one control Internal audit. Ask for the FloQast audit trail entries behind a specific control or reconciliation and see who changed what and when. Hand the walkthrough evidence to an auditor without a screenshot exercise. ### Keep the controls library current Compliance. When a process changes, create the new control, update the description and owner on existing controls, and retire the ones that no longer apply. Every edit is recorded against the person who made it. ### Set up next month's checklists Accounting operations. Create the checklists for the coming period and update owners and due dates when someone is out or a task moves. Do it from a conversation instead of one form at a time. ### Get a close status summary Finance leadership. Ask for a plain language rundown of programs, processes and open items across all entities before the close review meeting. See where sign-offs are stuck without opening FloQast yourself. ## Frequently asked questions ### How do I connect FloQast to Claude? Two steps. First, connect FloQast in Elaichi, which means pasting in a FloQast API key from your FloQast account; 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 Elaichi endpoint https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi as yourself, and FloQast is ready to use. ### Does FloQast work with ChatGPT and Cursor as well as Claude? Yes. Once FloQast 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 FloQast once and every client you use picks it up. ### What can an AI agent actually do with my FloQast data? An agent can look up your FloQast checklists, reconciliations, controls, entities, programs, processes, users and tags, and read the checklist and reconciliation analytics behind them. It can create and update checklists and controls, update folders, check the status of a transaction, and pull audit trail logs when you need to show who did what. In practice that means asking which reconciliations are still open for an entity, or telling it to set up next month's checklists, and having it done. ### Does connecting FloQast give the AI access to everything in my FloQast account? No. Every call to FloQast through Elaichi runs as the person who signed in, so an agent can only reach the entities, folders and checklists that person can already see in FloQast. Elaichi can narrow that further with restrictions on specific actions, but it can never widen what FloQast itself allows. ### Can my team share one FloQast connection? Yes. One person connects FloQast in Elaichi and shares the connection with a team, and nobody else ever handles the FloQast API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every FloQast checklist update or control change. ### Can I stop an agent from deleting or changing things in FloQast? Yes. Restrictions in Elaichi work per action, so you can allow reading FloQast reconciliations and checklists while blocking the ability to delete a control or edit a folder. A blocked action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it. ### What happens to a FloQast connection when someone leaves? Offboarding a person in Elaichi ends their access to FloQast through every client at once. If they connected a FloQast account that is shared with a team, the connection keeps working for everyone else. When you do want it gone, disconnecting FloQast once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together. ## All 26 FloQast tools Every tool below is callable through https://api.elaichi.ai/mcp once FloQast is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all FloQast me** (List). Get information about the current user and API token in FloQast. Returns apiKeyId identifying the API key and userId representing the authenticated user. - **List all FloQast users** (List). List users in FloQast who have current or historical shared workspace access with the authenticated user. Returns user details including identifiers, names, and access information. - **List all FloQast user groups** (List). List all user groups accessible to the current tenant in FloQast. Returns groupId, name, and groupOwner for each user group, along with pagination metadata including totalCount, page, limit, and totalPages. - **List all FloQast processes** (List). List processes in FloQast. Returns a collection of processes including key fields such as id, name, and programId. Requires no path parameters. - **List all FloQast programs** (List). List compliance programs in FloQast. Returns fields like id, name, startPeriod, endPeriod, and status for each program. - **Get single FloQast folder by ID** (Get). Get metadata about a folder in FloQast by id. Returns key folder attributes such as name, creation date, and associated files. - **Update a FloQast folder by ID** (Update). Update the lock state of a specific folder in FloQast using id. Returns the updated folder details including its current lock status. - **List all FloQast controls** (List). List controls in FloQast with optional filters for month, year, activity status, programId, and controlId. Returns control details such as id, name, and status in the response. - **Get single FloQast control by ID** (Get). Get a specific control by id in FloQast. Requires id. Returns the control object including key fields such as name, description, owners, assignees, and related metadata. - **Create a FloQast control** (Create). Create multiple controls in FloQast (up to 20 at a time). Requires an array of control objects including fields like controlId, programId, processId, title, description, and ownership details. Returns the created controls with their assigned ids and metadata in the response. - **Update a FloQast control by ID** (Update). Update a control in FloQast using its id. Returns updated control details including processId, title, description, assertions, owners, assignees, and frequency information. - **Delete a FloQast control by ID** (Delete). Delete an inactive control in FloQast using id. The response confirms successful deletion of the specified control. - **List all FloQast checklists** (List). List checklists in FloQast for a specific month and year. Requires filter[month] and filter[year]. Returns checklist details including templateId, description, entityId, and related financial period information. - **Create a FloQast checklist** (Create). Create a new checklist item in FloQast. Requires companyId, folderName, schedule, signatures, and description. Returns the created checklist item including its id, description, schedule details, and signature assignments. - **Update a FloQast checklist by ID** (Update). Update a checklist item in FloQast by id. Requires id. Returns updated checklist details including companyId, folderName, description, schedule, signatures, and tagIds. - **List all FloQast reconciliations** (List). List reconciliations in FloQast for a given period. Requires filter[month] and filter[year] or filter[modifiedBefore]/filter[modifiedSince]. Returns reconciliation details including account, status, and related TLCs. - **List all FloQast checklist analytics** (List). Get checklist analytics in FloQast for a specific month and year or based on modification dates. Returns key metrics including checklist completion rates, progress insights, and TLC data for each entity and workflow. - **List all FloQast reconciliation analytics** (List). List reconciliations in FloQast for a given filter[month] and filter[year]. Returns reconciliation details including TLCs and reconciliation progress metrics for the specified month and year. - **List all FloQast audit trail logs** (List). List audit-trail-logs in FloQast. Returns logs for all API keys within a client, including details such as timestamp, userApiKey._id, and request metadata. Requires specifying filter[startDate]. - **Get single FloQast transaction status by ID** (Get). Get the status of a transaction event in FloQast using the id. Returns fields showing the current processing state and any associated messages or errors. - **List all FloQast entities** (List). List all entities in FloQast. Returns key information such as entity name, ID, and related metadata for each entity. - **Get single FloQast entity by ID** (Get). Get a specific entity in FloQast using the required id. Returns key fields describing the entity such as its unique identifiers and related metadata. - **List all FloQast tags** (List). List all tags in FloQast. Returns tag id, name, and related metadata for each tag under a TLC. - **FloQast tags attachments** (Action). Attach or detach a tag in FloQast. Requires system, systemId, action, and name. The response confirms whether the tag was attached or detached successfully. - **List all FloQast chart of accounts** (List). Get chart of accounts data in FloQast. Returns account_id, name, type, and related entity information used for financial reporting. - **FloQast chart of accounts upload** (Upload). Upload Chart of Accounts data in FloQast. Requires entityId and accounts with number and name. Returns confirmation of processed accounts and associated entity information.