Skip to main content
Glama
MSKazemi

mcp-zenodo

by MSKazemi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ZENODO_API_TOKENYesYour Zenodo API token for authentication

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_recordsB
Search for records in Zenodo.

Args:
    query: Search query
    max_results: Maximum number of results to return
    sort: Sort order (bestmatch, mostrecent)
    
Returns:
    Dictionary containing search results
get_citationA

Get a citation for a Zenodo record in the specified format.

Args:
    record_id: The ID of the Zenodo record
    format: The citation format (bibtex, apa, etc.)
    
Returns:
    CitationResponse containing the citation
detect_data_typeA

Determine if a Zenodo record is a dataset, software, or article.

Args:
    record_id: The ID of the Zenodo record to analyze
    
Returns:
    Dictionary containing the detected data type and confidence score
get_metadataB

Retrieve detailed metadata for a Zenodo record.

Args:
    record_id: The ID of the Zenodo record
    include_files: Whether to include file information
    include_versions: Whether to include version information
    
Returns:
    MetadataResponse containing the record metadata
list_filesA

List all files available in a Zenodo record.

Args:
    record_id: The ID of the Zenodo record
    include_metadata: Whether to include file metadata
    
Returns:
    Dictionary containing the list of files and their metadata

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct aspect: search_records for querying, get_citation for citations, detect_data_type for classification, get_metadata for detailed metadata, and list_files for files. There is no meaningful overlap between their purposes.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (search_records, get_citation, detect_data_type, get_metadata, list_files). The verbs clearly indicate the action, and the nouns indicate the resource aspect.

Tool Count5/5

Five tools is well-scoped for a server focused on searching and retrieving Zenodo records. Each tool earns its place, and the count is within the ideal 3-15 range without feeling thin or bloated.

Completeness4/5

The tool set covers the core read-only workflow: search, retrieve metadata, list files, get citations, and detect data types. Minor gaps exist (e.g., no direct record download, no deposit/update functionality), but for a read-oriented server the surface is largely complete.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources