# Doaj [Health: Active]

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

## Description
DOAJ MCP — Directory of Open Access Journals

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

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

## Documentation

## What the Doaj MCP server does

The Doaj MCP server exposes the Directory of Open Access Journals as tools for an MCP-compatible AI client. DOAJ is a curated index of peer-reviewed open-access journals, so the server is suited to finding article and journal records rather than querying a private library or subscription database.

The available article operations include keyword or field-based searches and retrieval of a specific article by ID. Journal operations provide the equivalent search and record lookup functions for journals. Search requests support optional page, page-size, and sort parameters. The underlying data comes from DOAJ’s public API, which does not require an API key.

## How it works

A client can connect to the hosted MCP endpoint at `https://gateway.pipeworx.io/doaj/mcp`. That endpoint exposes the Doaj pack’s four tools along with shared Pipeworx gateway tools. The shared tools can route broader questions across the Pipeworx catalog, while direct calls to the pack tools remain focused on DOAJ data.

The same gateway also provides an HTTP tool interface. For example, an HTTP client can send a JSON POST request to the article-search tool endpoint rather than using an MCP client. The gateway documentation also exposes tool inspection and pack-search endpoints.

For an isolated connection, run the package locally over standard input and output. The local process answers MCP initialization, tool-listing, and tool-call requests for the Doaj pack only. It does not add the gateway’s shared meta-tools or its cross-catalog routing behavior.

## Setup and configuration

The Doaj MCP server can be configured in an MCP client with the hosted URL, or launched with `npx -y @pipeworx/mcp-doaj` as a local stdio process. The local option does not require a Pipeworx account and avoids a gateway round trip.

Claude Desktop, Cursor, and Windsurf are named as supported client choices. A hosted configuration points the client at the Doaj MCP endpoint; a local configuration uses `npx` as the command and `-y`, followed by the package name, as its arguments.

## Tools and capabilities

The Doaj MCP server includes these pack-specific tools:

- `search_articles(query, page?, page_size?, sort?)` searches indexed article records.
- `search_journals(query, page?, page_size?, sort?)` searches indexed journal records.
- `get_article(id)` retrieves an article record by identifier.
- `get_journal(id)` retrieves a journal record by identifier.

On the hosted gateway connection, `tools/list` also returns shared Pipeworx tools such as `ask_pipeworx`, `discover_tools`, `search_within`, and `remember` or `recall`. The exact gateway tool scope can change, so the connection’s `initialize` response is authoritative.

## Limitations and notes

The Doaj MCP server is limited to the records and behavior exposed by the DOAJ API.

Hosted pack connections include shared gateway schemas by design; they cannot currently be mounted without those additional tools. Choose the local package when only the four DOAJ tools are needed, or use the full Pipeworx gateway when direct access to all catalog packs is preferable. The project is released under the MIT license.

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