Application Development
FlowMate MCP connector
The FlowMate connector lets Claude, ChatGPT, Cursor, and other MCP clients list, start, stop, and update your FlowMate flows, build flows from templates, and read run logs and reports, all inside your own FlowMate access with every action recorded.
-
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.
How to connect
How to connect FlowMate to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect FlowMate once
-
Open Connections, choose Add connection, and pick FlowMate.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a FlowMate API key. One person generates a token in FlowMate 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 FlowMate 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 FlowMate 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 FlowMate 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 FlowMate 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 FlowMate through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Engineering
Find out why a flow failed overnight
Ask which FlowMate flows ran last night, pull the logs for the one that failed, and get a plain summary of where it went wrong before standup.
-
Operations
Stop a runaway flow without opening FlowMate
When a flow is firing too often or hitting the wrong system, tell the assistant to stop it by name, then start it again once the fix is in.
-
Product
Spin up a new flow from a template
Pick an existing FlowMate flow template, describe the change you need, and have a working flow generated and named ready for review.
-
IT
Add a new hire to FlowMate
Create the FlowMate user, check which flows they now show up on, and confirm the account details in a single conversation.
-
Support
Check whether a customer's flow actually ran
Look up the flow tied to a ticket, read its recent log entries, and give the customer a clear answer instead of asking engineering to dig.
-
Analytics
Pull weekly flow reporting into a summary
Ask for the FlowMate reporting figures for the week and get run counts, failures, and the flows that need attention in one short brief.
Try asking
- “List all FlowMate flows that are currently stopped.”
- “Generate a flow from the onboarding FlowMate template.”
- “Show which FlowMate users own the most flows.”
AI tools
FlowMate tools for your AI agents
20 tools are ready to call through Elaichi's MCP endpoint the moment you connect FlowMate, 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 FlowMate gets you
6 screens from the product, each doing one job for your FlowMate account.
The agent
Ask about flows, get real answers.
Plain language questions return live FlowMate flows, templates and users.
- flows
- flow templates
- users
- auths
Ask Elaichi to work across your apps.
List all FlowMate flows that are currently stopped.
Generate a flow from the onboarding FlowMate template.
Show which FlowMate users own the most flows.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Any MCP client reaches FlowMate over OAuth, with no SDK or shared key.
Copy the endpoint
Tool catalog
20 FlowMate tools ready to call.
Flows, templates, users and auths are covered with no custom code.
- Create a FlowMate auth
- List all FlowMate flow
- Get single FlowMate flow by ID
- Delete a FlowMate flow by ID
Toolboxes
Every team gets its own toolbox.
Curate FlowMate flow and template tools per team, scoped to their work.
- Platform
- Automation engineering
- Support
- Security
Shared connections
Teammates run flows without touching credentials.
Each FlowMate connection shows who added it and which teams share it.
- Platform prod
- Platform staging
- Automation engineering
- Support tier one
Audit log
Every flow start is on record.
See when, who, what happened, type and resource for each FlowMate call.
- When
- Who
- What happened
- Type
Launching 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 fires, a digest ships.
Six steps fetch FlowMate flows, group them, draft, await approval, post back.
FlowMate digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch flows
FlowMate
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
FlowMate
Queued
Collections and dashboards
FlowMate health, counted on a schedule.
Four metrics, 14 days of flows created and a per team breakdown.
FlowMate health
Refreshed 4 minutes ago · every 15 minutes · from the flows collection
Flows
1,284 ↓ 12%
Flow templates
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Flows created
Last 14 days
By team
Share of activity
Platform prod 34%
Platform staging 27%
Automation engineering 21%
Support tier one 18%
FAQ
Frequently asked questions
How do I connect FlowMate to Claude?
Connecting FlowMate takes two steps. First, open Elaichi, choose FlowMate, and paste in your FlowMate API key; there is no OAuth app 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. Claude will ask you to sign in to Elaichi and FlowMate is ready to use.
Does FlowMate work with ChatGPT and Cursor as well as Claude?
Yes. Once FlowMate 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 FlowMate once and every client you use picks it up.
What can an AI agent actually do with my FlowMate data?
With FlowMate connected, an AI agent can list your flows, look up a specific one, update it, start or stop it, and delete it if you allow that. It can browse and create flow templates, generate a new flow from a template, read run logs and reporting, look up FlowMate users or add one, and set up a webhook. In practice that means asking in plain language why a flow failed, or asking for a new flow to be built from a template, and getting it done.
Does connecting FlowMate give the AI access to every flow and user in my workspace?
No. Access to FlowMate follows the FlowMate account whose API key was used to connect, so the AI can only see and change what that account can see and change in FlowMate. Elaichi can narrow that further, for example to reading flows and logs only, but it can never grant more than the underlying FlowMate account has.
Can I stop an agent from deleting or changing flows in FlowMate?
Yes. Restrictions in Elaichi apply per action, so you can allow an agent to list FlowMate flows and read logs while blocking it from deleting flows, deleting templates, or changing users. A blocked action is never shown to Claude, ChatGPT, or any other client at all, so no prompt, however worded, can reach it.
What happens to a FlowMate connection when someone leaves?
When you offboard a person in Elaichi, their access to FlowMate through Elaichi ends immediately, across every client they were using. A FlowMate connection they shared with a team keeps working for everyone else on that team. If you want FlowMate gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Put FlowMate in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.