About Wikidata Sparql
Wikidata Sparql is an MCP server for querying Wikidata’s knowledge graph with SPARQL. It also provides convenience tools for class instances, subclasses, entity properties, and nearby geographic items.
Key features
- 01Run SPARQL queries
- 02List instances of a class
- 03Explore subclass trees
- 04Retrieve entity statements
- 05Find nearby geographic items
Use cases
- 01Query Wikidata for structured facts
- 02Explore class instances and subclasses
- 03Inspect statements about an entity
- 04Find Wikidata items near coordinates
MCP support
Exposes SPARQL querying and helper tools for Wikidata to MCP clients. It can connect through the Pipeworx gateway or run locally as a stdio MCP server.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://gateway.pipeworx.io/wikidata-sparql/mcpclaude mcp add --transport http pipeworx-io-wikidata-sparql https://gateway.pipeworx.io/wikidata-sparql/mcp{"mcpServers":{"pipeworx-io-wikidata-sparql":{"type":"http","url":"https://gateway.pipeworx.io/wikidata-sparql/mcp"}}}Open in Cursor{"servers":{"pipeworx-io-wikidata-sparql":{"type":"http","url":"https://gateway.pipeworx.io/wikidata-sparql/mcp"}}}Open in VS Code{"mcpServers":{"pipeworx-io-wikidata-sparql":{"type":"http","url":"https://gateway.pipeworx.io/wikidata-sparql/mcp"}}}{"mcpServers":{"pipeworx-io-wikidata-sparql":{"serverUrl":"https://gateway.pipeworx.io/wikidata-sparql/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
47| Parameter | Type | Required | Description |
|---|---|---|---|
| q | string | No | Alias for question. |
| ask | string | No | Alias for question. |
| text | string | No | Alias for question. |
| input | string | No | Alias for question. |
| packs | array | No | OPTIONAL. Restrict routing to these pack slugs (e.g. ["sec-form-d","sec-13f"]) — the router then picks only from tools in those packs. Omit for the default full-catalog routing. Slugs come from list_packs / search_packs / https://pipeworx.io/directory; unlisted or unknown slugs are ignored and named in _meta.pack_scope.ignored, and if none of them resolves the question is routed across the whole catalog with _meta.pack_scope.full_catalog:true (never an empty answer). |
| query | string | No | Alias for question. |
| prompt | string | No | Alias for question. |
| message | string | No | Alias for question. |
| question | string | Yes | Your question or request in natural language. Accepts query, q, prompt, text, input, ask, message as aliases. |
Details
From the project README@pipeworx/wikidata-sparql
Wikidata Query Service MCP — full SPARQL access to the entire Wikidata knowledge graph (~100M items, 1.5B statements). Complements the existing wikidata pack (which covers entity search + retrieval).
Part of Pipeworx — an MCP gateway connecting AI agents to 1684+ live data sources.
Tools
query(sparql, format?)— run a SPARQL queryinstances_of(entity_id, limit?)— convenience: all instances of a class (e.g. Q5 = humans)subclasses_of(entity_id, limit?)— convenience: subclass treeproperties_of(entity_id, limit?)— convenience: statements about an entityentities_at(latitude, longitude, radius_km?, instance_of?, limit?)— geo-spatial query: items near a point
No auth
The public WDQS at https://query.wikidata.org/sparql is keyless. Fair-use: ≤30 queries / min, ≤60 sec timeout per query. The pack sets a meaningful User-Agent (required by WMF policy).
Tips
Wikidata is enormous — narrow your queries! Use LIMIT, instance of filters, and language tags. Bring schema knowledge from https://www.wikidata.org/wiki/Wikidata:List_of_properties.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"wikidata-sparql": {
"url": "https://gateway.pipeworx.io/wikidata-sparql/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/wikidata-sparql/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 1684+ 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/wikidata_sparql_query \
-H 'Content-Type: application/json' \
-d '{"sparql":"SELECT ?item ?itemLabel WHERE { ?item wdt:P31 wd:Q5 . SERVICE wikibase:label { bd:serviceParam wikibase:language \"en\" } } LIMIT 10"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/wikidata_sparql_query. 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": {
"wikidata-sparql": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-wikidata-sparql"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-wikidata-sparql
It 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 Wikidata Sparql data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.