Zenodo vs Filesystem
A side-by-side look at the Zenodo and Filesystem MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Zenodo for research work as a local process; choose Filesystem for file systems as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Zenodo when
- You need dedicated capabilities in the Research domain.
- You prefer a local stdio subprocess transport.
- You want tools like
search, record, record_files.
Choose Filesystem when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
path, head, tail.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Research | File Systems |
| Quality signal | 57/100 · Good | 85/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 91,512 |
| Directory activity | 3 views 0 installs 0 upvotes | 11 views 0 installs 0 upvotes |
| Tools | 5 | 17 |
| Full listing | View Zenodo | View Filesystem |
Tools & capabilities
Zenodo tools 5
searchSearch Zenodo open-research repository for datasets, publications, software, and other research outputs by keyword query. Filterable by type, community, and sort order (mostrecent/bestmatch/mostviewed); returns metadata, DOI, and file links.recordSingle record by Zenodo id.record_filesList files attached to a Zenodo record by its numeric id. Returns file names, sizes, checksums, and direct download URLs.communitiesList or search Zenodo communities (thematic collections of records) by optional keyword query; returns community id, title, description, and record count.community_recordsFetch paginated records belonging to a Zenodo community by its slug id (e.g. "openaire"). Returns record metadata, DOIs, and file links for all items in the community.
Filesystem tools 17
pathheadtailpathscontenteditsoldTextnewTextdryRunsortBysourcedestination- +5 more on 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.
Zenodo
{
"mcpServers": {
"zenodo": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-zenodo"
]
}
}
}
Filesystem
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem"
]
}
}
}
Frequently asked questions
Zenodo is categorized under Research and uses a local stdio subprocess. Filesystem belongs to File Systems and uses a local stdio subprocess. Pick Zenodo for research work and Filesystem for file systems.
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.
Zenodo has no declared pricing — check the project's own site. Filesystem is listed as free. Auth: no auth required. 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 zenodo and filesystem as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Zenodo has a quality signal of 57/100 (Good) with 3 views, 0 installs and 0 GitHub stars. Filesystem has 85/100 (Excellent) with 11 views, 0 installs and 91,512 GitHub stars.