Zenodo MCP

MCPAI代理

提供方 MSKazemi

AI代理 未标注 OAuth 授权 社区 / 第三方 ClaudeCursorCodexZed
查看接入方式

Tool-based LLM integration with Zenodo via the Model Context Protocol (MCP)

一句话选型结论

按资料字段整理

Zenodo MCP 属于AI代理类 MCP 服务器,传输方式未标注,OAuth 授权,可直接接入 Claude、Cursor、Codex 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式未标注 鉴权OAuth 授权 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

api mcp openai fastapi llm langchain llm tools langgraph

支持客户端

适用场景

apimcpopenai

安装与配置

未标注 OAuth 授权
上游未给出传输方式
pip install -r requirements.txt

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、Codex,换客户端不用重新研究配置。

先想清楚的地方

  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Zenodo MCP当前 未标注 未标注 未标注 有 未标注
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方MSKazemi上游标注的维护方 MSKazemi
分类AI代理本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · python本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

10.5 KB
来自项目仓库与上游目录的原文,未做删改

mcp-zenodo — Zenodo MCP Server

mcp-zenodo is a Zenodo MCP server: it connects large language models to Zenodo, the CERN-hosted open-access research repository, through the Model Context Protocol (MCP). It lets an LLM search Zenodo records, read metadata, retrieve citations, and list or download files as callable tools. It is built for developers and researchers who want AI assistants to work with open research datasets, software, and publications. Use it when you want tools like Claude Desktop, Cursor IDE, or a LangChain/LangGraph agent to ground answers in real Zenodo records with DOIs. Do not use it if you need to deposit or publish to Zenodo, since this project is read/retrieval oriented and does not implement upload workflows. Compared with calling the Zenodo REST API directly, mcp-zenodo packages that access as MCP tools so any MCP-compatible client can use Zenodo without writing custom integration code.

> One-line value prop: an MCP server for Zenodo that turns open-access research data into LLM-callable tools.

Written in Python. Licensed under Apache-2.0.


What it does

mcp-zenodo exposes Zenodo's repository of research outputs to LLMs through MCP tools:

  • Search and retrieve records — find Zenodo records by query.
  • Get citations — retrieve citations in formats such as BibTeX and APA.
  • Detect data types — classify a record as dataset, software, or article.
  • Access metadata — get detailed metadata for a record.
  • List and download files — browse and download files attached to records.

Available tools

Tool Description
search_records Search for records in Zenodo
get_metadata Retrieve detailed metadata of a Zenodo record
get_citation Return a BibTeX or APA citation of a Zenodo record
detect_data_type Determine if a record is a dataset, software, or article
compare_records Compare metadata of multiple Zenodo records
list_files List available files in a Zenodo record
download_file Download a specific file from a record
generate_embed_link Create a direct embeddable link for a record (PDF, dataset)
extract_keywords Extract top keywords from a record's abstract or text
get_related_records Find records related to a given Zenodo record
summarize_record Generate a summary from a record's metadata

Repository structure

This repository contains two implementations for two different use cases:

  1. MCP SDK Core (/mcp_sdk_core) — a Python MCP server for integration with MCP-enabled environments such as Cursor IDE and Claude Desktop.
  2. MCP API (/mcp_api) — a FastAPI service that exposes MCP-compatible tools for LLM frameworks such as LangChain and LangGraph, and OpenAI-compatible clients.

MCP SDK Core

The MCP SDK Core implementation is designed for direct integration with MCP-enabled environments. It provides:

  • Direct MCP integration — follows the Model Context Protocol standard.
  • Cursor IDE / Claude Desktop compatibility — connects through the standard MCP client config.
  • Simple configuration — managed through a JSON config file.
  • Unified API — standardized access to Zenodo resources.

This is ideal for developers who want to access Zenodo directly from their development environment without additional middleware.

Learn more about the MCP SDK Core implementation →

MCP API

The MCP API implementation is a FastAPI service that provides MCP-compatible tools for LLM frameworks. It offers:

  • LangChain integration — use the tools with LangChain agents.
  • LangGraph compatibility — use the tools in LangGraph workflows.
  • OpenAI-compatible API — usable with OpenAI-compatible clients.
  • LibreChat support — compatible with LibreChat and similar platforms.
  • Custom tool creation — extensible architecture for adding tools.

This is ideal for developers building LLM applications that interact with Zenodo as part of a larger workflow.

Learn more about the MCP API implementation →


30-second quickstart

Option A — MCP server for Cursor IDE / Claude Desktop```bash

Clone the repository

git clone https://github.com/MSKazemi/mcp-zenodo.git
cd mcp-zenodo/mcp_sdk_core

Install dependencies

pip install -r requirements.txt


Then register the server with your MCP client. For Cursor IDE, create an `mcp.json` (in your project root or `~/.cursor/`); for Claude Desktop, add the same block to `claude_desktop_config.json`:```json
{
  "mcpServers": {
    "Zenodo": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/mcp-zenodo/mcp_sdk_core/server",
        "run",
        "server.py"
      ]
    }
  }
}

Adjust the --directory path to your local checkout. Restart the client; it will detect and start the Zenodo MCP server. You can then ask the assistant to search Zenodo, fetch metadata, or retrieve a citation.

Option B — FastAPI service for LangChain / LangGraph / OpenAI-compatible clients```bash

Clone the repository

git clone https://github.com/MSKazemi/mcp-zenodo.git
cd mcp-zenodo/mcp_api

Install dependencies

pip install -r requirements.txt

Set up environment variables

cp .env.example .env

Edit .env with your Zenodo API token

Run the API server

uvicorn server.main:app --host 0.0.0.0 --port 8000


---

## Example

Ask an MCP-enabled assistant (Claude Desktop, Cursor) a question that triggers the `search_records` tool:

> "Search Zenodo for records about climate model output and show me the top result with its DOI."

The assistant calls the `search_records` tool, then `get_metadata`, and returns a record's title, authors, DOI, and description. A representative (abbreviated) tool result looks like:```json
{
  "hits": [
    {
      "title": "Example Climate Model Output Dataset",
      "doi": "10.5281/zenodo.1234567",
      "type": "dataset",
      "url": "https://zenodo.org/record/1234567"
    }
  ]
}

You can then follow up with get_citation to obtain a BibTeX or APA citation, or list_files / download_file to access the record's files. (Exact fields and values depend on the live Zenodo record returned.)


Use cases

  • Literature and dataset discovery — let an AI assistant search Zenodo and surface relevant datasets, software, and papers with DOIs.
  • Citation retrieval — pull BibTeX or APA citations for records directly into a manuscript or notebook.
  • Research agents — give LangChain/LangGraph agents a Zenodo tool so they can ground answers in open research data.
  • In-editor research — query Zenodo from Cursor IDE or Claude Desktop while writing code or documentation.
  • Reproducibility workflows — locate, inspect metadata for, and download research artifacts programmatically.

Comparison and alternatives

  • vs. calling the Zenodo REST API directly — the Zenodo REST API gives full control (including deposition/upload), but you must write and maintain the integration yourself. mcp-zenodo wraps common read/retrieval operations as MCP tools so any MCP client can use them with no custom code.
  • vs. general-purpose HTTP/fetch MCP servers — a generic fetch tool can hit Zenodo URLs but has no knowledge of records, metadata, citations, or file listings. mcp-zenodo provides Zenodo-specific, typed tools.
  • vs. other research-repository MCP servers — comparable MCP servers exist for sources such as arXiv and other data repositories; mcp-zenodo is focused specifically on Zenodo. It ships two integration paths (a stdio MCP server and a FastAPI service), which lets you choose between direct MCP clients and LLM-framework/OpenAI-compatible usage.

Limitations / when NOT to use

  • Not for depositing or publishing — this project focuses on searching and retrieving from Zenodo; it does not implement Zenodo deposition/upload workflows.
  • Depends on the Zenodo API — availability, rate limits, and returned fields are governed by Zenodo; some operations may require a Zenodo API token.
  • Retrieval quality depends on Zenodo metadata — data-type detection, keyword extraction, and summaries are derived from record metadata and are best-effort.
  • Two separate implementations — the MCP SDK Core server and the FastAPI service are configured differently; pick the one matching your client rather than expecting a single unified deployment.

FAQ

What is mcp-zenodo?
mcp-zenodo is a Zenodo MCP server — an implementation of the Model Context Protocol that exposes Zenodo (the CERN open-access research repository) to large language models as callable tools for searching records, reading metadata, retrieving citations, and listing or downloading files.

How do I use Zenodo with Claude or ChatGPT via MCP?
For Claude Desktop or Cursor IDE, install the mcp_sdk_core server and add it to your MCP client config (claude_desktop_config.json or mcp.json) as shown in the quickstart. For OpenAI-compatible / ChatGPT-style workflows, run the mcp_api FastAPI service and call its MCP-compatible tools from your framework (e.g., LangChain, LangGraph) or OpenAI-compatible client.

Which MCP clients are supported?
Any MCP-compatible client can use the mcp_sdk_core server over the standard MCP transport; it is tested with Cursor IDE and works with Claude Desktop. The mcp_api service targets LLM frameworks such as LangChain and LangGraph, OpenAI-compatible clients, and platforms such as LibreChat.

Do I need a Zenodo API token?
The FastAPI service reads a Zenodo API token from .env (see .env.example). Some Zenodo operations work without a token, but a token is recommended for reliable access.

Is mcp-zenodo on PyPI?
Not at this time — install it by cloning the repository as shown in the quickstart.


Contributing

Contributions to both implementations are welcome. Please see the implementation READMEs (mcp_sdk_core, mcp_api) for details.


License

This project is licensed under the Apache License 2.0 — see the LICENSE file for details.


Citation

If you use mcp-zenodo in your work, please cite it. Citation metadata is provided in CITATION.cff. Example:

> Seyedkazemi Ardebili, M. mcp-zenodo: A Zenodo MCP server. https://github.com/MSKazemi/mcp-zenodo

Legal notice and responsible use

The materials in this repository are made available without warranties to the extent permitted by applicable law. Please read the Disclaimer and Responsible-Use Notice before relying on or deploying them. This notice does not change any existing software license or limit rights that cannot legally be waived.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Zenodo MCP 怎么安装?

在客户端按下面的安装命令接入:pip install -r requirements.txt。装完在客户端配置里引用同一个包或端点。

Zenodo MCP 怎么在 Claude、Cursor、Codex 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Zenodo MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Zenodo MCP 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Zenodo MCP 支持哪些客户端?

资料标注支持 Claude、Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Zenodo MCP 能提供哪些能力?

资料显示能力标签包括 api、mcp、openai、fastapi、llm、langchain。具体工具清单以官方文档为准。

Zenodo MCP 需要什么运行环境?

运行时为 python。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。