zenodo-mcp-server

An MCP server that allows LLM agents to query and interact with Zenodo repositories using the Zenodo REST API.

• Unauthenticated access – search and inspect public records without an API key
• Session API key – supply a personal access token at runtime via the set_api_key tool
• Persistent service account – set ZENODO_API_KEY environment variable for a long-lived key
• Optional write access – create, update, and publish depositions (enabled via ZENODO_ALLOW_WRITE=true)
• Search records with full Elasticsearch query syntax, pagination, and filtering
• Browse and filter Zenodo communities
• Retrieve record metadata, files, and file content (text or binary)
• List, create, update, publish, and version depositions (write tools require ZENODO_ALLOW_WRITE=true)
• Configurable Zenodo base URL for sandbox or self-hosted instances
• Optional default community filter via ZENODO_COMMUNITY

• Node.js 18 or later
• npm

git clone https://github.com/eic/zenodo-mcp-server.git
cd zenodo-mcp-server
npm install
npm run build

# Without authentication (public records only)
node build/src/index.js

# With a persistent API key (service account)
ZENODO_API_KEY=your_token node build/src/index.js

# Against the Zenodo sandbox
ZENODO_BASE_URL=https://sandbox.zenodo.org ZENODO_API_KEY=your_sandbox_token node build/src/index.js

Zenodo uses personal access tokens for authentication.

After connecting to the server, call the set_api_key tool:

{ "name": "set_api_key", "arguments": { "api_key": "your_personal_access_token" } }

The token is stored in memory for the lifetime of the server process and is never written to disk.