
Connects Claude to the DBLP computer science bibliography via the Pipeworx gateway. Exposes two search operations: one for finding authors by name (returns canonical IDs, affiliations, and ORCID identifiers), and another for searching venues like conferences and journals. Useful when you need to look up publication metadata, verify author identities, or find where specific CS research was published. Runs over streamable HTTP, so no local setup required. Part of a larger Pipeworx gateway that bundles 250+ data sources, but you can connect to just the DBLP endpoint if that's all you need.
DBLP MCP — Computer Science bibliography (~7M publications, ~3M authors). No auth.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
search_publications(query, format?, hits?, first?)search_authors(query, format?, hits?, first?)search_venues(query, format?, hits?, first?)https://dblp.org/search/ — public REST API, returns JSON via format=json.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"dblp": {
"url": "https://gateway.pipeworx.io/dblp/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/dblp/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 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
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 Dblp data" })
The gateway picks the right tool and fills the arguments automatically.
MIT