# Openaire [Health: Active]

**Category:** 🔬 Research  
**Repository:** https://github.com/pipeworx-io/mcp-openaire  
**GitHub Stars:** 0  
**npm Downloads (last month):** 125  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/openaire

## Description
OpenAIRE MCP — EU research outputs (publications, datasets, software, projects)

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "openaire": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-openaire"]
  }
}
```

## Documentation

## What Openaire MCP server does

Openaire provides MCP access to OpenAIRE's public Graph API at `https://api.openaire.eu/graph/v1/`. Its focus is research discovery across publications, datasets, software, and projects, including outputs associated with programs such as Horizon Europe and FP7. The integration is independent and unofficial; it is not affiliated with or endorsed by OpenAIRE.

Searches can use filters such as funder, country, year, result size, and page number where supported. Funder examples include the European Commission, NIH, Wellcome Trust, and NSF codes.

## How it works

The hosted option uses a streamable MCP endpoint:

```json
{
  "mcpServers": {
    "openaire": {
      "url": "https://gateway.pipeworx.io/openaire/mcp"
    }
  }
}
```

This scoped gateway endpoint lists Openaire's tools together with shared Pipeworx meta-tools. Those shared tools include `ask_pipeworx`, which can route questions across the wider Pipeworx catalog, along with discovery and memory tools. The endpoint's `initialize` response defines the exact tool scope available at connection time.

A full Pipeworx gateway connection is also available at `https://gateway.pipeworx.io/mcp`. Both hosted URLs use the same gateway and data sources; the pack endpoint lists Openaire tools directly, while the full gateway lists tools from all packs directly.

## Setup and configuration

For a local installation, run the package as an MCP stdio server:

```json
{
  "mcpServers": {
    "openaire": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-openaire"]
    }
  }
}
```

Running `npx -y @pipeworx/mcp-openaire` starts the server directly. The local process communicates over standard input and output, exposes only the Openaire tools, and does not require a Pipeworx account or gateway round trip.

Without an MCP client, hosted tools can also be called through HTTP. For example, tool requests use endpoints under `https://gateway.pipeworx.io/v1/tools/`, and tool schemas can be inspected with a `GET` request to the corresponding tool URL.

## Tools and capabilities

The Openaire-specific tools are:

- `search_publications` — find publications, with optional funder, country, year, page, and size parameters.
- `search_datasets` — search datasets with pagination controls.
- `search_projects` — find projects with optional funder, country, year, page, and size parameters.
- `search_software` — search research software with pagination controls.
- `get_publication` — retrieve a publication by ID.
- `get_project` — retrieve a project by ID.

The gateway's `ask_pipeworx` tool can accept a plain-language question and select and populate a suitable tool across the catalog. That routing capability is available through the hosted gateway connection, not the standalone local process.

## Limitations and notes

Openaire reads from a public JSON API and has no authentication requirement for the described gateway calls. The hosted pack endpoint includes shared gateway tools in addition to the six Openaire-specific tools, which increases the tool list and context size. The standalone package avoids those shared tools but is limited to this pack's capabilities. The integration is an unofficial Pipeworx connection rather than an OpenAIRE-published server.

_Full upstream README: https://allmcps.com/mcp/openaire/readme_