Connecting Claude and Other AI Clients
Edge MCP access is available on the Edge plan.
Flux exposes an MCP server at https://www.fluxgraph.app/mcp. Once connected, your AI client can query your post history, score drafts, research prospects, and manage your research streams in plain language.
| You use | How you connect |
|---|---|
| Claude on the web, desktop app, or mobile | Add a connector and sign in. No key needed. |
| Claude Code, Cursor, Zed, or another MCP client | Paste a config with your MCP key. |
Claude (web, desktop, and mobile)
You need a Claude account (custom connectors work on every Claude plan; Free allows one) and an Edge plan. If you don't have a Flux account yet, signing in creates one. Connectors you add in claude.ai also appear in the Claude desktop and mobile apps.
Add a custom connector. In claude.ai or the Claude desktop app, open Settings → Connectors, click Add custom connector, name it Flux, and paste https://www.fluxgraph.app/mcp.
Choose "Sign in when needed" for authentication and "Register automatically" for client registration.
Claude may preselect No sign-in. Change it: with that setting the connector can never reach your own data.
Sign in and approve. The first time a tool needs your account, Claude shows Connect. Sign in with Google or your Flux email (6-digit code or password) and click Approve.
Try it. Enable Flux from the tools menu in a chat and ask: "List my tracked LinkedIn profiles."
Signing out of Flux ends the connection; Claude asks you to sign in again next time. If your organization's Claude admin manages connectors, ask them to add the URL above, and each person signs in with their own Flux account.
Claude Code, Cursor, Zed, and other clients
Generate an MCP key. In Flux, open Settings → MCP → Developer setups and click Generate MCP key. It starts with flux_ and is shown once. That panel also shows the snippets below with your key filled in.
Add Flux to your client. Pick your client and replace YOUR_API_KEY with your key.
Run this in a terminal to add Flux for every project:
claude mcp add --transport http --scope user flux \
https://www.fluxgraph.app/mcp \
--header "Authorization: Bearer YOUR_API_KEY"Claude Code can't use browser sign-in with Flux yet (it picks a random local port for the sign-in callback, and Flux's sign-in server needs an exact one), so a key is the supported path.
Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):
{
"mcpServers": {
"flux": {
"url": "https://www.fluxgraph.app/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Add this to your Zed settings.json, or use Settings → AI → MCP Servers → Add Remote Server:
{
"context_servers": {
"flux": {
"url": "https://www.fluxgraph.app/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Any client that supports HTTP transport and custom headers works. Most read this shape:
{
"mcpServers": {
"flux": {
"type": "http",
"url": "https://www.fluxgraph.app/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Try it. Ask: "List my tracked LinkedIn profiles." If your client lists the Flux tools and returns your profiles, you're connected.
The key only ever reaches your own data. Generating a new MCP key invalidates the previous one.
Troubleshooting
Next steps
- MCP tool reference: every tool and its inputs. Most analytics tools are free; live LinkedIn lookups,
suggest_angles,save_post, stream runs, and constellation mapping use credits. - Workflows with Flux MCP: ready-to-use prompts for content analysis, prospecting, and draft scoring.