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.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldSupermemoryShortlist candidatecodaMCP100 Recommended
Task fit
Best for
  • Users who want persistent cross-session memory/recall with explicit project scoping.
  • Collaborative document and structured-table workflows in Coda.
Not ideal for
  • Privacy-sensitive workflows that should not persist conversation/project memory outside the client.
  • Teams outside the publisher ecosystem or without least-privilege credentials
Avoid when
  • Do not store secrets or sensitive personal/project data unless Supermemory retention/project boundaries meet your requirements.
  • The connected identity is broader than the task requires
  • Tool calls cannot be reviewed before consequential mutations
Provenance
Provenance details

First-party MCP

endpoint:https: · 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
Shared repository stars

31,345

Shared repository stars (not MCP-specific) · checked 2026-10-21

Not documented
Client coverage
Client coverage detailsNot documented
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationOAuth is the default; API key/Bearer authentication is an alternative.The official hosted endpoint supports OAuth 2 and personal access tokens.
CostSupermemory plan/API limits and model/provider costs apply.The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.
PermissionsCan add/read persistent memories available to the authorized account/project.Coda document sharing, user permissions, admin controls, and OAuth or PAT scope determine access.
Data handlingSubmitted memories are intentionally persisted by the Supermemory service; project scoping and retention are therefore central privacy controls.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
  • Promising signal, but it ranks below the current Recommended/Shortlist admission cohort on maturity, uniqueness, publisher trust, security clarity, or MCP-native evidence.
  • Documents and tables can contain broad internal knowledge, and write tools can alter shared operational records.
Risk contextIntentional persistent storage can retain sensitive context beyond the current session.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 review2026-10-212026-07-30
Candidate evidence2026-10-21T00:00:00Z2026-09-24T04:25:05.554391Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →