@cyanheads/openalex-mcp-server
Access the OpenAlex academic research catalog - 270M+ publications through MCP. Supports STDIO and Streamable HTTP.
README
<div align="center"> <h1>@cyanheads/openalex-mcp-server</h1> <p><b>Access the OpenAlex academic research catalog - 270M+ publications through MCP. STDIO & Streamable HTTP.</b> <div>4 Tools • 2 Prompts</div> </p> </div>
<div align="center">
</div>
<div align="center">
</div>
<div align="center">
Public Hosted Server: https://openalex.caseyjhand.com/mcp
</div>
Tools
Four tools for querying the OpenAlex academic research catalog:
| Tool Name | Description |
|---|---|
openalex_search_entities |
Search, filter, sort, or retrieve by ID across all 8 entity types. |
openalex_analyze_trends |
Group-by aggregation for trend and distribution analysis. |
openalex_resolve_name |
Resolve a name or partial name to an OpenAlex ID via autocomplete. |
openalex_get_citation_graph |
Walk the citation graph one hop from a seed work: cites, cited_by, or related_to. |
openalex_search_entities
Primary discovery and lookup tool. Covers all OpenAlex entity types (works, authors, sources, institutions, topics, keywords, publishers, funders).
- Retrieve a single entity by ID (OpenAlex ID, DOI, ORCID, ROR, PMID, PMCID, ISSN)
- Keyword search with boolean operators, quoted phrases, wildcards, and fuzzy matching
- Exact and AI semantic search modes
- Rich filter syntax: AND across fields, OR within fields (
us|gb), NOT (!us), ranges (2020-2024), comparisons (>100) - Sensible default field selection per entity type — prevents oversized responses; pass
selectto override - Invalid
selectfield names produce an error listing the valid fields for that entity type - Formatted MCP output is a generic markdown renderer — every returned field is surfaced without per-entity-type hard-coding
- Cursor pagination, sorting, up to 100 results per page
openalex_analyze_trends
Aggregate entities into groups and count them for trend, distribution, and comparative analysis.
- Group by any supported field (publication year, OA status, institution, country, topic, etc.)
- Combine with filters to scope the population before aggregation
- Up to 200 groups per page with cursor pagination
- Supports
include_unknownto show entities with no value for the grouped field
openalex_resolve_name
Name-to-ID resolution via autocomplete. Always use this before filtering by entity — names are ambiguous, IDs are not.
- Returns up to 10 matches with disambiguation hints
- Accepts partial names and DOIs for direct lookup
- Optional entity type filter and field-level filters
- ~200ms response time
openalex_get_citation_graph
One-hop citation graph traversal from a seed work. Wraps the OpenAlex cites/cited_by/related_to filters behind an explicit direction argument so callers do not have to know the filter names.
cites: works that cite the seed (incoming citations)cited_by: works the seed cites (its reference list)related_to: OpenAlex algorithmic "related works" (~8-30 typical, may be empty for less-cited seeds)- Accepts OpenAlex IDs, DOIs, PMIDs, PMCIDs as
seed_id; validates the seed via a singleton/works/{id}lookup before walking, so non-existent seeds surface asNotFound - Stacks with
filters/sort/selectto narrow the graph (e.g.,publication_year=">2020",is_oa="true")
Prompts
| Prompt | Description |
|---|---|
openalex_literature_review |
Guides a systematic literature search: formulate query, search, filter, analyze citation network, synthesize findings. |
openalex_research_landscape |
Analyzes the research landscape for a topic: volume trends, top authors/institutions, open access rates, funding sources. |
Features
Built on @cyanheads/mcp-ts-core:
- Declarative tool definitions — single file per tool, framework handles registration and validation
- Unified error handling across all tools
- Pluggable auth (
none,jwt,oauth) - Swappable storage backends via the framework (not currently used by this server)
- Structured logging with optional OpenTelemetry tracing
- Runs locally (stdio/HTTP) or in Docker from the same codebase
OpenAlex-specific:
- Typed API client with automatic ID normalization (DOI, ORCID, ROR, PMID, PMCID, ISSN, OpenAlex URLs)
- Abstract reconstruction from inverted indices — plaintext instead of OpenAlex's position-keyed encoding
- HTTP status codes mapped to specific MCP error classes (400/422 → InvalidParams, 429 → RateLimited, etc.) with upstream messages surfaced
- Timeout-aware request retries and cancellation support via
AbortSignal
Getting Started
Public Hosted Instance
A public instance is available at https://openalex.caseyjhand.com/mcp — no installation required. Point any MCP client at it via Streamable HTTP:
{
"mcpServers": {
"openalex-mcp-server": {
"type": "streamable-http",
"url": "https://openalex.caseyjhand.com/mcp"
}
}
}
Self-Hosted / Local
Add to your MCP client config (e.g., claude_desktop_config.json):
{
"mcpServers": {
"openalex-mcp-server": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@cyanheads/openalex-mcp-server"],
"env": {
"OPENALEX_API_KEY": "your-email@example.com"
}
}
}
}
No API key needed — just provide your email to access the polite pool (10x faster rate limits).
Prerequisites
- Bun v1.3.0 or higher (for development)
Installation
- Clone the repository:
git clone https://github.com/cyanheads/openalex-mcp-server.git
- Navigate into the directory:
cd openalex-mcp-server
- Install dependencies:
bun install
Configuration
| Variable | Description | Default |
|---|---|---|
OPENALEX_API_KEY |
Optional. Email address for the OpenAlex polite pool (10x faster rate limits). Without it, anonymous rate limits apply. | — |
OPENALEX_BASE_URL |
OpenAlex API base URL. | https://api.openalex.org |
MCP_TRANSPORT_TYPE |
Transport: stdio or http. |
stdio |
MCP_HTTP_PORT |
Port for HTTP server. | 3010 |
MCP_AUTH_MODE |
Auth mode: none, jwt, or oauth. |
none |
MCP_ALLOWED_ORIGINS |
Comma-separated allow-list of browser Origin headers for HTTP transport. Unset = loopback-only; set to * to disable. |
loopback only |
MCP_LOG_LEVEL |
Log level (RFC 5424). | debug |
LOGS_DIR |
Directory for log files (Node.js only). | <project-root>/logs |
OTEL_ENABLED |
Enable OpenTelemetry instrumentation (spans, metrics, completion logs). | false |
Running the Server
Local Development
-
Build and run the production version:
bun run build bun run start:http # or start:stdio -
Run checks and tests:
bun run devcheck # Lints, formats, type-checks bun run test # Runs test suite
Docker
docker build -t openalex-mcp-server .
docker run -e OPENALEX_API_KEY=your-key -p 3010:3010 openalex-mcp-server
Project Structure
| Directory | Purpose |
|---|---|
src/mcp-server/tools/definitions/ |
Tool definitions (*.tool.ts). |
src/mcp-server/prompts/definitions/ |
Prompt definitions (*.prompt.ts). |
src/services/openalex/ |
OpenAlex API client service and domain types. |
src/config/ |
Environment variable parsing and validation with Zod. |
tests/ |
Unit and integration tests, mirroring the src/ structure. |
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 logging,ctx.statefor storage - Always resolve names to IDs via
openalex_resolve_namebefore using them in filters
Contributing
Issues and pull requests are welcome. Run checks before submitting:
bun run devcheck
bun run test
License
Apache-2.0 — see LICENSE for details.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.