The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Wikidata listing page.
Wikidata is the free, structured-data sister of Wikipedia. ~110 million items (people, places, works, concepts) with machine-readable properties and relationships. The closest thing the open web has to a universal knowledge graph. Free, no auth, supports SPARQL queries.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
For entity disambiguation, structured facts about anything notable, or graph traversal ("what books did this author write that won prizes?"), Wikidata is the canonical open source. Pair with Wikipedia (prose) and OpenAlex (academic specifics) for full open-knowledge coverage.
Common flows:
| Tool | What it returns |
|---|---|
search_entities | Q-ids matching a label or alias, with labels, descriptions and aliases. Start here when you have a name and need an id. |
get_entity | Full entity by Q-id — labels, descriptions, aliases, raw P-coded claims, sitelinks, plus lastrevid / modified. |
get_wikidata_facts | The same statements with property names and values resolved to human-readable labels, plus lastrevid / modified. Prefer this for "what is X's ". |
wikidata_recent_changes | Items created or edited most recently, newest-first, from list=recentchanges — Q-id, revision ids, UTC timestamp, user, comment, byte size, plus a cursor for paging further back. |
Wikidata is live and continuously edited, so "the current statements" is only meaningful
relative to a revision. Both entity tools return lastrevid, modified and a
revision_url, so an answer built from them can be pinned to the exact edit it was read
at, and re-checked later for drift.
wikidata_recent_changes answers the other half of that: which items changed, and when.
Namespace 0 is items (Q-ids), 120 is properties (P-ids), 146 is lexemes. type is
new (freshly created), edit (edits to existing items) or all. Use since for a time
window and cursor to page further back.
None. Wikidata is fully open. Wikidata's SPARQL endpoint has fair-use rate limits but generous for most agent traffic.
| Prefix | Type |
|---|---|
| Q | Item (an entity — person, place, thing) |
| P | Property (a relationship type — "spouse," "instance of," "located in") |
| L | Lexeme (a word/sense, for linguistic data) |
Every entity has a stable Q-number that serves as a permanent identifier across Wikipedia language editions. Embed Q-numbers in agent output as canonical citations.
references field on properties you're acting on.references chain to an authoritative source.en) when label is missing.https://www.wikidata.org/w/api.php
action=wbsearchentities (search), action=wbgetentities (entity read, props=info|labels|descriptions|aliases|claims|sitelinks)action=query&list=recentchanges (recent changes feed)https://www.wikidata.org/wiki/<QID>; a specific revision: https://www.wikidata.org/w/index.php?oldid=<revid>All endpoints are keyless. Wikidata asks callers to send a descriptive User-Agent; this
pack sends Pipeworx-Wikidata-MCP/1.0.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
tools/list at https://gateway.pipeworx.io/wikidata/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:
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:
The gateway picks the right tool and fills the arguments automatically.
MIT