Search and fetch Wikidata entities, execute SPARQL queries, and resolve external identifiers.
Search and fetch Wikidata entities, execute SPARQL queries, and resolve external identifiers. That is what the wikidata mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The server publishes 9 tools. What each one is for:
wikidata_search_entities — Search for items or properties by text query, returning QIDs/PIDs with labels, descriptions, and match metadatawikidata_get_entity — Fetch a full entity by QID or PID with optional field and language filteringwikidata_get_labels — Batch-resolve up to 50 QIDs or PIDs to human-readable labels and descriptionswikidata_get_statements — Fetch property claims for an entity with qualifier detail and QID label resolutionwikidata_get_sitelinks — Fetch Wikipedia and Wikimedia project article URLs for a Wikidata itemwikidata_sparql_query — Execute a SPARQL SELECT query against the Wikidata Query Servicewikidata_resolve_external_id — Look up a Wikidata entity by an external identifier (DOI, PubMed ID, ORCID, OpenAlex ID, etc.)Prerequisites — The Prerequisites tool exposed by this serverInstallation — The Installation tool exposed by this serverConfiguration is passed through the environment: MCP_TRANSPORT_TYPE, MCP_LOG_LEVEL, MCP_HTTP_ENDPOINT_PATH, MCP_PUBLIC_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Among the file and storage access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Wikidata's toolset — wikidata_search_entities, wikidata_get_entity, wikidata_get_labels and 6 more — is a fair guide to whether it matches your workflow. It is maintained by cyanheads; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Wikidata's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| wikidata_search_entities | Search for items or properties by text query, returning QIDs/PIDs with labels, descriptions, and match metadata |
| wikidata_get_entity | Fetch a full entity by QID or PID with optional field and language filtering |
| wikidata_get_labels | Batch-resolve up to 50 QIDs or PIDs to human-readable labels and descriptions |
| wikidata_get_statements | Fetch property claims for an entity with qualifier detail and QID label resolution |
| wikidata_get_sitelinks | Fetch Wikipedia and Wikimedia project article URLs for a Wikidata item |
| wikidata_sparql_query | Execute a SPARQL SELECT query against the Wikidata Query Service |
| wikidata_resolve_external_id | Look up a Wikidata entity by an external identifier (DOI, PubMed ID, ORCID, OpenAlex ID, etc.) |
| Prerequisites | The Prerequisites tool exposed by this server. |
| Installation | The Installation tool exposed by this server. |
{
"mcpServers": {
"wikidata-mcp-server": {
"type": "stdio",
"command": "bunx",
"args": ["@cyanheads/wikidata-mcp-server@latest"],
"env": {
"MCP_TRANSPORT_TYPE": "stdio",
"MCP_LOG_LEVEL": "info"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MCP_TRANSPORT_TYPE | Configuration value read at startup. | Optional |
| MCP_LOG_LEVEL | Configuration value read at startup. | Optional |
| MCP_HTTP_ENDPOINT_PATH | Filesystem location the server is allowed to use. | Optional |
| MCP_PUBLIC_URL | Endpoint or connection string the server talks to. | Yes |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.