Give Claude, ChatGPT, Cursor or any MCP-capable assistant safe, read-first access to your Flowmingo recruiting pipeline — scoped to your organisation only.
There are two ways to connect. Most clients (Claude Desktop, ChatGPT) support one-click sign-in — pick that. Use an API key only if your client asks for a static token.
Add the server URL to your client and choose to sign in when prompted. A Flowmingo page opens, you authorise once, and the client stores a revocable token (it auto-refreshes — no copy-pasting keys).
Claude Desktop / Cursor — add this to your MCP config:
{
"mcpServers": {
"flowmingo": {
"type": "http",
"url": "https://mcp.flowmingo.ai/mcp"
}
}
}
ChatGPT (Developer mode / connectors) — add a custom connector, paste the URL above, and complete the sign-in popup.
Prefer a static token, or your client only supports header auth? Mint a key in Settings → API keys in the Flowmingo portal, then send it as the x-api-key header (or Authorization: Bearer fl_…).
{
"mcpServers": {
"flowmingo": {
"type": "http",
"url": "https://mcp.flowmingo.ai/mcp",
"headers": {
"x-api-key": "fl_live_YOUR_KEY"
}
}
}
}
Your key never leaves your client config. Revoke it any time from the portal.
Reads are always allowed. Writes always show you a preview first and only run when you confirm — and never touch more than 50 applicants at once.
Everything is scoped to your organisation by the Flowmingo API — the agent can never see another company's data.
Need a hand connecting? Reply to your Flowmingo onboarding thread and we'll jump on it. During the pilot we log tool usage to improve the product; we never store your API keys in plain text or share your candidate data.