Project Context MCP vs Flanner
A side-by-side look at the Project Context MCP and Flanner MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
F
FlannerDeveloper Tools · Local subprocess (stdio)Keeps AI coding agents' plan and design markdown managed and versioned, for Claude Code and Codex.41FairAuth: not declaredVerdict: choose Project Context MCP for developer tools work as a local process; choose Flanner for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Project Context MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
FChoose Flanner when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | F Flanner | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 51/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 5 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Project Context MCP | View Flanner |
Tools & capabilities
Project Context MCP 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.
Project Context MCP
{
"mcpServers": {
"ericbrown-project-context-mcp": {
"command": "uvx",
"args": [
"project-context-mcp"
]
}
}
}
Flanner
{
"mcpServers": {
"flanner": {
"command": "uvx",
"args": [
"flanner"
]
}
}
}
Frequently asked questions
Project Context MCP is categorized under Developer Tools and uses a local stdio subprocess. Flanner belongs to Developer Tools and uses a local stdio subprocess. Pick Project Context MCP for developer tools work and Flanner for developer tools.
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.
Project Context MCP is listed as free. Auth: no auth required. 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 ericbrown-project-context-mcp and flanner as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Project Context MCP has a quality signal of 51/100 (Good) with 3 views, 0 installs and 6 GitHub stars. Flanner has 41/100 (Fair) with 0 views, 0 installs and 5 GitHub stars.
