All clientsGuide
Set up FlowSEO in Codex
One entry in the Codex configuration, then a login or an environment variable.
- MCP address
https://mcp.flowconnect.one/flowseo- Sign-in
- OAuth or key
- Status
- MCP-compatible
Requirements
- A FlowSEO package or a trial.
- A domain in FlowSEO. You add new domains yourself, in the browser or through your agent.
- Codex is installed.
- For OAuth: your account with FlowConnect. The connection always reaches every domain of your team.
- For sign-in with a key: an MCP key you create in FlowConnect under Developer › MCP (/entwickler/mcp). It reaches every domain of your team.
Steps
-
Add the server
Extend the configuration.
~/.codex/config.toml [mcp_servers.flowseo] url = "https://mcp.flowconnect.one/flowseo" -
Sign in
Run the login or use a key as described below.
Terminal codex mcp login flowseo
Sign-in
The address stays the same, only the sign-in differs.
OAuth
With codex mcp login flowseo you sign in through the browser.
MCP key
Instead of the login, enter the name of an environment variable and set it to your key. The value of the setting is the name of the variable, not the key.
[mcp_servers.flowseo]
url = "https://mcp.flowconnect.one/flowseo"
bearer_token_env_var = "FLOWSEO_MCP_KEY"
Verify
Ask your agent about your domains. If it answers with your domain, the connection is working.
Example data: Lumivo Werkhaus GmbH (fictional)
Troubleshooting
Other clients
- Claude
- Claude Code
- ChatGPT
- Cursor
- Windsurf
- VS Code
- FlowAgents
- Hermes
- OpenClaw
- Zed
- GitHub Copilot CLI
- Cline
“MCP-compatible” means the client speaks the protocol according to its documentation. A test date only appears here once a real run against our server has taken place.
Source of the steps: Codex: MCP, retrieved on 08.11.2026