CoS Codex Bridge vs Flanner
A side-by-side look at the CoS Codex Bridge and Flanner MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
F
FlannerCoding Agents · Local subprocess (stdio)Keeps AI coding agents' plan and design markdown managed and versioned, for Claude Code and Codex.41FairAuth: not declaredVerdict: choose CoS Codex Bridge for coding agents work as a local process; choose Flanner for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose CoS Codex Bridge when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
FChoose Flanner when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | F Flanner | |
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 41/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 5 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View CoS Codex Bridge | View Flanner |
Tools & capabilities
CoS Codex Bridge tools
No tool names declared yet. Check the project README from the listing page.
Flanner tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
CoS Codex Bridge
{
"mcpServers": {
"cos-codex-bridge": {
"command": "npx",
"args": [
"-y",
"cos-codex-bridge"
]
}
}
}
Flanner
{
"mcpServers": {
"flanner": {
"command": "uvx",
"args": [
"flanner"
]
}
}
}
Frequently asked questions
CoS Codex Bridge is categorized under Coding Agents and uses a local stdio subprocess. Flanner belongs to Coding Agents and uses a local stdio subprocess. Pick CoS Codex Bridge for coding agents work and Flanner for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
CoS Codex Bridge has no declared pricing — check the project's own site. Flanner has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add cos-codex-bridge and flanner as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, CoS Codex Bridge has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 3 GitHub stars. Flanner has 41/100 (Fair) with 0 views, 0 installs and 5 GitHub stars.