Semantic Scholar MCP Server

Semantic Scholar MCP Server

[CI] [codecov] [PyPI version] [PyPI downloads/30d] [DOI] [Provenance: SLSA + SBOM] [Docker] [GitHub Release] [License: MIT] [MCP] [Python 3.11-3.13 recommended] [Glama score] [Awesome MCP Servers]

A 14-tool Semantic Scholar MCP server for academic research workflows. Direct access to 200M+ papers from Semantic Scholar — paper search, citation graph traversal, author profiles, and recommendations — from any Model Context Protocol client (e.g., Claude Desktop, Claude Code, Cursor, Cline, Continue, and others).

Every release ships verifiable supply-chain provenance: Sigstore-signed SLSA build-provenance attestations on the wheel, sdist, and container image; PEP 740 attestations on the PyPI upload; and a CycloneDX SBOM — so you can prove the artifact you installed was built from this repo. See Provenance & supply chain.

Author: Santiago Maniches · ORCID 0009-0005-6480-1987 · TOPOLOGICA LLC

Research authorship: Santiago Maniches independently directs and maintains this project and is the sole scientific author of its research contributions. AI-assisted tools have supported coding, documentation, and internal review; they do not constitute scientific coauthors or independent validation. Semantic Scholar content and reused software and methods are attributed to their respective sources.

Quick start

uvx s2-mcp-server                                      # run instantly, no installclaude mcp add semantic-scholar -- uvx s2-mcp-server   # or register it in Claude Code

Runtime support (October 2026). Python 3.11–3.13 are the recommended, CI-tested interpreters. Python 3.10 reached upstream end of life on October 1, 2026 and no longer receives security fixes. The package retains Requires-Python >=3.10 and a legacy Python 3.10 compatibility test to avoid breaking existing installs, but Python 3.10 is not a security-supported runtime. Migrate deployed clients to Python 3.11 or newer. Python 3.14+ remains outside the declared CI verification matrix; installability is not a claim of tested support. The development dependency security audit runs on Python 3.12 and checks its hash-pinned closure, not every legacy environment.

No API key is needed to start. Set SEMANTIC_SCHOLAR_API_KEY to use your assigned Semantic Scholar quota and avoid the shared unauthenticated pool. Semantic Scholar currently assigns introductory API keys a 1 request/second limit across all endpoints. Claude Desktop, Docker, pip, and remote (Streamable HTTP) setups are in Installation.

Provenance & supply chain

A research tool is only as trustworthy as the chain from its source to the binary you run. Every release of this server ships cryptographically verifiable supply-chain evidence, all generated in CI from the tagged commit:

Verify the wheel and the container image against their attestations with the GitHub CLI:

# Wheel / sdist (download from the PyPI project or the release assets first)gh attestation verify s2_mcp_server-*.whl --repo smaniches/semantic-scholar-mcp
# Container imagegh attestation verify oci://ghcr.io/smaniches/semantic-scholar-mcp:latest \  --repo smaniches/semantic-scholar-mcp

The full supply-chain posture, including the known-limitations list, is in SECURITY.md. This is release-time provenance (proving how the artifact was built); the server does not currently attach a per-response receipt to individual API results.

How it compares

There is no public Semantic Scholar MCP standard, so the most useful comparison is against the obvious alternative: calling the Semantic Scholar REST API yourself from an agent. Everything in the right-hand column is plumbing this server already owns and the caller would otherwise reimplement.

Installation

Option 1: One-Line Install (Recommended)

# No cloning needed — runs directly from PyPIuvx s2-mcp-server

Option 2: Claude Code

claude mcp add semantic-scholar -- uvx s2-mcp-server

Option 3: Claude Desktop (Windows)

Add to %APPDATA%\Claude\claude_desktop_config.json:

{  "mcpServers": {    "semantic-scholar": {      "command": "uvx",      "args": ["s2-mcp-server"],      "env": {        "SEMANTIC_SCHOLAR_API_KEY": "your-key-here"      }    }  }}

Option 4: Claude Desktop (macOS)

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{  "mcpServers": {    "semantic-scholar": {      "command": "uvx",      "args": ["s2-mcp-server"],      "env": {        "SEMANTIC_SCHOLAR_API_KEY": "your-key-here"      }    }  }}

Option 5: pip / From Source

pip install s2-mcp-server# orgit clone https://github.com/smaniches/semantic-scholar-mcp.gitcd semantic-scholar-mcp && pip install -e .

Option 6: Docker

docker pull ghcr.io/smaniches/semantic-scholar-mcp:latestdocker run -e SEMANTIC_SCHOLAR_API_KEY=your-key ghcr.io/smaniches/semantic-scholar-mcp

Option 7: Remote server (Streamable HTTP) — requires ≥ 1.5.0

# Serve MCP over HTTP at http://127.0.0.1:8000/mcp instead of stdio# (--from pins the floor: uvx may otherwise reuse a cached older version)uvx --from "s2-mcp-server>=1.5.0" s2-mcp-server --transport http

See Remote access (Streamable HTTP) for client configuration, per-request API keys, and deployment guidance.

Note: An API key is optional for most public Semantic Scholar endpoints. This server conservatively throttles unkeyed requests to about one per second, but anonymous users share an upstream pool. Semantic Scholar can return HTTP 429 even when this server respects its local interval. For dependable, sustained research workflows, configure an assigned API key. See Known Limitations.

Architecture

flowchart LR  Client["MCP client<br/>(Claude Desktop, Claude Code,<br/>Cursor, Cline, Continue, …)"]  subgraph Server ["s2-mcp-server (this package)"]    direction TB    FastMCP["FastMCP runtime<br/>(stdio / Streamable HTTP, lifespan)"]    Tools["14 @mcp.tool functions<br/>(server.py)"]    Models["Pydantic input models<br/>+ field sets (models.py)"]    Validators["Paper-ID validator<br/>(validators.py)"]    Cache["TTL cache<br/>(cache.py)"]    Fmt["Markdown formatters<br/>(formatters.py)"]    HTTP["httpx client<br/>+ rate limit + retry/backoff<br/>(client.py)"]    Errors["Typed exceptions<br/>(errors.py)"]    Log["Structured JSON logger<br/>(logging_config.py)"]  end  S2Graph["Semantic Scholar<br/>Graph API"]  S2Recs["Semantic Scholar<br/>Recommendations API"]
  Client <-- "stdio or Streamable HTTP<br/>(JSON-RPC)" --> FastMCP  FastMCP --> Tools  Tools --> Models  Tools --> Validators  Tools --> Cache  Tools --> HTTP  Tools --> Fmt  HTTP --> Errors  HTTP --> Log  HTTP -- "GET / POST<br/>x-api-key" --> S2Graph  HTTP -- "GET / POST<br/>x-api-key" --> S2Recs

Module responsibilities (src/semantic_scholar_mcp/):

Design choices worth knowing

• Single httpx.AsyncClient per process. Created lazily, closed in the FastMCP lifespan teardown. Amortizes connection setup; respects keep-alive limits. The lifespan is reference-counted: under the Streamable HTTP transport the SDK enters it per request, so teardown only runs when the last holder exits.
• Rate limit is enforced at the client, not the API. A semaphore + last-request timestamp ensures we never exceed the per-tier interval even when the MCP host issues tool calls in parallel.
• Retry is bounded and jittered. Up to MAX_RETRIES = 3, base 1 s, capped at 30 s. Honors Retry-After when present.
• Errors are typed. Status codes map onto a small exception hierarchy so callers can branch on AuthenticationError vs RateLimitError vs NotFoundError instead of parsing strings.
• Input validation is pre-flight. Paper IDs are checked before any outbound request; bad IDs never hit the wire.
• Version is single-source. __version__ is derived from importlib.metadata.version("s2-mcp-server"), so bumping pyproject.toml is sufficient; release-please bumps the manifest, server.json (×2 paths), CITATION.cff, and .zenodo.json in lockstep on every release.

Configuration

API Key Options

You can provide your API key in three ways:

1. Environment Variable (recommended for persistent use):

   bash

   export SEMANTIC_SCHOLAR_API_KEY="your-api-key-here"

2. Per-request HTTP header (Streamable HTTP transport only): send x-api-key: your-key with each request — see Remote access (Streamable HTTP).

3. Per-Request Parameter (overrides env var):

   json

   {  "api_key": "your-api-key-here"}

   Deprecated: per-request api_key is deprecated and will be removed in v2.0.0. Tool-call arguments may be visible in MCP transcripts, client logs, and the LLM's tool-call history. Use the SEMANTIC_SCHOLAR_API_KEY environment variable instead. See SECURITY.md for details.

Get a free API key at: https://www.semanticscholar.org/product/api

Claude Desktop Setup

Add to your Claude Desktop config file:

Windows: %APPDATA%\Claude\claude_desktop_config.json macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Linux: ~/.config/Claude/claude_desktop_config.json

{  "mcpServers": {    "semantic-scholar": {      "command": "python",      "args": ["-m", "semantic_scholar_mcp"],      "env": {        "SEMANTIC_SCHOLAR_API_KEY": "your-api-key-here"      }    }  }}

Then restart Claude Desktop.

Remote access (Streamable HTTP)

stdio remains the default transport. --transport http serves the same 14 tools over the MCP Streamable HTTP transport, which is what remote clients — claude.ai custom connectors, Smithery listings, mcp-remote bridges — connect to.

Requires s2-mcp-server ≥ 1.5.0. Earlier releases (≤ 1.4.0) do not parse CLI flags: they silently ignore --transport http and start a stdio server instead, never opening the port.

# Local HTTP endpoint at http://127.0.0.1:8000/mcp# (--from pins the floor: uvx may otherwise reuse a cached older version)uvx --from "s2-mcp-server>=1.5.0" s2-mcp-server --transport http
# Bind a public interface and custom port (only behind a TLS proxy — see Security).# The DNS-rebinding guard only admits localhost Host headers by default, so# also allow the public hostname clients will use (":*" matches any port).uvx --from "s2-mcp-server>=1.7.1" s2-mcp-server --transport http --host 0.0.0.0 --port 8080 \  --allowed-host "mcp.example.org:*"
# Dockerdocker run -p 8000:8000 ghcr.io/smaniches/semantic-scholar-mcp --transport http

Flags and environment variables

CLI flags beat environment variables. The server is stateless and returns JSON by default — the configuration recommended for production Streamable HTTP deployments — and no tool relies on sessions, streaming, or server-initiated messages, so there is no functional trade-off.

Per-request API keys (bring your own key)

When served over HTTP, each request may carry its own Semantic Scholar API key; concurrent users never share or observe each other's keys. Sources, in precedence order:

1. x-api-key HTTP header (recommended)
2. SEMANTIC_SCHOLAR_API_KEY query parameter (Smithery session config)
3. api_key query parameter
4. Legacy base64 ?config= parameter (older Smithery deployments)

A request without a key falls back to the server's SEMANTIC_SCHOLAR_API_KEY environment variable, or to keyless public-tier access.

Client configuration

Claude Code

claude mcp add --transport http semantic-scholar http://127.0.0.1:8000/mcp \  --header "x-api-key: your-key-here"

JSON config (clients that accept a url)

{  "mcpServers": {    "semantic-scholar": {      "type": "http",      "url": "http://127.0.0.1:8000/mcp",      "headers": { "x-api-key": "your-key-here" }    }  }}

claude.ai custom connectors require a public HTTPS URL and accept either authless servers or OAuth — API keys in the connector URL are not supported by claude.ai. Host the server with the key supplied server-side (SEMANTIC_SCHOLAR_API_KEY env var) and register the public /mcp URL as the connector.

Smithery lists remote servers by URL (smithery mcp publish <url>); the per-request key extraction above is compatible with Smithery session config out of the box.

Security notes

• The HTTP transport performs no authentication of inbound callers. The default bind is loopback (127.0.0.1). Expose it publicly only behind a TLS-terminating reverse proxy.
• The built-in Uvicorn request access log is disabled to avoid recording URL credentials, but proxies, gateways and other upstream systems may still log full request URLs. Query parameters, including base64 ?config=, are not safe places for secrets. Prefer the x-api-key header or a server-side environment variable. See SECURITY.md.
• See SECURITY.md for the project's broader threat model.

Supported ID Formats

The server accepts the following paper identifier formats:

Tools Reference

1. semantic_scholar_search_papers

Search for academic papers with advanced filters.

Parameters:

Example:

Search for "transformer attention mechanism" papers from 2023 with at least 100 citations

JSON Example:

{  "query": "transformer attention mechanism",  "year": "2023",  "min_citation_count": 100,  "fields_of_study": ["Computer Science"],  "limit": 20}

2. semantic_scholar_get_paper

Get detailed information about a specific paper.

Parameters:

Example:

Get details for DOI:10.1038/s41586-021-03819-2 including its top 20 citations

JSON Example:

{  "paper_id": "DOI:10.1038/s41586-021-03819-2",  "include_citations": true,  "citations_limit": 20,  "citations_offset": 0,  "response_format": "json"}

Citation and reference pages are independent. In JSON mode, requested directions retain the existing citations / references arrays and additionally return citations_page / references_page metadata with offset and next. When next is non-null, use it as that direction's *_offset on the next call with the same paper ID and limit. A null next means no continuation was advertised by Semantic Scholar. Markdown mode prints a continuation hint when one is available. Never treat a first page as a complete citation graph.

3. semantic_scholar_search_authors

Search for academic authors by name.

Parameters:

Example:

Find author "Yoshua Bengio"

JSON Example:

{  "query": "Yoshua Bengio",  "limit": 5}

4. semantic_scholar_get_author

Get author profile with publications.

Parameters:

Example:

Get author profile for author ID 1741101 with their top 50 publications

JSON Example:

{  "author_id": "1741101",  "include_papers": true,  "papers_limit": 50}

5. semantic_scholar_recommendations

Get AI-powered paper recommendations based on a seed paper.

Parameters:

Example:

Get recommendations based on paper 649def34f8be52c8b66281af98ae884c09aef38b

JSON Example:

{  "paper_id": "ARXIV:1706.03762",  "limit": 15}

6. semantic_scholar_bulk_papers

Retrieve multiple papers in a single request (max 500).

Parameters:

Example:

Retrieve these papers: DOI:10.1038/nature12373, ARXIV:2106.15928, PMID:32908142

JSON Example:

{  "paper_ids": [    "DOI:10.1038/nature12373",    "ARXIV:2106.15928",    "PMID:32908142"  ]}

7. semantic_scholar_bulk_search

Search papers with sorting and cursor-based pagination for large result sets. Unlike search_papers, supports a sort order and returns a token for paging through all results.

Parameters:

JSON Example:

{  "query": "graph neural networks",  "sort": "citationCount:desc",  "year": "2020-2024",  "limit": 100}

Returns: total result count, the page of papers, and a token for the next page (when more results exist).

8. semantic_scholar_export_citation

Export a citation for a paper in BibTeX format.

Parameters:

JSON Example:

{  "paper_id": "DOI:10.1038/s41586-021-03819-2",  "format": "bibtex"}

Returns: the BibTeX string for the requested paper.

9. semantic_scholar_match_paper

Find the single best paper matching a title string. Returns a numeric matchScore alongside the matched paper.

Parameters:

JSON Example:

{  "query": "Attention Is All You Need"}

Returns: the best-matching paper plus its matchScore, or "No matching paper found." if no match.

10. semantic_scholar_paper_authors

Get full author profiles for a paper's authors (richer than the abbreviated author list returned by get_paper).

Parameters:

JSON Example:

{  "paper_id": "ARXIV:1706.03762",  "limit": 25}

Returns: the list of full author records for the paper.

11. semantic_scholar_author_batch

Retrieve multiple authors in a single request (max 1000).

Parameters:

JSON Example:

{  "author_ids": ["1741101", "40348417", "144749327"]}

Returns: counts of requested / retrieved, the retrieved author records, and a not_found list of IDs the API did not return.

12. semantic_scholar_multi_recommend

Get recommendations using multiple positive (and optional negative) example papers.

Parameters:

JSON Example:

{  "positive_paper_ids": ["ARXIV:1706.03762", "ARXIV:1810.04805"],  "negative_paper_ids": ["DOI:10.1038/nature14539"],  "limit": 20}

Returns: the recommended papers plus an echo of the positive/negative seeds used.

13. semantic_scholar_snippet_search

Search within paper full text and return text snippets with surrounding context. Heavily rate-limited without an API key.

Parameters:

JSON Example:

{  "query": "scaling laws for language models",  "year": "2022-2024",  "limit": 20}

Returns: matching snippets, each with the source paper title, section, and a short text excerpt.

14. semantic_scholar_status

Check server health and API connectivity status.

Parameters: None

Example:

Check Semantic Scholar API status

Response:

{  "server": "semantic-scholar-mcp",  "version": "<current package version>",  "api_key_configured": true,  "rate_tier": "authenticated",  "configuration_valid": true,  "min_seconds_between_requests": 1.1,  "effective_client_max_requests_per_second": 0.909091,  "timestamp": "2026-04-06T12:00:00.000000+00:00",  "api_reachable": true,  "rate_limited": false,  "retry_after": null}

Rate Limits

Semantic Scholar's current API guidance says introductory API keys receive 1 request/second across all endpoints, while some keys may receive a higher rate after review. Unauthenticated requests share upstream capacity and may be throttled during heavy use.

The server therefore uses these conservative client-side defaults:

If Semantic Scholar has explicitly assigned your key a different quota, set SEMANTIC_SCHOLAR_MIN_SECONDS_BETWEEN_REQUESTS to an interval that stays below that ceiling. For example, a reviewed 10 RPS quota should use an interval slightly greater than 0.1 seconds rather than assuming every API key has that rate. The setting is process-wide, so remote deployments accepting multiple user-provided keys should configure it for the slowest accepted quota.

The server automatically handles rate limiting with:

• Request serialization to enforce minimum intervals
• Exponential backoff retry for 429 (rate limit), 502 (bad gateway), and 503 (service unavailable) errors
• Maximum 3 retries with jitter

Development

# Clonegit clone https://github.com/smaniches/semantic-scholar-mcp.gitcd semantic-scholar-mcp
# Install dev dependenciespip install -e ".[dev]"
# Run testspytest
# Run tests with coveragepytest --cov=src/semantic_scholar_mcp --cov-report=term-missing
# Type checkingmypy src/

Security

API keys are never persisted to disk by the server. When the server makes authenticated requests, the key is sent only to api.semanticscholar.org over HTTPS as the x-api-key header. No telemetry is sent to any third party. Under the default stdio transport the server runs locally on your machine; if you connect to a remotely hosted instance over Streamable HTTP, your per-request key also transits that endpoint's operator before being forwarded to Semantic Scholar — only send keys to remote endpoints you trust, and only over HTTPS.

Prefer the SEMANTIC_SCHOLAR_API_KEY environment variable over the per-request api_key tool parameter. The per-request parameter is deprecated (removal planned for v2.0.0) because tool-call arguments may be visible in MCP transcripts and client logs. See SECURITY.md for vulnerability reporting and the known-limitations list.

Related MCP servers by the same author

• alphafold-sovereign-mcp — Model Context Protocol server for AlphaFold DB and other public biomedical data sources, with a local SQLite knowledge graph (pip install alphafold-sovereign-mcp).
• uniprot-mcp — Model Context Protocol server for UniProt Swiss-Prot and TrEMBL (pip install uniprot-mcp-server).

License

MIT License - see LICENSE file.

Author

Santiago Maniches

• Founder & CEO, TOPOLOGICA LLC
• ORCID: 0009-0005-6480-1987
• LinkedIn: santiago-maniches
• Website: topologica.ai

Contributing

Contributions welcome! Please read our Contributing Guidelines.

Support

• Issues: GitHub Issues
• Contact: [email protected]

Built by TOPOLOGICA LLC