A side-by-side look at the Openalex and OpenAlex MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Openalex for research work as a local process; choose OpenAlex for research. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Openalex when
You need dedicated capabilities in the Research domain.
No tool names declared yet. Check the project README from the listing page.
OpenAlex tools
No tool names declared yet. Check the project README from the listing page.
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.
No confirmed install command for OpenAlex yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Openalex is categorized under Research and uses a local stdio subprocess. OpenAlex belongs to Research and uses an install path we have not confirmed yet. Pick Openalex for research work and OpenAlex for research.
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. OpenAlex has no confirmed install command yet — follow its own setup instructions.
Openalex has no declared pricing — check the project's own site. OpenAlex is listed as free. Auth: oauth 2.0. 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 openalex and openalex-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Openalex has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. OpenAlex has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.