pubmed-mcp-server

v2.11.1

Search PubMed, fetch articles, generate citations, explore MeSH terms, and discover related research.

pubmed.caseyjhand.com/mcp
claude mcp add --transport http pubmed-mcp-server https://pubmed.caseyjhand.com/mcp
codex mcp add pubmed-mcp-server --url https://pubmed.caseyjhand.com/mcp
{
  "mcpServers": {
    "pubmed-mcp-server": {
      "url": "https://pubmed.caseyjhand.com/mcp"
    }
  }
}
gemini mcp add --transport http pubmed-mcp-server https://pubmed.caseyjhand.com/mcp
{
  "mcpServers": {
    "pubmed-mcp-server": {
      "command": "bunx",
      "args": [
        "mcp-remote",
        "https://pubmed.caseyjhand.com/mcp"
      ],
      "env": {
        "NCBI_API_KEY": "your-ncbi-api-key",
        "NCBI_ADMIN_EMAIL": "you@example.com",
        "UNPAYWALL_EMAIL": "you@example.com"
      }
    }
  }
}
{
  "mcpServers": {
    "pubmed-mcp-server": {
      "type": "http",
      "url": "https://pubmed.caseyjhand.com/mcp"
    }
  }
}
curl -X POST https://pubmed.caseyjhand.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"curl","version":"1.0.0"}}}'

Tools

12

pubmed_search_articles

open-world

Search PubMed with full query syntax, filters, and date ranges. Returns PMIDs and optional brief summaries. Supports field-specific filters (author, journal, MeSH terms), common filters (language, species, free full text), and pagination via offset for paging through large result sets.

read
invocation
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "pubmed_search_articles",
    "arguments": {
      "query": "<query>"
    }
  }
}
schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "description": "PubMed search query (supports full NCBI syntax), sent as written apart from inline formatting tags such as `<i>`, which are removed. Must carry a search term: a value that is blank once markup, bracketed field tags (`[pdat]`), parentheses, and invisible characters such as a zero-width space are disregarded is rejected rather than sent to PubMed."
    },
    "maxResults": {
      "default": 20,
      "description": "Maximum results to return. 0 returns only `totalCount`.",
      "type": "integer",
      "minimum": 0,
      "maximum": 1000
    },
    "offset": {
      "default": 0,
      "description": "Result offset for pagination (0-based). PubMed serves at most the first 9999 records of a result set, so this caps at 9998; narrow the query or add filters to reach anything beyond it.",
      "type": "integer",
      "minimum": 0,
      "maximum": 9998
    },
    "sort": {
      "default": "relevance",
      "description": "Sort order: relevance (default), pub_date (newest first), author, or journal",
      "type": "string",
      "enum": [
        "relevance",
        "pub_date",
        "author",
        "journal"
      ]
    },
    "dateRange": {
      "description": "Filter by date range. The filter is applied only when both `minDate` and `maxDate` are non-empty; either one empty disables the entire date range. A partial date covers its whole year or month, and a range whose `minDate` falls after its `maxDate` is rejected: `2024/06` to `2024` is valid, `2024/07` to `2024/06/30` is not.",
      "type": "object",
      "properties": {
        "minDate": {
          "type": "string",
          "pattern": "^$|^\\d{4}([/\\-.]\\d{1,2}([/\\-.]\\d{1,2})?)?$",
          "description": "Start date (YYYY/MM/DD, YYYY/MM, or YYYY). Must be a real calendar date — `2023/02/29` is rejected. Leaving it empty drops the whole date range, not just this bound; for no lower bound pass a wide sentinel such as `1000`."
        },
        "maxDate": {
          "type": "string",
          "pattern": "^$|^\\d{4}([/\\-.]\\d{1,2}([/\\-.]\\d{1,2})?)?$",
          "description": "End date (YYYY/MM/DD, YYYY/MM, or YYYY). Must be a real calendar date — `2023/02/29` is rejected. Leaving it empty drops the whole date range, not just this bound; for no upper bound pass a wide sentinel such as `3000`."
        },
        "dateType": {
          "default": "pdat",
          "description": "Date type: pdat (publication), mdat (modification), edat (entrez)",
          "type": "string",
          "enum": [
            "pdat",
            "mdat",
            "edat"
          ]
        }
      },
      "required": [
        "minDate",
        "maxDate",
        "dateType"
      ],
      "additionalProperties": false
    },
    "publicationTypes": {
      "description": "Filter by publication type (e.g. \"Review\", \"Clinical Trial\", \"Meta-Analysis\"). Multiple values are OR'd — any match qualifies. Empty strings are skipped; an element of only whitespace, invisible characters, markup, parentheses, brackets, or double quotes is rejected.",
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "author": {
      "description": "Filter by author name (e.g. \"Smith J\"). An empty string applies no filter; a value of only whitespace, invisible characters, markup, parentheses, brackets, or double quotes is rejected.",
      "type": "string"
    },
    "journal": {
      "description": "Filter by journal name. An empty string applies no filter; a value of only whitespace, invisible characters, markup, parentheses, brackets, or double quotes is rejected.",
      "type": "string"
    },
    "meshTerms": {
      "description": "Filter by MeSH terms. Multiple terms are AND'd — all must match. Empty strings are skipped; an element of only whitespace, invisible characters, markup, parentheses, brackets, or double quotes is rejected.",
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "language": {
      "description": "Filter by language (e.g. \"english\"). An empty string applies no filter; a value of only whitespace, invisible characters, markup, parentheses, brackets, or double quotes is rejected.",
      "type": "string"
    },
    "hasAbstract": {
      "description": "Only include articles with abstracts",
      "type": "boolean"
    },
    "freeFullText": {
      "description": "Only include free full text articles",
      "type": "boolean"
    },
    "species": {
      "description": "Filter by species: `humans` adds `humans[MeSH Terms]`, `animals` adds `\"animals\"[mh:noexp]` (animals other than humans; a record indexed for both stays in). Both match only records with MEDLINE species indexing, which preprints and ahead-of-print citations lack.",
      "type": "string",
      "enum": [
        "humans",
        "animals"
      ]
    },
    "summaryCount": {
      "default": 0,
      "description": "Fetch brief summaries for top N results (0 = PMIDs only). Above the 50 cap, pass the remaining PMIDs to pubmed_fetch_articles.",
      "type": "integer",
      "minimum": 0,
      "maximum": 50
    }
  },
  "required": [
    "query",
    "maxResults",
    "offset",
    "sort",
    "summaryCount"
  ],
  "additionalProperties": false
}
view source ↗

pubmed_fetch_articles

open-world

Fetch full article metadata by PubMed IDs. Returns detailed article information including abstract, authors, journal, MeSH terms, linked retraction, erratum, and comment notices, and databank accessions such as trial registration IDs; grants and the members of a collective author are opt-in (`includeGrants`, `includeInvestigators`). Set `maxResponseCharacters` to bound the whole response: articles past the ceiling are deferred whole and listed in `deferred.ids` for a follow-up call.

read
invocation
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "pubmed_fetch_articles",
    "arguments": {
      "pmids": "<pmids>"
    }
  }
}
schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "pmids": {
      "minItems": 1,
      "maxItems": 200,
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^\\d+$"
      },
      "description": "PubMed IDs to fetch"
    },
    "includeMesh": {
      "default": true,
      "description": "Include MeSH terms",
      "type": "boolean"
    },
    "includeGrants": {
      "default": false,
      "description": "Include grant information",
      "type": "boolean"
    },
    "includeInvestigators": {
      "default": false,
      "description": "Include `investigators`: the members NCBI lists for a collective author such as \"TGU Investigators\". Off by default because the list is unbounded: consortium trials name thousands, at about 60 characters of JSON each — PMID 33933206 lists 6,349, adding about 372,000 characters to its record. Under `maxResponseCharacters` they count toward the size of their article, which is deferred whole when it no longer fits.",
      "type": "boolean"
    },
    "maxResponseCharacters": {
      "description": "Opt-in ceiling for the whole response, in characters. Each article is measured as the JSON record it is returned as — title, abstract, authors, journal, MeSH terms, grants, identifiers, every field it carries. Articles are kept in response order until the next one would cross the ceiling; that article and the rest are deferred whole (never partially populated) and listed in `deferred.ids`. Response envelope fields — counts, `unavailablePmids`, `deferred` itself — are not counted. Omit to return every resolved article.",
      "type": "integer",
      "minimum": 1,
      "maximum": 9007199254740991
    }
  },
  "required": [
    "pmids",
    "includeMesh",
    "includeGrants",
    "includeInvestigators"
  ],
  "additionalProperties": false
}
view source ↗

pubmed_fetch_fulltext

open-world

Fetch full-text articles from PubMed Central as structured sections — the body, then back matter such as acknowledgments, declarations, and appendices — with tables and references. When PMC misses, transparently falls back to Europe PMC `fullTextXML` (structured JATS for its open-access subset, preprints included), then to Unpaywall — publisher-hosted or institutional open-access copies as HTML-as-Markdown or PDF-as-text. Name articles by `pmcids` (PMC IDs directly), `pmids` (PubMed IDs, auto-resolved), `dois` (DOIs, auto-resolved to PMC via the ID Converter; preprints and EPMC-only OA fall through to the Europe PMC and Unpaywall layers), or any mix of the three — up to 50 distinct identifiers; the first 10 are fetched per call, the rest returned in `overLimit`; an article several of them name is fetched and returned once. Two independent character controls: `maxCharacters` caps body text per article, `maxResponseCharacters` caps the whole response and defers articles past the ceiling whole, listing them in `deferred.ids` for a follow-up call.

read
invocation
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "pubmed_fetch_fulltext",
    "arguments": {}
  }
}
schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "pmcids": {
      "description": "PMC IDs to fetch (e.g. [\"PMC9575052\"]). Combinable with `pmids` and `dois` — up to 50 distinct identifiers across the three; the first 10 are fetched per call, the rest returned in `overLimit`. PMC IDs with no retrievable full text fall through to Europe PMC, then to Unpaywall on the DOI the chain resolves for them.",
      "minItems": 1,
      "maxItems": 50,
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^(?:PMC)?\\d+$"
      }
    },
    "pmids": {
      "description": "PubMed IDs. Combinable with `pmcids` and `dois` — up to 50 distinct identifiers across the three; the first 10 are fetched per call, the rest returned in `overLimit`. Articles in PMC are returned as structured JATS; articles not in PMC fall through to Europe PMC (when EPMC has a `fullTextXML`), then to Unpaywall when `UNPAYWALL_EMAIL` is set and a DOI is available.",
      "minItems": 1,
      "maxItems": 50,
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^\\d+$"
      }
    },
    "dois": {
      "description": "DOIs to resolve (e.g. [\"10.21203/rs.3.rs-9010375/v1\"]), one per element. Combinable with `pmcids` and `pmids` — up to 50 distinct identifiers across the three; the first 10 are fetched per call, the rest returned in `overLimit`. Resolved to a PMCID via the PMC ID Converter and returned as structured JATS when the article is in PMC; DOIs with no PMC counterpart (preprints, EPMC-only OA) fall through to Europe PMC, then Unpaywall, when those layers are enabled.",
      "minItems": 1,
      "maxItems": 50,
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^10\\.[^\\s,]+\\/[^\\s,]+$"
      }
    },
    "includeReferences": {
      "default": false,
      "description": "Include reference list. Applies to `source=pmc` results only.",
      "type": "boolean"
    },
    "includeTables": {
      "default": true,
      "description": "Include the article's tables — cells, captions, labels and footnotes. On by default because a dropped table takes its numbers with it. Table-dense articles pay for it: rendered tables typically add 12–17% to an article record and can more than double it. Set false to omit them, or cap the cost with `maxCharacters`, which drops tables it cannot fit whole. Applies to `source=pmc` results only.",
      "type": "boolean"
    },
    "includeAssets": {
      "default": true,
      "description": "Include the article's figures and supplementary material — `assets[]`, each with its label, caption, enclosing section and deposit pointer. On by default because it is cheaper than tables: a median asset-bearing article grows about 10%, and the body prose already refers to these by label. Set false to omit them, which also removes the `[Figure: …]` / `[Supplementary: …]` markers from the section text, since without the array they point at nothing. Prose-shaped blocks — lists, definition lists, block quotes, boxed text, preformatted blocks, displayed formulae — are section text rather than assets and this switch never affects them. Applies to `source=pmc` results only.",
      "type": "boolean"
    },
    "maxSections": {
      "description": "Maximum top-level sections, counted after `sections`. Back-matter sections count and follow the body, so a cap drops them first. The sections it drops are named per article in `sectionCap`. Applies to `source=pmc` results only.",
      "type": "integer",
      "minimum": 1,
      "maximum": 9007199254740991
    },
    "sections": {
      "description": "Filter to specific sections by title (e.g. [\"Introduction\", \"Methods\", \"Results\", \"Discussion\"]). A term matches a section or subsection title at any nesting depth, case-insensitively, as a substring — \"resul\" matches \"Results\". Back-matter sections match the same way: by their own titles, or by their kind when they carry neither a title nor a label — \"appendix\" matches a section titled \"Appendix A\", \"footnotes\" an untitled footnote group. A label is never matched, so an appendix labelled \"Appendix A\" under a title of its own matches only on that title. A section whose own title matches is returned whole; one kept only because a nested subsection matched keeps its heading as a breadcrumb, with its own text cleared and only the matching branch beneath it. Tables and assets narrow with the filter: one whose section did not survive, or that names no section, is dropped. Empty strings are skipped, so `[\"\"]` applies no filter; an element of only whitespace or invisible characters, such as a zero-width space, is rejected. Applies to `source=pmc` results only.",
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "maxCharacters": {
      "description": "Per-article budget for body text, in characters. Counts `source=pmc` section and subsection text — which carries the inline blocks the parser renders in place, such as lists, definition lists, block quotes, boxed text, preformatted blocks and displayed formulae — plus table label, caption, cell and footnote text and asset label, caption and `href` text; or the `source=unpaywall` `content` body. Titles, abstracts, identifiers, licenses, and references are never counted or shortened. Shortened text ends at the last word boundary inside its allowance, so it can come back a few characters under it; a section or subsection whose allowance cannot hold its first word returns no text rather than part of that word, so it is dropped in `truncate` mode and heading-only in `outline` mode, while text that is one unbroken token, such as a sequence or URL, is cut at the allowance. The counted unit is that text alone — the Markdown grid `content[]` renders around the cells (pipes, padding, the divider row, headings) is scaffolding this budget does not measure, so a table renders longer than it costs here. Body sections are served first, then tables, then assets, then back-matter sections, each spending what is left, in document order. For tables and assets, admission stops at the first entry that does not fit, and every entry from there on is dropped whole rather than cut mid-row or returned with a shortened caption, counted in `truncation.omittedTables` / `truncation.omittedAssets` and named in `truncation.articles[].omittedTableNames` / `omittedAssetNames`. Back matter takes only what remains and is shortened or dropped as body sections are; `sections` still returns it after the body. Applied after `sections`, `maxSections`, `includeReferences`, `includeTables`, and `includeAssets`, so semantic filtering is unaffected. This knob alone bounds only bodies: the response-wide ceiling it implies is this value times the number of articles returned, plus every uncounted field. Use `maxResponseCharacters` for a true whole-response ceiling. Omit for the full body.",
      "type": "integer",
      "minimum": 1,
      "maximum": 9007199254740991
    },
    "maxCharactersPerSection": {
      "description": "Budget for a single top-level section, in characters, counting the section text plus its subsections. Combine with `maxCharacters` to cap both one section and the article; the tighter of the two wins. Applies to `source=pmc` results only.",
      "type": "integer",
      "minimum": 1,
      "maximum": 9007199254740991
    },
    "maxResponseCharacters": {
      "description": "Opt-in ceiling for the whole response, in characters — the true response-wide counterpart to the per-article `maxCharacters`. Each article is measured as the JSON record it is returned as, after every filter and the per-article body budget: title, abstract, sections, references, identifiers, license and source metadata — every field it carries. One ledger covers all tiers, so PMC-, Europe PMC-, and Unpaywall-served articles spend the same budget. Articles are kept in the order `articles` lists them until the next one would cross the ceiling; that article and the rest are deferred whole (never partially populated) and listed in `deferred.ids`. Response envelope fields — counts, `unavailable`, `truncation`, `sectionCap`, `deferred` itself — are not counted. Omit to return every resolved article.",
      "type": "integer",
      "minimum": 1,
      "maximum": 9007199254740991
    },
    "overflowMode": {
      "default": "truncate",
      "description": "How to spend `maxCharacters` across an article that exceeds it. truncate: fill sections in document order, so early sections stay whole, the section the budget runs out in is cut, and every section or subsection past that point is dropped (counted in `truncation.omittedSections`). outline: every section and subsection keeps its heading, and the budget is split evenly at every level — across the top-level sections, then inside each one across its own text and each subsection — with what a short part does not need going to the rest. A part whose share would cut it to under 100 characters (or under `maxCharactersPerSection`, when that is lower) returns heading-only instead, its share going to the others, emptying the last such part first; a part that fits its share keeps all its text however short, and a cut excerpt ends at the last word boundary inside its share, so it can run somewhat under that floor. A heading the budget left empty is marked as such in the rendered text. In both modes the body sections spend the budget first and back-matter sections share what the body, tables, and assets leave. Use it to survey what an article contains before requesting specific `sections`. Ignored when no budget is set, and identical for `source=unpaywall` bodies, which have no headings to preserve.",
      "type": "string",
      "enum": [
        "truncate",
        "outline"
      ]
    }
  },
  "required": [
    "includeReferences",
    "includeTables",
    "includeAssets",
    "overflowMode"
  ],
  "additionalProperties": false
}
view source ↗

pubmed_format_citations

open-world

Get formatted citations for PubMed articles in one or more formats (apa, mla, bibtex, ris, vancouver). Pass a single format as a string or multiple as an array. Retractions, errata, and expressions of concern NCBI links to an article come back in `notices`; Vancouver and APA also cite a retraction in the reference itself.

read
invocation
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "pubmed_format_citations",
    "arguments": {
      "pmids": "<pmids>"
    }
  }
}
schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "pmids": {
      "minItems": 1,
      "maxItems": 50,
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^\\d+$"
      },
      "description": "PubMed IDs to cite"
    },
    "format": {
      "default": "apa",
      "description": "Citation format(s) to generate — single style as a string or multiple as an array. Allowed values: apa, mla, bibtex, ris, vancouver.",
      "anyOf": [
        {
          "type": "string",
          "enum": [
            "apa",
            "mla",
            "bibtex",
            "ris",
            "vancouver"
          ],
          "description": "Single citation style. One of: apa, mla, bibtex, ris, vancouver."
        },
        {
          "minItems": 1,
          "type": "array",
          "items": {
            "type": "string",
            "enum": [
              "apa",
              "mla",
              "bibtex",
              "ris",
              "vancouver"
            ]
          },
          "description": "Multiple citation styles to generate. Each entry: apa, mla, bibtex, ris, or vancouver."
        }
      ]
    }
  },
  "required": [
    "pmids",
    "format"
  ],
  "additionalProperties": false
}
view source ↗

pubmed_spell_check

open-world

Spell-check a PubMed search query against NCBI ESpell and get the corrected query back. Use after a zero-hit or thin `pubmed_search_articles` result, or when a drug, gene, disease, or author name may be misspelled. Corrections are applied in place, so field tags, operators, spacing, and gene symbols stay as written (`alzhiemer diseese treatmnt outcomse` → `alzheimer disease treatment outcomes`). The value of an indexed field — MeSH, publication type, journal, author, language, subset, and the like (`aged[mh]`, `free full text[sb]`, `zhang y[au]`) — is kept as written, misspelled or not, since the ESpell dictionary is not the index that field searches; free-text fields such as `[tiab]`, `[ti]`, and `[tw]` are corrected. Words in all capitals, with digits or non-ASCII letters, or differing only in case are never changed, nor is a single letter swapped for another (`q fever`, the initial in `smith q`), words after a number or symbol ESpell skips are left as written, and `hasSuggestion` is false when no correction was applied. Re-run the search with `corrected`.

read
invocation
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "pubmed_spell_check",
    "arguments": {
      "query": "<query>"
    }
  }
}
schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 2,
      "description": "PubMed search query to spell-check. Must carry a term: a value of only whitespace or invisible characters, such as a zero-width space, is rejected rather than sent to ESpell."
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}
view source ↗

pubmed_lookup_mesh

open-world

Search and explore the MeSH (Medical Subject Headings) controlled vocabulary. Returns descriptor records with tree numbers, scope notes, and entry terms, plus pagination via offset for paging past the maxResults cap.

read
invocation
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "pubmed_lookup_mesh",
    "arguments": {
      "query": "<query>"
    }
  }
}
schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "description": "MeSH descriptor name or free-text term to look up. Must carry a term: a value of only whitespace or invisible characters, such as a zero-width space, is rejected rather than searched."
    },
    "maxResults": {
      "default": 10,
      "description": "Maximum results",
      "type": "integer",
      "minimum": 1,
      "maximum": 50
    },
    "offset": {
      "default": 0,
      "description": "Result offset for pagination (0-based). Pass the `nextOffset` from the previous response to get the following page; the exact-descriptor match is pinned to the first page only.",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    },
    "includeDetails": {
      "default": true,
      "description": "Fetch full MeSH records (scope notes, tree numbers, entry terms)",
      "type": "boolean"
    }
  },
  "required": [
    "query",
    "maxResults",
    "offset",
    "includeDetails"
  ],
  "additionalProperties": false
}
view source ↗

pubmed_lookup_citation

open-world

Look up PubMed IDs from partial bibliographic citations. Useful when you have a reference (journal, year, volume, page, author) and need the PMID — deterministic citation matching, more reliable than free-text search for structured references. Each citation must include at least journal or a four-digit year (ECitMatch primary-keys on journal+volume+page; author-only or volume-only inputs guarantee no match); more fields = better match accuracy.

read
invocation
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "pubmed_lookup_citation",
    "arguments": {
      "citations": "<citations>"
    }
  }
}
schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "citations": {
      "description": "Citations to look up, 1–25, each matched independently. More fields = better match accuracy.",
      "minItems": 1,
      "maxItems": 25,
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "journal": {
            "description": "Journal title or ISO abbreviation (e.g., \"proc natl acad sci u s a\"). Must contain a visible character, and cannot contain a pipe (\"|\") or a line break.",
            "type": "string",
            "pattern": "^[^|\\r\\n]*$"
          },
          "year": {
            "description": "Publication year as four digits (e.g., \"1991\").",
            "type": "string",
            "pattern": "^[ \\t]*\\d{4}[ \\t]*$"
          },
          "volume": {
            "description": "Volume number. Must contain a visible character, and cannot contain a pipe (\"|\") or a line break.",
            "type": "string",
            "pattern": "^[^|\\r\\n]*$"
          },
          "firstPage": {
            "description": "First page number. Must contain a visible character, and cannot contain a pipe (\"|\") or a line break.",
            "type": "string",
            "pattern": "^[^|\\r\\n]*$"
          },
          "authorName": {
            "description": "Author name, typically \"lastname initials\" (e.g., \"mann bj\"). Must contain a visible character, and cannot contain a pipe (\"|\") or a line break.",
            "type": "string",
            "pattern": "^[^|\\r\\n]*$"
          },
          "key": {
            "description": "Arbitrary label to track this citation in results. Auto-assigned if omitted. Echoed back unchanged and never sent to NCBI, so any character is accepted here.",
            "type": "string"
          }
        },
        "additionalProperties": false,
        "description": "Citation to match against PubMed. Must include at least journal or a four-digit year — ECitMatch primary-keys on journal+volume+page, so author-only or volume-only inputs guarantee no match."
      }
    }
  },
  "required": [
    "citations"
  ],
  "additionalProperties": false
}
view source ↗

pubmed_convert_ids

open-world

Convert between article identifiers (DOI, PMID, PMCID). Accepts up to 50 IDs of a single type per request. Only resolves articles indexed in PubMed Central — for articles not in PMC, use pubmed_search_articles instead.

read
invocation
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "pubmed_convert_ids",
    "arguments": {
      "ids": "<ids>",
      "idType": "<idType>"
    }
  }
}
schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ids": {
      "minItems": 1,
      "maxItems": 50,
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1
      },
      "description": "Article identifiers to convert — one identifier per element, all of the same type. Each element is checked against `idType` before the request: `doi` starts with \"10.\" and carries a \"/\" (\"10.1093/nar/gks1195\"); `pmid` is digits (\"23193287\"); `pmcid` is digits with an optional \"PMC\" prefix (\"PMC3531190\" or \"3531190\"). No element may contain a comma or whitespace — a packed value like \"23193287,37952131\" is rejected, so split it across elements."
    },
    "idType": {
      "type": "string",
      "enum": [
        "pmcid",
        "pmid",
        "doi"
      ],
      "description": "The type of IDs being submitted. Required so the API can unambiguously resolve them."
    }
  },
  "required": [
    "ids",
    "idType"
  ],
  "additionalProperties": false
}
view source ↗

pubmed_fetch_citation_metrics

open-world

Fetch NIH iCite citation metrics for PubMed articles: the Relative Citation Ratio (RCR), NIH percentile, citation count, citations per year, expected and field citation rates, the Approximate Potential to Translate (APT), the human, animal, and molecular/cellular shares of each article's MeSH terms, and how many clinical articles cite it. RCR is a field- and year-normalized citation rate benchmarked to NIH-funded papers, whose median RCR is 1.0; iCite computes none for the most recent papers and marks recent ones provisional. iCite does not flag retractions — a retracted article keeps its metrics — so check pubmed_fetch_articles for retraction notices before relying on a record. Up to 1000 PMIDs per call; the first 200 distinct PMIDs are fetched and the rest returned in `overLimit`. PMIDs iCite has no record for are listed in `unavailablePmids`.

read
invocation
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "pubmed_fetch_citation_metrics",
    "arguments": {
      "pmids": "<pmids>"
    }
  }
}
schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "pmids": {
      "minItems": 1,
      "maxItems": 1000,
      "type": "array",
      "items": {
        "type": "string",
        "pattern": "^\\d+$"
      },
      "description": "PubMed IDs to look up (e.g. [\"23456789\"]). The first 200 distinct PMIDs are fetched; the rest are returned in `overLimit`. Leading zeros are ignored, so \"00023456789\" and \"23456789\" name one article."
    }
  },
  "required": [
    "pmids"
  ],
  "additionalProperties": false
}
view source ↗

pubmed_europepmc_fetch

open-world

Fetch complete Europe PMC records — including the full, untruncated abstract — addressed as `records: [{ source, epmcId }]`, an array even for one record. Pairs with `pubmed_europepmc_search`, which returns bounded `abstractSnippet` values and flags cut ones with `abstractTruncated: true`; copy each hit's `source` and `epmcId` into `records` here to read the whole abstract. This is the retrieval path for preprint (`PPR`), patent (`PAT`), and Agricola (`AGR`) records, which frequently carry no PMID and no DOI, so `pubmed_fetch_articles` and `pubmed_fetch_fulltext` cannot address them. Up to 25 records per call. Set `maxResponseCharacters` to bound the whole response: records past the ceiling are deferred whole and listed in `deferred.records` for a follow-up call.

read
invocation
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "pubmed_europepmc_fetch",
    "arguments": {
      "records": "<records>"
    }
  }
}
schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "records": {
      "minItems": 1,
      "maxItems": 25,
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "source": {
            "description": "Europe PMC source corpus — `MED` (PubMed), `PMC` (PubMed Central), `PPR` (preprint), `PAT` (patent), `AGR` (Agricola). Copy it from the search hit's `source`. `PMC` paired with a PMCID resolves whether or not the article is also indexed in PubMed, and a PubMed-indexed one comes back as its canonical `MED` record carrying that PMCID in `pmcId`.",
            "type": "string",
            "enum": [
              "MED",
              "PMC",
              "PPR",
              "PAT",
              "AGR"
            ]
          },
          "epmcId": {
            "type": "string",
            "maxLength": 64,
            "pattern": "^[A-Za-z0-9][A-Za-z0-9._-]*$",
            "description": "Europe PMC's own record id within that source. Copy it from the search hit's `epmcId` — for `MED` records this is the PMID; for the other sources it is an EPMC-native accession."
          }
        },
        "required": [
          "source",
          "epmcId"
        ],
        "additionalProperties": false,
        "description": "One record address: the Europe PMC source corpus plus its id within that corpus"
      },
      "description": "Records to retrieve, each addressed by the `source` and `epmcId` of a `pubmed_europepmc_search` hit. The whole batch resolves in one Europe PMC request."
    },
    "maxResponseCharacters": {
      "description": "Opt-in ceiling for the whole response, in characters. Each record is measured as the JSON record it is returned as — title, authors, journal, abstract, identifiers, every field it carries. Records are kept in the order Europe PMC returned them until the next one would cross the ceiling; that record and the rest are deferred whole (never partially populated) and listed in `deferred.records`. Response envelope fields — `notFound`, `deferred` itself — are not counted. Omit to return every resolved record.",
      "type": "integer",
      "minimum": 1,
      "maximum": 9007199254740991
    }
  },
  "required": [
    "records"
  ],
  "additionalProperties": false
}
view source ↗

Resources

1

PubMed database metadata including field list, last update date, and record count.

uri pubmed://database/info mime application/json

Prompts

1

Generate a structured research plan outline for a biomedical research project.

  • titlerequired — Project title
  • goalrequired — Primary research goal
  • keywordsrequired — Research keywords (comma-separated)
  • organism — Target organism
  • includeAgentPrompts — Include inline guidance blocks under each phase with execution-time hints ("true" or "false"; omitted = "false")