Opencitations vs Next Devtools MCP

A side-by-side look at the Opencitations and Next Devtools MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Opencitations logoOpencitationsResearch · Local subprocess (stdio)OpenCitations COCI — open-license citation index by DOI59GoodAuth: not declaredNext Devtools MCP logoNext Devtools MCPDeveloper Tools · Local subprocess (stdio)Official Next.js MCP server for coding agents. Provides runtime diagnostics, route inspection, dev server logs, docs search, and upgrade guides. Requires Next.js 16+ dev server for full runtime features.86ExcellentAuth: no auth required

Verdict: choose Opencitations for research work as a local process; choose Next Devtools MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Opencitations logoChoose Opencitations when

  • You need dedicated capabilities in the Research domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like references, citations, citation_count.
Explore Opencitations

Next Devtools MCP logoChoose Next Devtools MCP when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like nextjs_index, nextjs_call, nextjs_docs.
Explore Next Devtools MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecOpencitations logoOpencitationsNext Devtools MCP logoNext Devtools MCP
CategoryResearchDeveloper Tools
Quality signal59/100 · Good86/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars0832
Directory activity 1 views 0 installs 0 upvotes 9 views 0 installs 1 upvotes
Tools64

Tools & capabilities

Opencitations tools 6

  • references"What does paper [DOI] cite" / "references in [paper]" / "what sources does this paper use" — DOIs cited BY the given DOI (the paper's reference list / bibliography). Use for citation-graph traversal, literature review, source tracking.
  • citations"Who cites paper [DOI]" / "what papers reference [DOI]" / "incoming citations to [paper]" / "what work has cited [study]" — DOIs that CITE the given DOI (reverse-direction from references). Use for impact analysis, follow-on research discovery, "is this paper influential" questions.
  • citation_count"How many times has paper [DOI] been cited" / "citation count for [paper]" / "is [study] highly cited" — incoming citation count for a DOI. Fast version of `citations` when you only need the number, not the citing DOIs.
  • references_count"How many references does paper [DOI] have" / "how big is the bibliography of [paper]" — outgoing reference count for a DOI. Fast version of `references` when you only need the number.
  • metadata"Get paper info for [DOI]" / "bibliographic details for [paper]" / "title / authors / year of [DOI]" — bibliographic metadata for one or more DOIs (up to 50 at once). Returns title, authors, year, journal, publisher.
  • citationFetch one citation record by its Open Citation Identifier (OCI — a compound ID of the form citing-DOI__cited-DOI). Returns citing/cited DOI pair, creation date, and journal self-citation flag. Use `citations` or `references` instead when you only have a DOI.

Next Devtools MCP tools 4

  • nextjs_indexDiscover running Next.js dev servers and list each one's runtime MCP tools.
  • nextjs_callCall a runtime tool on a discovered server (errors, routes, logs, Server Actions).
  • nextjs_docsGateway.** Point the agent at version-accurate docs in `node_modules/next/dist/docs/`.
  • browser_evalGateway.** Point the agent at the [`agent-browser`](https://github.com/vercel-labs/agent-browser) CLI for browser automation.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Opencitations

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "opencitations": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-opencitations"
      ]
    }
  }
}

Next Devtools MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vercel-next-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "next-devtools-mcp@latest"
      ]
    }
  }
}

Frequently asked questions

Opencitations is categorized under Research and uses a local stdio subprocess. Next Devtools MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Opencitations for research work and Next Devtools MCP for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Opencitations has no declared pricing — check the project's own site. Next Devtools MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add opencitations and vercel-next-devtools-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Opencitations has a quality signal of 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Next Devtools MCP has 86/100 (Excellent) with 9 views, 0 installs and 832 GitHub stars.