crossref-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CROSSREF_MAILTO | No | Email address to use for Crossref polite pool (recommended but optional) |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_work_by_doiA | Retrieve bibliographic metadata for a single work by its DOI. Args: doi: The Digital Object Identifier, e.g. "10.1145/3292500.3330701". A full URL such as "https://doi.org/10.1145/..." is also accepted. Returns: A dictionary of the work's metadata (title, authors, journal, year, DOI, abstract when available, citation counts, etc.). |
| search_worksA | Search Crossref for works by free text, title, and/or author. At least one of Args: query: Free-text bibliographic search across all fields. title: Restrict the search to the work's title. author: Restrict the search to author names. rows: Number of results to return (1-50, default 5). Returns:
A dictionary with |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are clearly distinct: one retrieves a specific work by DOI, the other searches for works using query parameters. There is no overlap in their purposes, making it easy for an agent to select the appropriate tool.
Both tools follow a consistent verb_noun pattern: 'get_work_by_doi' and 'search_works'. The naming clearly indicates the action and the resource, and there is no mixing of conventions.
With only two tools, the server feels thin for a general Crossref API, but for the narrow purpose of retrieving works by identifier or search, it is minimally sufficient. The count is at the low end of what is reasonable.
The core workflows of looking up a work by DOI and searching for works are covered. Minor gaps exist, such as no support for other identifiers or listing all works of an author directly, but the primary use cases are addressed.