About crossref-mcp-server
crossref-mcp-server serves scholarly research and literature workflows through the Crossref REST API. It resolves DOIs, searches scholarly works, and retrieves references and records for journals, funders, and publishers over stdio or Streamable HTTP.
Key features
- 01Resolve DOIs to scholarly work metadata
- 02Search works with text or structured filters
- 03Retrieve a work's outgoing references
- 04Find journals by ISSN or title
- 05Search funders and their funded works
- 06Look up publishers and DOI prefixes
Use cases
- 01Retrieve authors, abstracts, and publication details
- 02Search scholarly works by topic, author, or filters
- 03Inspect the references cited by a paper
- 04Verify journal, funder, or publisher records
MCP support
It exposes seven Crossref scholarly metadata tools to MCP clients over stdio or Streamable HTTP, and provides a public hosted instance.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://crossref.caseyjhand.com/mcpclaude mcp add --transport http cyanheads-crossref https://crossref.caseyjhand.com/mcp{"mcpServers":{"cyanheads-crossref":{"type":"http","url":"https://crossref.caseyjhand.com/mcp"}}}Open in Cursor{"servers":{"cyanheads-crossref":{"type":"http","url":"https://crossref.caseyjhand.com/mcp"}}}Open in VS Code{"mcpServers":{"cyanheads-crossref":{"type":"http","url":"https://crossref.caseyjhand.com/mcp"}}}{"mcpServers":{"cyanheads-crossref":{"serverUrl":"https://crossref.caseyjhand.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
7| Parameter | Type | Required | Description |
|---|---|---|---|
| doi | string | Yes | DOI in the format "10.NNNN/suffix", e.g. "10.1038/nature12373". A resolver-wrapped form — "https://doi.org/10.1038/nature12373", "https://dx.doi.org/…", "doi:10.1038/nature12373" — is accepted and unwrapped. |
| limit | integer | No | Maximum number of authors to return in one page (1–500, default 25). Ordinary records fit in a single page; large-collaboration papers in particle physics and genomics deposit thousands. |
| offset | integer | No | Zero-based index of the first author to return. Pass the nextOffset value from the previous response to continue through a long author list. Only the author list is paged; every other field of the record is returned in full on every page. |
Details
From the project README@cyanheads/crossref-mcp-server
Resolve DOIs, search ~188M scholarly works, fetch references, and look up publishers via the Crossref REST API. STDIO or Streamable HTTP.
Public Hosted Server: https://crossref.caseyjhand.com/mcp
Overview
Scholarly metadata from the Crossref REST API. Resolve DOIs to full metadata records, search across ~188 million scholarly works by free text or structured filters, fetch outgoing reference lists, and look up journals, funders, and publishers.
Tools
| Tool | Description |
|---|---|
crossref_get_work | Resolve a DOI to its full Crossref metadata record: title, authors, editors, affiliations, abstract, journal with volume/issue/pages, ISSNs and ISBNs, publication date, license, full-text links, funder acknowledgements, post-publication updates, and related identifiers |
crossref_search_works | Search the Crossref works index by free text and/or structured filters, with field-scoped query parameters, sort, field selection, and offset or cursor-based paging |
crossref_get_references | Return the outgoing reference list for a DOI — the works cited by this paper, with citation strings and resolved DOIs where available |
crossref_search_journals | Find Crossref journal records by ISSN or title query; optionally retrieve a page of the journal's most recent works |
crossref_search_funders | Find funders in the Crossref Funder Registry by name, registry ID, or funder DOI; optionally retrieve a page of funded works |
crossref_get_member | Resolve a Crossref member ID to its publisher record — name, owned DOI prefixes, DOI counts, and per-category metadata deposit coverage |
crossref_get_prefix | Resolve a DOI prefix (e.g. 10.1038) to its owning publisher, chaining into crossref_get_member |
Capability reference
crossref_get_work tool
- DOI validated against the
10.NNNN/suffixregex before the upstream call, accepted either bare or wrapped in its resolver (https://doi.org/…,https://dx.doi.org/…,doi:…) and unwrapped before the lookup - Returns title, authors with affiliations, abstract (when deposited), container/journal, publication date, work type, ISSN, license URLs, full-text link URLs, and funder acknowledgements
- Citation locators
volume,issue,page, andarticleNumberunder the same names and on the same rendered line ascrossref_search_works, plusisbn— each as deposited, omitted when absent editorsin the author entry shape, returned whole and never counted inauthorCount- Author list paged by
offset/limit(default 25, up to 500 per call — a largerlimitis clamped to 500 with anotice);authorCountreports the full deposited total and anextOffsetcontinues when authors remain — every other field is returned in full on every page updatedBylists the corrections, retractions, expressions of concern, and new versions Crossref records against the work — notice DOI, type, source (publisherorretraction-watch, with its record ID), and date, entry for entry — andupdateTothe works this record is a notice for; whenupdatedByis present,noticenames each update type with its sources. An absentupdatedBydoes not mean the work was never updatedrelationsgroups related identifiers (preprint ↔ published version, versions, reviews, supplements) by relation type, identifier type, and asserting party, returned whole; only Crossref-registered DOIs among them resolve through this tool- A funder or affiliation asserted only through the ROR registry (no name deposited) carries
rorin place ofname, never as a blank entry - Publication date is the first of
published,published-print,published-online, andissued(this tool only) that names a value; a date component Crossref records as unknown is omitted, along with everything less precise below it - Outgoing references are reported as a count (
referencesCount) — entries come fromcrossref_get_references; incoming citation count (isReferencedByCount) is included, but citing works are not exposed by Crossref — use OpenAlex for citation graphs - A DOI Crossref holds no record for returns
doi_not_foundnaming the agency the DOI registry says holds it (registrationAgency— DataCite, JaLC, mEDRA, …), a Funder Registry pointer when Crossref registered it, or that no agency registered it at all
crossref_search_works tool
- Free-text
queryplus a structuredfilterobject using Crossref's hyphenated keys (from-pub-date,type,funder,issn,has-abstract,license.url, etc.) - Field-scoped parameters
queryTitle,queryAuthor,queryContainerTitle, andqueryBibliographiccombine withqueryand with each other - Sort by
relevance,score,is-referenced-by-count,published,deposited, or other listed fields — the publication-date sorts page byoffsetonly, since Crossref refuses them with a cursor. A cursor walk with a query term and nosortruns by relevance (sent assort=score, withoutorder) and can repeat or skip a record at a page boundary;sort: "created"walks without repeats. A filter-only walk runs in Crossref registration order fieldsnarrows the payload to any of the 19 select names the summary projects — including the citation locatorsvolume,issue,page,article-number, andISSN, and the update linksupdated-byandupdate-to— and refuses any other name;DOIis always returned, andcrossref_get_workcarries the rest of the record- Each work carries
updatedBy(corrections, retractions, expressions of concern, new versions recorded against it) andupdateTo(the works it is a notice for) in the entry shape and rendered linecrossref_get_workuses, so a page of results can be screened for retractions without a call per DOI - A blank or whitespace-only query term or filter value, and an empty
sortororder, is read as omitted; when that leaves nothing to search by, thenoticesays the page is an unfiltered listing rowsreturns up to 100 works per call andauthorLimitcaps authors per work (default 25, up to 500); a larger value of either is clamped to its cap with anotice, which on an offset page also names the offset that continues after the records returned (and, near the ~10K ceiling, the smallerrowsthat still fits beside it);authorCountreports the full deposited total — chain a cut work's DOI intocrossref_get_workfor the rest- Offset paging is capped at
offset + rows ≤ 10,000; a rejected offset below the cap names therowsthat still fit, andcursor="*"starts deep paging via chainednextCursortokens — cursor and offset cannot be combined - A cursor walk ends on the page that omits
nextCursor— an empty page never carries one; every empty page'snoticenames which of the three causes applies
crossref_get_references tool
- Takes the citing work's DOI bare or resolver-wrapped, the same forms
crossref_get_workaccepts - Each reference carries its deposited citation string and, when Crossref has resolved it, a DOI for
crossref_get_work, withdoiAssertedBysaying whether the publisher deposited that DOI or Crossref matched it - Structured parts as deposited: author, year, article title, journal title, the title of a cited book or volume (
volumeTitle, which stands in as the title when there is no article title), series title, volume, issue, first page, edition, and ISSN - Citation strings have formatting markup stripped and character references decoded; a bracketed span that isn't a recognized tag (a cited URL, a Miller index, a DOI fragment) is left exactly as deposited
- Paged by
offset/limit(default 100, up to 500 per call — a largerlimitis clamped to 500 with anotice);referenceCountis the full deposited total andnextOffsetcontinues when more remain - Coverage varies by publisher — pre-2000 works and non-participating publishers often have no indexed references
- Single-hop only; incoming citations are not available through Crossref — use OpenAlex for citation graphs
- A DOI Crossref holds no record for returns
doi_not_foundnaming its registration agency (registrationAgency), or saying no agency registered it, the same waycrossref_get_workdoes
crossref_search_journals tool
include_works: truealso returns a page of the journal's most recent works — newest published first byworks_offset, newest registered first on aworks_cursorwalk; requires an unambiguous journal — a title query matching more than one returnsambiguous_journal, naming candidates and ISSNs- Returns journal title, publisher, ISSNs with their print/electronic form, subject areas, DOI counts (total/current/backfile), and per-category metadata deposit coverage (abstracts, references, ORCIDs, funders, licenses, and more) as current/backfile fractions — the same breakdown
crossref_get_membergives per publisher - An
issnlookup also returns DOI counts by issued year, ascending; title-query results omit them - Title-query results page by
offset(ceilingoffset + rows ≤ 100,000); the works list pages separately byworks_offset(ceiling≤ 10,000) — an offset past the end of either list carries anoticenaming it, and so does a page that stalls at either ceiling, along with the offset and smallerrowsthat reach the last records below it works_cursor="*"pages the works list with no ceiling via chainednextWorksCursortokens; a cursor walk runs by Crossref registration date, newest first (Crossref does not walk a publication-date sort by cursor), and cannot combine withworks_offset > 0(works_cursor_offset_conflict)- A matched journal with no ISSN registered has no addressable works list —
include_worksis skipped with anoticerather than returning an empty list
crossref_search_funders tool
- Accepts a name
query, a bare registry ID (100000001), or a full funder DOI (10.13039/100000001, optionally behind adoi:/https://doi.org/prefix) include_works: truealso returns a page of funded works; requires an unambiguous funder — a name query matching more than one returnsambiguous_funder, naming candidates and registry IDs- Returns funder name, registry ID, country, and alternate names
- Name-query results page by
offset(ceiling≤ 100,000); the funded-works list pages separately byworks_offset(ceiling≤ 10,000) or, with no ceiling,works_cursor="*"chainingnextWorksCursor— offset pages run newest published first, a cursor walk newest registered first, and the two cannot combine (works_offset > 0); an offset past the end of either list carries anoticenaming it, and a page that stalls at either ceiling names the offset and smallerrowsthat reach the last records below it - The funded-works list also counts works funded by the funder's registry descendants, which a
crossref_search_worksfilter on{"funder": "10.13039/<id>"}does not - A deprecated registry entry answers to its successor's name while counting only its own works — the response's
noticenames the superseding ID viareplacedBy; the replacement is never followed automatically
crossref_get_member tool
- Members are the organizations that register DOIs — this answers "what does this publisher publish, and how completely do they deposit metadata?"
- Returns primary name, alternate imprint names, owned DOI prefixes, DOI counts (total/current/backfile), a per-work-type breakdown, and per-category metadata deposit coverage (references, abstracts, ORCIDs, funders, licenses, and more) as current/backfile fractions
- Pair with
crossref_get_prefixto resolve a DOI prefix to the member ID first
crossref_get_prefix tool
- Accepts the registrant prefix of a DOI (e.g.
10.1038, no/suffix) - Returns the publisher name and numeric member ID — the ID chains directly into
crossref_get_memberfor the full record - The Crossref prefix record is thin by design (owner name and member link only); richer publisher data lives on the member record
- A prefix with no Crossref member returns
prefix_not_foundnaming the agency that registered it (registrationAgency, e.g. DataCite for10.5281), or saying no agency registered it
Features
Built on @cyanheads/mcp-ts-core: stdio and Streamable HTTP transports, pluggable auth (none / jwt / oauth), swappable storage (in-memory, filesystem, Supabase, Cloudflare KV/R2/D1), structured logging with optional OpenTelemetry tracing.
Crossref-specific:
- Polite-pool
User-Agentheader injected on every Crossref request — priority access viaCROSSREF_MAILTO, keyless otherwise; no API token required - Retry with exponential backoff on 429 (honoring
Retry-After), 5xx, HTTP 408/504, and network failures; a malformed response body and a request that hitsCROSSREF_TIMEOUT_MSare not retried - Cursor-based deep paging on the works search and on both works sub-resources, for result sets beyond the offset cap
- Crossref's rejections of a request come back as declared reasons —
unknown_filter(with the hyphenated key when Crossref lists one),invalid_parameter,sort_cursor_conflict,invalid_cursor— carrying the rejected inputs and a recovery hint; a malformedissnfilter value is refused before the request, and no upstream error relays Crossref's raw response body - Text normalization on every human-readable value: HTML character references decoded and whitespace collapsed; citation strings additionally have formatting markup stripped, so titles and abstracts read as plain text instead of raw JATS XML; a MathML formula keeps its structure — the TeX annotation where the deposit carries one, otherwise a linear form such as
x_i,A^{−1},√(m),(a+b)/c
Agent-friendly output:
- Provenance — identifiers, URLs, and dates are returned byte-exact while human-readable text is normalized, so a caller can trust
doi,issn, and date fields without re-verification - Graceful partial failure — an empty page is a success, not an error: an offset past the end of a list, or a query nothing matched, carries a
noticesaying which, and so does the page that ends acrossref_search_workscursor walk; a journal or funder works walk ends on the page that omitsnextWorksCursor - Discriminated output contracts — the
nextCursor,nextOffset,nextWorksOffset, andnextWorksCursorcontinuation fields are withheld once a list is exhausted, and a page that stops at an offset ceiling says so in itsnotice; a cursor token can still ride the last partial page, and the empty page after it carries none - Ambiguity handled explicitly —
ambiguous_journalandambiguous_funderlist every candidate and its identifier in the error data rather than silently resolving to the first match
Getting started
Public Hosted Instance
A public instance is available at https://crossref.caseyjhand.com/mcp — no installation required. Point any MCP client at it via Streamable HTTP:
{
"mcpServers": {
"crossref-mcp-server": {
"type": "streamable-http",
"url": "https://crossref.caseyjhand.com/mcp"
}
}
}
Self-Hosted / Local
Add the following to your MCP client configuration file. CROSSREF_MAILTO is optional but recommended — without it the server uses Crossref's anonymous pool with stricter rate limits.
{
"mcpServers": {
"crossref-mcp-server": {
"type": "stdio",
"command": "bunx",
"args": ["@cyanheads/crossref-mcp-server@latest"],
"env": {
"MCP_TRANSPORT_TYPE": "stdio",
"MCP_LOG_LEVEL": "info",
"CROSSREF_MAILTO": "[email protected]"
}
}
}
}
Or with npx (no Bun required):
{
"mcpServers": {
"crossref-mcp-server": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@cyanheads/crossref-mcp-server@latest"],
"env": {
"MCP_TRANSPORT_TYPE": "stdio",
"MCP_LOG_LEVEL": "info",
"CROSSREF_MAILTO": "[email protected]"
}
}
}
}
Or with Docker:
{
"mcpServers": {
"crossref-mcp-server": {
"type": "stdio",
"command": "docker",
"args": [
"run", "-i", "--rm",
"-e", "MCP_TRANSPORT_TYPE=stdio",
"-e", "[email protected]",
"ghcr.io/cyanheads/crossref-mcp-server:latest"
]
}
}
}
For Streamable HTTP, set the transport and start the server:
MCP_TRANSPORT_TYPE=http MCP_HTTP_PORT=3010 [email protected] bun run start:http
# Server listens at http://localhost:3010/mcp
Prerequisites
- Bun v1.4.0 or higher (or Node.js v24+).
- An email address for
CROSSREF_MAILTOis optional but recommended — Crossref's polite pool grants priority access to clients that identify themselves. No account or token is required.
Installation
- Clone the repository:
git clone https://github.com/cyanheads/crossref-mcp-server.git
- Navigate into the directory:
cd crossref-mcp-server
- Install dependencies:
bun install
- Configure environment:
cp .env.example .env
# edit .env and optionally set CROSSREF_MAILTO for polite-pool access
Configuration
All configuration is validated at startup via Zod schemas in src/config/server-config.ts.
| Variable | Description | Default |
|---|---|---|
CROSSREF_MAILTO | Email address embedded in the polite-pool User-Agent header of every Crossref request. Optional — server starts without it but logs a warning and uses the anonymous pool with stricter rate limits. Never sent to the DOI registry: the agency lookup after a Crossref not-found identifies the server and version only. | — |
CROSSREF_BASE_URL | Crossref API base URL. Override for testing against a local proxy. The agency lookup after a Crossref not-found always goes to https://doi.org, whatever this is set to. | https://api.crossref.org |
CROSSREF_TIMEOUT_MS | Per-request timeout in milliseconds. Also the worst-case wait against an unresponsive upstream — a request that hits the deadline is not retried. | 10000 |
MCP_TRANSPORT_TYPE | Transport: stdio or http. | stdio |
MCP_SESSION_MODE | HTTP session mode: auto, stateful, or stateless. This server needs no multi-round input, so src/index.ts declares stateless; Docker and .env.example pin the same value, and setting this variable overrides the declaration. | stateless (declared in src/) |
MCP_HTTP_PORT | Port for the HTTP server. | 3010 |
MCP_AUTH_MODE | Auth mode: none, jwt, or oauth. | none |
MCP_LOG_LEVEL | Log level (RFC 5424). | info |
LOGS_DIR | Directory for log files (Node.js only). | <project-root>/logs |
LOG_TOOL_FAILURE_PAYLOADS | Log each failed tool call's arguments and result, redacted by key name and capped at LOG_TOOL_FAILURE_PAYLOAD_MAX_BYTES (default 16384). A secret inside a free-form value is not redacted. | false |
OTEL_ENABLED | Enable OpenTelemetry instrumentation. | false |
See .env.example for the full list of optional overrides.
Running the server
Local development
-
Build and run:
# One-time build bun run rebuild # Run the built server bun run start:stdio # or bun run start:http -
Run checks and tests:
bun run devcheck # Lint, format, typecheck, security bun run test # Vitest test suite bun run lint:mcp # Validate MCP definitions against spec
Project structure
| Directory | Purpose |
|---|---|
src/index.ts | createApp() entry point — registers tools and inits services. |
src/config | Server-specific environment variable parsing and validation with Zod. |
src/mcp-server/tools | Tool definitions (*.tool.ts). |
src/services/crossref | CrossrefService — HTTP client, polite-pool header, retry, pagination helpers. |
tests/ | Unit and integration tests mirroring src/. |
Development guide
See CLAUDE.md for development guidelines and architectural rules. The short version:
- Handlers throw, framework catches — no
try/catchin tool logic - Use
ctx.logfor request-scoped logging,ctx.statefor tenant-scoped storage - Register new tools via the barrel in
src/mcp-server/tools/definitions/index.ts - Wrap external API calls: validate raw → normalize to domain type → return output schema; never fabricate missing fields (abstracts, reference lists, and affiliations are frequently absent in Crossref records)
Contributing
Issues are welcome. Run checks and tests before submitting:
bun run devcheck
bun run test
License
Apache-2.0 — see LICENSE for details.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.