Search scholarly sources, verify references, and export citations with traceable evidence.
To add CiteNexus to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It needs 8 environment variables, listed below.
Install
uvx cite-nexus-mcp@0.2.2Environment variables
CITE_NEXUS_CONTACT_EMAILSet in your MCP configSEMANTIC_SCHOLAR_API_KEYSet in your MCP configOPENALEX_API_KEYSet in your MCP configSERPAPI_API_KEYSet in your MCP configSCOPUS_API_KEYSet in your MCP configSCOPUS_INSTTOKENSet in your MCP configWOS_API_KEYSet in your MCP configUNPAYWALL_EMAILSet in your MCP configInstall with your client
claude mcp add citenexus --env CITE_NEXUS_CONTACT_EMAIL=<YOUR_CITE_NEXUS_CONTACT_EMAIL> --env SEMANTIC_SCHOLAR_API_KEY=<YOUR_SEMANTIC_SCHOLAR_API_KEY> --env OPENALEX_API_KEY=<YOUR_OPENALEX_API_KEY> --env SERPAPI_API_KEY=<YOUR_SERPAPI_API_KEY> --env SCOPUS_API_KEY=<YOUR_SCOPUS_API_KEY> --env SCOPUS_INSTTOKEN=<YOUR_SCOPUS_INSTTOKEN> --env WOS_API_KEY=<YOUR_WOS_API_KEY> --env UNPAYWALL_EMAIL=<YOUR_UNPAYWALL_EMAIL> -- uvx cite-nexus-mcp@0.2.2
Run this in a terminal to add the server to Claude Code.
What this does
CiteNexus exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.
Requirements
This server needs the following environment variables to be set before it can run:
CITE_NEXUS_CONTACT_EMAIL SEMANTIC_SCHOLAR_API_KEY OPENALEX_API_KEY SERPAPI_API_KEY SCOPUS_API_KEY SCOPUS_INSTTOKEN WOS_API_KEY UNPAYWALL_EMAIL
Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).
Frequently asked questions
How do I install CiteNexus?
Run the Claude Code command in the install section to add CiteNexus to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.
Which clients work with CiteNexus?
This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to CiteNexus as well.
Does CiteNexus need an API key?
Yes. Before it can run, set these environment variables: CITE_NEXUS_CONTACT_EMAIL, SEMANTIC_SCHOLAR_API_KEY, OPENALEX_API_KEY, SERPAPI_API_KEY, SCOPUS_API_KEY, SCOPUS_INSTTOKEN, WOS_API_KEY, UNPAYWALL_EMAIL. They go in the env block of your MCP config.
Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.
Is this your MCP server?
Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.
Add this badge to your README
Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.
[](https://clauderules.net/mcp/io-github-akougkas-cite-nexus-mcp)<a href="https://clauderules.net/mcp/io-github-akougkas-cite-nexus-mcp" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-akougkas-cite-nexus-mcp" alt="Listed on clauderules.net" /></a>More Search MCP servers
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Serena MCP: the IDE for your agent
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
mediar-ai/screenpipe
🎖️ 🦀 🏠 🍎 Local-first system capturing screen/audio with timestamped indexing, SQL/embedding storage, semantic search, LLM-powered history analysis, and event-triggered actions - enables building c
Figma-Context-MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.