All clientsGuide
Connect FlowSEO to OpenClaw
According to its documentation, OpenClaw is an open-source AI assistant you run yourself, reachable through chat apps. One command adds FlowSEO, a second verifies the connection.
- 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.
- OpenClaw 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
Run these commands in the terminal.
Terminal openclaw mcp add flowseo --url https://mcp.flowconnect.one/flowseo --transport streamable-http openclaw mcp doctor flowseo --probe -
Add the sign-in
Add OAuth or the key as described below.
Sign-in
The address stays the same, only the sign-in differs.
OAuth
Set auth: "oauth" in mcp.servers.flowseo, then run openclaw gateway stop and openclaw mcp login flowseo. As long as OAuth is active, OpenClaw ignores a fixed header.
MCP key
Add the header under headers and use an environment variable instead of plain text. Otherwise openclaw mcp doctor warns about an exposed value.
"headers": { "Authorization": "Bearer ${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
- Codex
- Cursor
- Windsurf
- VS Code
- FlowAgents
- Hermes
- 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: OpenClaw Docs: MCP, retrieved on 08.11.2026