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 | Anytype MCPShortlist candidate | Hugging Face MCPMCP100 Recommended |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP Anytype · Publisher source ↗ | First-party MCP Hugging Face · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Not documented Package: Not documented | Repo: Sep 23, 2026 Package: Not documented |
| Popularity evidence | ||
| GitHub stars | 534 GitHub stars · checked 2026-10-20 | 296 GitHub stars · checked 2026-09-24T04:14:16.295000Z |
| Package downloads / 30 days | 6,370 package downloads / 30 days · checked 2026-10-20 | No reliable download data |
| 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 | Anytype API key supplied as a Bearer authorization header to the local Anytype API. | The hosted server supports the current documented Hugging Face OAuth or bearer-token paths. Tool advertisement or discovery configuration is not a server-side authorization boundary for a caller that already knows a tool name; actual authority remains bounded by the authenticated Hugging Face account and token permissions. |
| Cost | No separate MCP fee is documented for the open-source server/package. | Hub search and the open-source server have no separately documented MCP fee. Hugging Face Jobs, sandboxes, inference, storage, hardware-backed Spaces, and the AI client can incur normal account charges. |
| Permissions | Authority follows the Anytype API key. The current wrapper exposes `auth_whoami` to inspect credential permissions; API-key management/pairing operations are intentionally excluded. | Base tools search and navigate Hugging Face Hub resources and documentation. Optional tools can create and write repositories, manage sandbox files, run or schedule Jobs, and invoke selected or dynamically discovered community Spaces, bounded by the authenticated Hugging Face token and configured tool set. |
| Data handling | By default the MCP connects to the local Anytype API. File downloads are written to a private temporary directory. Debug logging explicitly omits authorization headers, arguments, payloads, and complete operation tables. | Queries and results pass through Hugging Face's hosted MCP service. Community Space calls send their arguments to the selected Space and return its outputs to the client. Jobs and sandboxes can process files and compute inputs on Hugging Face infrastructure. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | The MCP can create, edit, and delete knowledge-base objects and can download files. A leaked API key exposes the permissions granted to that key. | Begin with search-only tools and a least-privilege token. Disable dynamic Spaces, repository writes, Jobs, and sandboxes unless separately approved; review every community Space as third-party code and never send secrets or regulated data. This documentary review does not claim MCP100 execution testing. |
| Evidence date | ||
| Editorial review | 2026-10-19 | 2026-07-24 |
| 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 →