Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | OpenFlowKit MCPShortlist candidate | codaMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | Community implementation OpenFlowKit · Publisher source ↗ | First-party MCP ecosystem:coda · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Not documented Package: Not documented | Repo: Not documented Package: Not documented |
| Popularity evidence | ||
| Package downloads / 30 days | 222 package downloads / 30 days · checked 2026-10-20 | No reliable download data |
| Shared repository stars | 898 Shared repository stars (not MCP-specific) · checked 2026-10-20 | Not documented |
| Client coverage | ||
| Client coverage details | Not documented | Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Local stdio mode requires no account or provider key. The local live bridge supports an optional `OPENFLOWKIT_BRIDGE_TOKEN`; the hosted connector requires no sign-in. | The official hosted endpoint supports OAuth 2 and personal access tokens. |
| Cost | OpenFlowKit is free to use; external AI-provider charges may apply when used through a model provider. | The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply. |
| Permissions | Local mode can edit diagrams/files and can inspect a codebase path explicitly supplied to analysis/discovery tools. The live bridge is localhost-bound with host/origin checks. | Coda document sharing, user permissions, admin controls, and OAuth or PAT scope determine access. |
| Data handling | Local stdio calls no outside service. The hosted endpoint is stateless and stores nothing. The browser app keeps diagrams locally and sends basic usage stats that can be disabled. | Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive files & knowledge information. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Local mode can read codebases and write diagram files; live mode edits the open canvas. The hosted connector is read-only/reduced compared with the local server. | Documents and tables can contain broad internal knowledge, and write tools can alter shared operational records. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review. |
| Evidence date | ||
| Editorial review | 2026-10-19 | 2026-07-30 |
| Candidate evidence | 2026-10-20 | 2026-09-24T04:25:05.554391Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →