MCP Wikidata Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WIKIDATA_TIMEOUT | No | Request timeout in seconds | 30 |
| WIKIDATA_CACHE_TTL | No | Cache TTL in seconds | 3600 |
| WIKIDATA_RATE_LIMIT | No | Request rate limit (per minute) | 60 |
| WIKIDATA_USER_AGENT | No | User-Agent for API requests | MCP-Wikidata/0.1.0 |
| WIKIDATA_MAX_RESULTS | No | Maximum number of results per query | 50 |
| WIKIDATA_DEFAULT_LANGUAGE | No | Default language | en |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_entitiesB | Search for entities in Wikidata by text query |
| get_entityB | Get detailed information about a Wikidata entity |
| sparql_queryC | Execute a SPARQL query against Wikidata |
| get_relationsC | Get relations of a Wikidata entity |
| find_by_propertyC | Find entities by property and value |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: find_by_property targets property-value pairs, get_entity retrieves entity details, get_relations focuses on entity relationships, search_entities handles text-based queries, and sparql_query allows custom SPARQL queries. The descriptions reinforce these distinct roles, making tool selection unambiguous.
All tool names follow a consistent verb_noun pattern (e.g., find_by_property, get_entity, get_relations, search_entities, sparql_query), using snake_case uniformly. The verbs (find, get, search, execute) are appropriate to their actions, creating a predictable and readable naming convention throughout the set.
With 5 tools, this server is well-scoped for interacting with Wikidata, covering essential operations like entity retrieval, searching, and querying without being overly complex. Each tool earns its place by addressing a core need in the domain, making the count appropriate for the server's purpose.
The tool surface provides strong coverage for querying and retrieving Wikidata data, including basic CRUD-like operations (e.g., get and search) and advanced querying via SPARQL. A minor gap exists in write operations (e.g., create or update entities), but agents can work around this given Wikidata's read-heavy nature, and the tools support most common workflows.