Frequently Asked Questions
What is the Flowkon MCP connector?
It's a hosted bridge, built on the open Model Context Protocol, between your Flowkon workspace and any MCP-speaking AI client — Claude, ChatGPT, or your own. It holds no database and no business logic of its own: every tool call is a live, scoped request to Flowkon's own API, so your assistant always sees exactly what's in your workspace right now.
How do I connect it?
Add https://mcp.flowkon.io/mcp as a custom connector in your AI client's settings, then sign in on Flowkon's own hosted login page — email, password, and 2FA if you have it enabled. Your credentials go straight to Flowkon; they never pass through the model or the chat window.
Which AI assistants work with it?
Claude and ChatGPT both support the hosted connector out of the box, and any other MCP-compatible client can connect the same way over OAuth. Developers can also run the same server locally over stdio for Claude Desktop, Claude Code, or the MCP Inspector.
What can my AI actually do with it?
54 tools spanning lead search and LinkedIn search, campaign creation/stats/flow-building, inbox and messaging, workspace and team management, tags, placeholders, integrations and booking. On top of that, 5 live resources (your workspaces, connected LinkedIn accounts, dashboard stats, a lead, a campaign) and 4 guided prompts that chain several tool calls into one ready-made workflow, like a campaign stats report or a workspace health summary.
What stops it from doing something I didn't ask for?
Almost every tool is read-only and runs immediately. The two that change something real — creating a campaign and pausing or resuming one — always come back first with exactly what would happen and wait for your explicit yes before anything is applied.
How is authentication handled?
The hosted connector runs a real OAuth 2.1 flow, resolving each connected client's own Flowkon identity on every single call — so one server safely serves many different Claude or ChatGPT users at once, each acting only as themselves. Self-hosted locally, you authenticate once through a small local browser login window, and that session is reused on every restart — no password is ever typed into the chat.
Is my data secure?
The server is a thin, typed wrapper around Flowkon's existing REST API — it keeps no copy of your data and Flowkon's backend stays the single source of truth. Every request is scoped to the workspace you're signed into, and the tools that change something require your explicit confirmation first.
Can I self-host it instead of using the hosted connector?
The server is a thin, typed wrapper around Flowkon's existing REST API — it keeps no copy of your data and Flowkon's backend stays the single source of truth. Every request is scoped to the workspace you're signed into, and the tools that change something require your explicit confirmation first.
.webp)
