mcp-osf
Provides tools for searching and retrieving public research data from the Open Science Framework (OSF), including searching public projects ("nodes") by title to get id, title, description, category, creation date and tags, fetching a single project's metadata by its OSF id, and searching public preprints by title to get id, title, description, publication date, DOI and tags.
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., "@mcp-osfsearch OSF for preprints about CRISPR gene editing"
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.
mcp-osf
OSF (Open Science Framework, by the Center for Open Science) MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Tools
Tool | Description |
| OSF (Open Science Framework, by the Center for Open Science): search public research projects ("nodes") by title. Returns id, title, description, category, creation date, and tags. Keyless public data; the API can be slow. |
| OSF: fetch metadata for a single public research project (node) by its OSF id (e.g. "abc12"). Returns title, description, category, dates, tags, and public flag. |
| DEPRECATED ALIAS for osf_search_preprints — identical behavior, kept for existing callers. New callers should use osf_search_preprints. |
| OSF: search public preprints by title (Open Science Framework, by the Center for Open Science). Returns id, title, description, publication date, DOI, and tags. Keyless public data; the API can be slow. |
Related MCP server: mcp-openaire
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"osf": {
"url": "https://gateway.pipeworx.io/osf/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/osf/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 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/osf_search_projects \
-H 'Content-Type: application/json' \
-d '{"query":"climate change"}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/osf_search_projects. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"osf": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-osf"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-osfIt 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.
Using with ask_pipeworx
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 Osf data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
A public commons for agents to search and share reusable findings and open research questions.
Open scientific and engineering knowledge for AI agents: search, evidence, document publishing.
Search peer-reviewed papers and research methodology guidance from your AI agent.
Scholarly search: OpenAlex, Crossref, arXiv, OpenCitations and PubMed in one endpoint.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to search academic literature and retrieve detailed metadata for papers, journals, and funding organizations via the Crossref database. It supports DOI-based lookups and keyword searches to facilitate programmatic access to scholarly research data.7-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search and retrieve EU research outputs including publications, datasets, software, and funded projects from OpenAIRE.182 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables querying bioRxiv and medRxiv preprints, including metadata, publication status, and submission counts, through natural language or direct tool calls.148 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search scholarly works, authors, institutions, venues, and concepts, retrieve detailed metadata, and explore citation networks through natural-language requests.151 npmMIT