VS Code reads MCP servers from .vscode/mcp.json in your project.
With a key
Create a key in FlowConnect under Developer › MCP, as described in MCP keys for FlowSEO, and copy it. It is shown only once.
So the key doesn't end up in the file, VS Code asks for it at startup:
{
"inputs": [
{ "type": "promptString", "id": "flowseo-key", "description": "FlowSEO MCP key", "password": true }
],
"servers": {
"flowseo": {
"type": "http",
"url": "https://mcp.flowconnect.one/flowseo",
"headers": { "Authorization": "Bearer ${input:flowseo-key}" }
}
}
}
By signing in
Enter only type and url. VS Code offers you the sign-in when the server starts. Sign in to FlowConnect, choose your team and confirm.
Good to know
- A connection by sign-in and a key both reach all domains of your team.
- According to the client's documentation, FlowSEO is MCP-compatible, but a real run against our server is still pending. If a menu or file looks different for you, the client's current documentation applies.