Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@CORE Research MCP Find open-access papers on CRISPR gene editing from the last year"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
CORE Research MCP — wraps CORE API (api.core.ac.uk/v3)
Part of Pipeworx — an MCP gateway connecting AI agents to 1573+ live data sources.
Tool | Description |
| Search open-access research papers by keyword (e.g., "machine learning healthcare"). Returns titles, authors, abstracts, DOIs, and download links. Useful for literature reviews and finding academic sources. |
| Get full metadata for a research paper by its CORE ID. Returns title, authors, abstract, full text link, DOI, publisher, year, and citation count. |
Related MCP server: arXiv Search MCP Server
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"core-research": {
"url": "https://gateway.pipeworx.io/core-research/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/core-research/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1573+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"core-research": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-core-research"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-core-researchIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Core Research data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Search arXiv, fetch paper metadata, and read full-text content.
Search and download academic papers from arXiv, PubMed, bioRxiv, medRxiv, Google Scholar, Semantic…
Federated search of books and papers, BibTeX/RIS citations, open-access retrieval and reading.
Search PubMed/Europe PMC, fetch articles and full text (PMC/EPMC/Unpaywall), citations, MeSH terms.
