OpenAI · Codex

Give ChatGPT and Codex live LinkedIn data

Flux is a remote MCP server. Codex connects in 60 seconds with a bearer key; here’s that setup, plus exactly where ChatGPT’s web connectors stand today.

Start in your browser Connect your agent

Connector URL: https://fluxgraph.app/mcp· auth: bearer API key

Read this first

What works today, plainly.

Codex CLI & Codex in VS Code

Fully supported. Codex speaks Streamable HTTP and lets you set the bearer token, so Flux drops straight in. Setup is below and takes about a minute.

ChatGPT web connectors

Not yet. ChatGPT’s custom-connector form accepts OAuth or no authentication — there’s no field for a bearer token or a custom header, and Flux authenticates with an API key. OAuth is on the roadmap; say so and it moves up.

Codex setup · 60 seconds

Three steps, one endpoint.

Flux exposes a single Streamable-HTTP MCP endpoint at https://fluxgraph.app/mcp. Codex reads the token from an environment variable, so the key never lands in a config file.

1
Generate an API key
Log in and open Settings → MCP, then click Generate MCP key. It’s shown exactly once. Keys start with flux_ and can be revoked at any time.

Register the server with Codex

Export the key, then let codex mcp add write the config for you:

terminal

export FLUX_API_KEY=flux_xxx

codex mcp add flux \
  --url https://fluxgraph.app/mcp \
  --bearer-token-env-var FLUX_API_KEY

Or edit ~/.codex/config.toml by hand — same result, and the same file the Codex VS Code extension reads:

~/.codex/config.toml

# ~/.codex/config.toml
[mcp_servers.flux]
url = "https://fluxgraph.app/mcp"
bearer_token_env_var = "FLUX_API_KEY"

3
Try it
Start a Codex session and ask: “List my tracked LinkedIn profiles.” It calls list_profiles. If that answers, all 63 tools are live. Make sure FLUX_API_KEY is exported in the shell Codex runs in — it’s read at connect time.

Three things to ask first

Real questions, in customers’ words.

Swap the placeholder for a LinkedIn profile or post URL and these run exactly as written.

“Get the data for my client's LinkedIn posts in one place”

Every profile you track, every post, every metric — returned as structured data your agent can summarize, chart, or drop straight into a client report.

list_profilesget_postsget_profile_summary

“What are the top performing posts of <person> so I can study their content?”

Pulls their recent posts live, ranks them by engagement, and reads the text back. Paste their LinkedIn profile URL in place of the placeholder.

linkedin_profile_postsget_posts

“Who engaged with this post and which of them work at target accounts?”

Fetches the reactors and commenters, groups them by current employer, and flags employees and alumni of the accounts you name.

linkedin_post_reactionsget_post_engagers_by_companyget_alumni_engagers

FAQ

The awkward questions.

Why can’t I add Flux from ChatGPT’s connector screen?

ChatGPT’s custom-connector form (Settings → Connectors, with Developer mode on) offers two auth choices: OAuth, or no authentication. There is no field for a static bearer token or a custom request header. Flux authenticates with a bearer API key, so there is nothing valid to put in that form yet. Codex reads the same endpoint and does support the header — that’s the working path today.

Is OAuth coming?

It’s the unlock for both ChatGPT web and claude.ai’s browser connector directory, and it’s on the roadmap. Tell us you want it and it moves up the list.

Where does Codex read its MCP config from?

~/.codex/config.toml, shared by the Codex CLI and the Codex extension in VS Code. The codex mcp add command writes that same file, so either route works.

Why an env var instead of pasting the key?

bearer_token_env_var tells Codex the name of the variable to read at connect time, so the key never lands in a config file you might commit. Codex sends it as Authorization: Bearer.

I get a 401.

The key is missing, malformed, or revoked. Confirm FLUX_API_KEY is exported in the shell Codex actually runs in, and that it starts with flux_. Generate a fresh key from Settings → MCP.

Also available

Prefer Claude?

Claude Code, Claude Desktop, Cursor, and Zed all take the bearer header directly — same endpoint, one command.

Claude setup →All 63 tools →

One ask away.

MCP access is on Edge — $15/month or $150/year, including all 63 tools and the dashboard.