# Dblp [Health: Active]

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

## Description
DBLP MCP — Computer Science bibliography

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

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

## Documentation

## What Dblp does

Dblp MCP server exposes search access to DBLP, a computer science bibliography containing approximately 7 million publications and 3 million authors. Its three domain-specific tools search publications, authors, and venues. Queries are sent to DBLP’s public search REST API, using JSON responses through the `format=json` option.

The integration is independent and unofficial. It is useful when an agent needs to find computer science literature, identify authors, or locate publication venues without handling DBLP’s HTTP API directly.

## How it works

The hosted connection is available at `https://gateway.pipeworx.io/dblp/mcp`. An MCP client can connect to that URL and discover the DBLP tools. The endpoint also exposes shared Pipeworx gateway tools, including routing and discovery functions, so its tool list contains more than the three DBLP-specific tools. The exact scope is reported by the connection’s `initialize` response.

The full Pipeworx gateway is available at `https://gateway.pipeworx.io/mcp` as an alternative. Both endpoints use the same gateway and data sources; the difference is which pack’s tools appear directly in the tool listing. The `ask_pipeworx` function can route natural-language questions to tools across the catalog.

For clients without MCP support, tool calls can be sent over HTTP. For example, publication searches use `POST https://gateway.pipeworx.io/v1/tools/dblp_search_publications` with a JSON body containing a `query` field. Tool details can be inspected with a `GET` request to the corresponding tool endpoint.

## Setup and configuration

For a hosted MCP connection, add the DBLP endpoint to an MCP client configuration. Claude Desktop, Cursor, and Windsurf are named as supported client choices. No account is needed for initial hosted calls.

A local stdio option is provided by the `@pipeworx/mcp-dblp` npm package. Configure the client to start it with `npx -y @pipeworx/mcp-dblp`. The bridge forwards requests to the hosted Pipeworx endpoint, so it requires network access and has no offline mode.

Anonymous use of the npm bridge is limited to 50 calls per day. A free Pipeworx account and `PIPEWORX_API_KEY` raise the allowance to 200 calls per day. The key is sent as a Bearer token. Set `PIPEWORX_META_TOOLS=1` if the local bridge should also list the shared gateway tools; otherwise, it lists the DBLP pack tools only.

When running behind an HTTPS proxy, Node’s `fetch` does not automatically read `HTTPS_PROXY` in all versions. Newer Node releases can use proxy environment settings when `NODE_USE_ENV_PROXY=1` is enabled.

## Tools and capabilities

- `search_publications(query, format?, hits?, first?)` searches DBLP publication records.
- `search_authors(query, format?, hits?, first?)` searches DBLP author records.
- `search_venues(query, format?, hits?, first?)` searches publication venues.

The optional `format`, `hits`, and `first` arguments control response format, result count, and the starting position for each search. The underlying data source is `https://dblp.org/search/`.

## Limitations and notes

This integration depends on network access to the Pipeworx gateway and DBLP’s public service. It does not provide an offline mode. The npm bridge’s usage limits differ between anonymous and authenticated calls, and authenticated requests are metered through Pipeworx. The integration is unofficial and is not affiliated with, endorsed by, or published by DBLP.

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