# 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. Source: https://elaichi.ai/connectors/flowmate/ ## Facts | | | | --- | --- | | Application | FlowMate | | Category | Application Development | | AI tools | 20 | | 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 FlowMate is connected - List all FlowMate flows that are currently stopped. - Generate a flow from the onboarding FlowMate template. - Show which FlowMate users own the most flows. ## Connect FlowMate in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick FlowMate. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which FlowMate tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect FlowMate 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 FlowMate 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 FlowMate 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 FlowMate 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 FlowMate 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 FlowMate through Elaichi ### Find out why a flow failed overnight Engineering. 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. ### Stop a runaway flow without opening FlowMate Operations. 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. ### Spin up a new flow from a template Product. Pick an existing FlowMate flow template, describe the change you need, and have a working flow generated and named ready for review. ### Add a new hire to FlowMate IT. Create the FlowMate user, check which flows they now show up on, and confirm the account details in a single conversation. ### Check whether a customer's flow actually ran Support. 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. ### Pull weekly flow reporting into a summary Analytics. Ask for the FlowMate reporting figures for the week and get run counts, failures, and the flows that need attention in one short brief. ## 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 my team share one FlowMate connection? Yes. One person connects FlowMate in Elaichi and shares the connection with a team, and nobody else on the team ever handles the FlowMate API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who started, stopped, or edited a flow rather than a shared account. ### 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. ## All 20 FlowMate tools Every tool below is callable through https://api.elaichi.ai/mcp once FlowMate is connected, subject to the toolbox it is in and the restrictions on the caller. - **Create a FlowMate auth** (Create). Log in to FlowMate with username and password. Returns the authentication token and its id. Required: username, password. - **List all FlowMate flow** (List). List flows in flowmate. Returns the flow records including id, name, type, status, createdAt, and updatedAt. - **Get single FlowMate flow by ID** (Get). Get a single flowmate flow by id. Returns data containing the full flow record, plus meta. Required: id. - **Delete a FlowMate flow by ID** (Delete). Delete a flowmate flow by id. Returns an empty success object on success. Required: id. - **Update a FlowMate flow by ID** (Update). Update an existing flowmate flow by id. Returns data containing the updated flow record, plus meta. Required: id, name, graph, type. - **FlowMate flow start** (Start). Start a flowmate flow by flow_id. Returns data with the flow id and new status, plus meta. Required: flow_id. - **FlowMate flow stop** (Stop). Stop a flowmate flow's integration process by flow id. Returns the flow's id and new status under data, plus response metadata. Required: flow_id. - **List all FlowMate flow template** (List). List flow templates in flowmate available to the current user or their tenants. Returns: type, id, status, createdAt, updatedAt. Supports filtering by status, user, sort, search, and tags. - **Create a FlowMate flow template** (Create). Create a new flow template in flowmate. Returns data (the created template object, including id, name, type, status, createdAt, and updatedAt) and meta. Required: name, graph, type. - **Get single FlowMate flow template by ID** (Get). Get a single flow template in flowmate by id. Returns data (the template with id, name, status, createdAt, updatedAt) and meta. Required: id. - **Delete a FlowMate flow template by ID** (Delete). Delete a flow template in flowmate by id. Returns an empty 204 response on success. Required: id. - **Update a FlowMate flow template by ID** (Update). Update an existing flow template in flowmate by id. Returns data (the updated template with id, name, status, createdAt, updatedAt) and meta. Required: id. - **FlowMate flow template generate flow from template** (Generate). Generate a new flow in flowmate from an existing flow template. Returns data and meta, where data contains the new flow's id and status. Required: template_id. Deprecated. - **List all FlowMate user** (List). List all users in flowmate. Returns user records including id, username, firstname, lastname, status, tenant, roles, permissions, confirmed, and img. Optional: meta. - **Create a FlowMate user** (Create). Create a new user in flowmate. Returns the created user with id, username, firstname, lastname, status, tenant, roles, permissions, confirmed, and img. Required: username, firstname, lastname. - **Get single FlowMate user by ID** (Get). Get a single flowmate user by id. Returns: id, username, password. Required: id. - **FlowMate user get current** (Get). Get the current authenticated flowmate user. Returns: id, username, password. - **List all FlowMate reporting** (List). List execution counts for FlowMate reporting by time frame. Returns grouped execution records in data (_id, user, tenant, allFlows, executions, username) and period metadata with start, end, and totalExecutions. Optional: start, end, groupby. - **List all FlowMate log** (List). List flowmate logs for a tenant, optionally filtered by flow, step, or error-only mode. Returns the raw response object. Required: tenant. - **Create a FlowMate webhook** (Create). Send a JSON payload to a FlowMate incoming webhook by webhook_id (flow ID). The body is processed in the flow. Returns an empty JSON object on success. Required: webhook_id.