Compatible with every major AI agent and IDE
What is the Zenodo MCP Server?
Connect your Zenodo account to any AI agent to streamline your scientific research workflows and data management through natural conversation.
What you can do
- Deposition Management — Create new unpublished depositions, update metadata, and manage your research drafts directly from the AI.
- Record Discovery — Search and list public records across the entire Zenodo database to find relevant research, software, or datasets.
- File Inspection — List all files attached to specific depositions to understand the contents of a research package.
- Metadata Control — Precisely update titles, creators, descriptions, licenses, and access rights for your unpublished work.
- Version Tracking — Retrieve specific deposition details using unique IDs to monitor the status of your submissions.
How it works
- Subscribe to this server
- Enter your Zenodo Personal Access Token
- Start managing your research data from Claude, Cursor, or any MCP-compatible client
No more manual navigation through complex forms to update a dataset description or find a specific research record. Your AI acts as a dedicated research assistant.
Who is this for?
- Researchers & Academics — quickly draft depositions and manage metadata for publications without leaving your writing environment.
- Data Scientists — automate the listing and retrieval of datasets for analysis directly from your code editor.
- Open Science Advocates — easily search and discover public research artifacts to foster collaboration and transparency.
Built-in capabilities (14)
You can optionally provide metadata. Create a new Zenodo deposition
Note: Only unpublished depositions can be deleted. Delete an unpublished Zenodo deposition
Delete a file from a Zenodo deposition
Discard edits on a Zenodo deposition
Edit a published Zenodo deposition
Retrieve a Zenodo deposition by ID
Retrieve a published Zenodo record by ID
List files in a Zenodo deposition
List Zenodo depositions
Search published Zenodo records
Create a new version of a Zenodo deposition
WARNING: Once published, a deposition cannot be deleted. Publish a Zenodo deposition
Update a Zenodo deposition
Upload a text file to a Zenodo deposition
Why Cursor?
Cursor's Agent mode turns Zenodo into an in-editor superpower. Ask Cursor to generate code using live data from Zenodo and it fetches, processes, and writes. all in a single agentic loop. 14 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Zenodo in Cursor
Zenodo and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Zenodo to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Zenodo in Cursor
The Zenodo MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 14 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Zenodo for Cursor
Every tool call from Cursor to the Zenodo MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I delete a deposition that has already been published?
No. The delete_deposition tool only works for unpublished depositions. Once a record is published on Zenodo, it is permanent to ensure scientific traceability.
How can I search for public datasets about a specific topic?
You can use the list_records tool with a search query. For example, ask the agent to 'Search Zenodo records for climate change' and it will return matching public entries.
Is it possible to see which files are included in a deposition before downloading them?
Yes! Use the list_deposition_files tool with the Deposition ID. The agent will provide a list of all filenames and metadata associated with that specific deposition.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Evolio
14 toolsTransform your coaching practice with client tracking, session management, and progress analytics that help people grow.

Slack Webhook Notifier
1 toolsThis MCP does exactly one thing: it sends messages to your Slack channels. That's its only function, and nothing else. Zero bloat, incredible for giving your AI agents a voice.

ChartMogul
8 toolsAnalyze subscription revenue and SaaS metrics via ChartMogul — track MRR, churn, and customer growth directly from any AI agent.

Bounsel
9 toolsManage your contract lifecycle via Bounsel — list documents, automate templates, and request signatures directly from any AI agent.
