FloQast MCP connector
The FloQast connector brings your close checklists, reconciliations, controls, entities and audit trail to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each accountant can ask about and update the close inside their own FloQast access.
- Connects with an API key
- Free 14-day trial
- No credit card
List FloQast controls with no owner assigned
Working in FloQast with Elaichi
-
List all FloQast me
-
List all FloQast users
-
List all FloQast user groups
How to connect FloQast to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
FloQast MCP connector for 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.
FloQast MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
FloQast MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
FloQast MCP connector for 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.
FloQast MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with FloQast through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in FloQast is logged.
-
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”
What connecting FloQast gets you
6 screens from Elaichi, each doing one job for your FloQast account.
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, Cursor or Microsoft Copilot
The agent
Ask about controls, get real answers.
Plain language questions run against live FloQast checklists, controls and processes.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach FloQast.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
26 FloQast tools ready on connect.
Checklists, controls, processes, programs, folders and users, with no custom code.
Toolboxes
Every team gets its own toolbox.
Curate separate FloQast toolboxes for controls, close checklists and program owners.
Shared connections
Teammates use FloQast without the credential.
See who connected each account and how many teams and members share it.
Audit log
Every control change has a name on it.
When, who, what happened, type and resource for each FloQast call.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
FloQast digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
FloQast
Queued
Automations
A schedule starts the close digest.
Fetch FloQast checklists, group them, draft a digest, approve, post back.
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%
Collections and dashboards
Close health, counted not summarized.
Four metrics, 14 days of checklists created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for FloQast
All three can connect FloQast to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over FloQast tools | Allow or restrict single FloQast tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per FloQast call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
Questions, answered
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, Microsoft Copilot, 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 restricting the ability to delete a control or edit a folder. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot and every other client together.
Does the FloQast MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. FloQast is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for FloQast?
Yes. Both let Claude, ChatGPT or Cursor use FloQast. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every FloQast call.
How is Elaichi different from Composio for FloQast?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to FloQast: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put FloQast in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot