Accounting
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.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
26 tools
How to connect
How to connect FloQast to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect FloQast once
-
Open Connections, choose Add connection, and pick FloQast.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect FloQast to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect FloQast to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with FloQast through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Accounting
Find the reconciliations still open
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.
-
Controllership
Check close progress by entity
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.
-
Internal audit
Pull the audit trail for one control
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.
-
Compliance
Keep the controls library current
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.
-
Accounting operations
Set up next month's checklists
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.
-
Finance leadership
Get a close status summary
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.
Try asking
- “List FloQast controls with no owner assigned”
- “Which close checklists are still open this month”
- “Show FloQast processes by program and user group”
AI tools
FloQast tools for your AI agents
26 tools are ready to call through Elaichi's MCP endpoint the moment you connect FloQast, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting FloQast gets you
6 screens from the product, each doing one job for your FloQast account.
The agent
Ask about controls, get real answers.
Plain language questions run against live FloQast checklists, controls and processes.
- controls
- checklists
- processes
- programs
Ask Elaichi to work across your apps.
List FloQast controls with no owner assigned
Which close checklists are still open this month
Show FloQast processes by program and user group
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach FloQast.
One org MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
26 FloQast tools ready on connect.
Checklists, controls, processes, programs, folders and users, with no custom code.
- List all FloQast me
- List all FloQast users
- List all FloQast user groups
- List all FloQast processes
ElaichiToolsToolboxes
Every team gets its own toolbox.
Curate separate FloQast toolboxes for controls, close checklists and program owners.
- Controls
- Close
- Compliance
- Accounting
ElaichiToolboxesShared connections
Teammates use FloQast without the credential.
See who connected each account and how many teams and members share it.
- Controls
- Month end close
- Compliance
- Internal audit
ElaichiConnectionsAudit log
Every control change has a name on it.
When, who, what happened, type and resource for each FloQast call.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts the close digest.
Fetch FloQast checklists, group them, draft a digest, approve, post back.
FloQast digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch controls
FloQast
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
FloQast
Queued
Collections and dashboards
Close health, counted not summarized.
Four metrics, 14 days of checklists created and a team breakdown, refreshed on schedule.
FloQast health
Refreshed 4 minutes ago · every 15 minutes · from the controls collection
Controls
1,284 ↓ 12%
Checklists
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Controls created
Last 14 days
By team
Share of activity
Controls 34%
Month end close 27%
Compliance 21%
Internal audit 18%
Related connectors
More from the catalog
FAQ
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 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.
Put FloQast in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.