CiteNexus MCP

Scholarly discovery and citations with evidence you can trace.

CiteNexus connects research assistants to open scholarly metadata, specialist academic indexes, and optional commercial databases through the Model Context Protocol. Search without an API key, resolve stable identifiers, check references against their sources, and export citations without asking a language model to invent the missing fields.

This is a citation and metadata service for the assistant you already use. It works alongside reference managers such as Zotero and writing environments that support MCP.

CiteNexus 0.2.3 includes the MCP service and the cite-nexus-wtfp companion. The WTF-P integration targets its separate 0.7.0 release. Marketplace listings and native client plugin qualification are tracked independently.

Quick start · WTF-P integration · Provider guide · Troubleshooting · Release information

• Useful without credentials: Crossref, DataCite and Europe PMC are the default search sources. arXiv and Semantic Scholar are also available without mandatory keys.
• Optional specialist and commercial access: OpenAlex, Google Scholar through SerpAPI or SearchApi, Scopus and Web of Science Starter have explicit configuration and provider selection.
• Source-backed records: namespaced identifiers, retrieval timestamps, field attribution, incomplete-author warnings and provider-specific citation counts.
• Deterministic export: BibTeX, RIS and CSL-JSON from retrieved metadata. No model is required.
• Current MCP: Python SDK 2.2, the 2026-07-28 specification, structured tool results, resources, prompts, progress, stdio and Streamable HTTP. Earlier clients remain supported by the SDK's legacy protocol path.

Quick start

Python 3.11+ and uv are required.

uvx --from cite-nexus-mcp==0.2.3 cite-nexus-mcp --version
uvx --from cite-nexus-mcp==0.2.3 cite-nexus-mcp --no-env-file --list-providers

For an MCP client with a mcpServers configuration:

{
  "mcpServers": {
    "cite-nexus": {
      "command": "uvx",
      "args": ["--from", "cite-nexus-mcp==0.2.3", "cite-nexus-mcp", "--no-env-file"]
    }
  }
}

The client starts MCP over stdio. No API key or .env file is required. Running the server command directly waits for a client; it is not an interactive search shell. If your client cannot find uvx, use its absolute executable path. The first run downloads the package and its dependencies.

For a persistent installation, including the WTF-P companion:

uv tool install cite-nexus-mcp==0.2.3
cite-nexus-wtfp --check

The diagnostic starts the actual MCP service and lists providers without querying vendor APIs. See the WTF-P setup for the separate integration and executable-path setting.

For local HTTP clients:

uvx --from cite-nexus-mcp==0.2.3 cite-nexus-mcp --no-env-file --transport streamable-http --port 8000

Connect to http://127.0.0.1:8000/mcp. The CLI binds only to loopback and serves a single trust boundary. A public, multi-user deployment needs authentication, credential isolation and its own deployment integration; the CLI does not supply those features.

Sources and access

find-open-access can additionally enrich DOI records with Unpaywall when UNPAYWALL_EMAIL is configured. It returns reported legal OA locations and licensing information; it does not download PDFs or bypass access restrictions.

Free access is subject to provider rate limits and terms. Anonymous Semantic Scholar can be heavily throttled. OpenAlex access policies have changed over time; CiteNexus requires a key for that adapter even when an anonymous request happens to succeed. Institution keys do not by themselves guarantee subscription access or access outside an institution's network.

Commercial and metered adapters are called only when selected explicitly, when resolving their own namespaced IDs, or when deliberately configured as search defaults. Setting a key alone does not add a vendor to default searches. list-providers reports configuration, capabilities and documentation links without testing access or revealing key values.

Research workflows

Use CiteNexus to build a literature shortlist, repair an uncertain reference, check the source behind a citation count, or prepare a bibliography for your writing tool. For a full writing workflow, the WTF-P companion connects discovery to evidence tables, outlines and manuscript work while keeping candidate references visible for review.

Ask your assistant to use the tools directly, or start with the literature-review and bibliography-audit MCP prompts. Example tool arguments:

{"query": "reproducible machine learning benchmarks", "providers": ["crossref", "arxiv"], "limit": 5}

{"identifier": "10.1038/nature14539", "format": "bibtex"}

{"citation": "10.1038/nature14539", "expected_title": "Deep learning", "expected_year": 2015}

{"identifier": "PMID:26017442", "direction": "references", "provider": "europe_pmc", "limit": 10}

{"identifiers": ["10.1038/nature14539", "arxiv:1706.03762"], "format": "csl-json"}

search-papers defaults to 10 results per provider, not 10 overall. Results interleave each provider's ranking, then merge compatible records. limit is 1–50, or at most 20 when using SerpAPI or SearchApi. Use each provider's next_offsets with the same limit, selecting that provider for the next call. Europe PMC search uses next_cursors instead: pass its token as cursor, select only europe_pmc, keep the same query and limit, and leave offset at zero. Offsets must be multiples of the limit, up to 10,000. year_from, year_to and open_access_only filter the fetched page; unknown values are excluded. Abstracts are omitted from search results by default; set include_abstract: true or resolve a record to retrieve them. Search records are compact by default: field_sources is empty while sources still names every provider. Set detail: "full" or resolve a record for per-field provenance. Provider search languages differ: explicit advanced queries use that provider's syntax.

Supported identifiers include 10.1038/nature14539, arxiv:1706.03762, PMID:26017442, PMC12345, openalex:W2919115771, s2:<paperId>, s2:CorpusId:<number>, scholar:<numericClusterId>, scopus:<numericId>, and WOS:<recordId>. DOI, arXiv and PubMed URLs are recognized. Arbitrary URLs are not fetched, and unprefixed numeric strings are not assumed to be PubMed or Scholar IDs.