Press Monitor Wikidata MCP Server — Usage Guide

The Wikidata MCP Server mirrors the REST API with JSON-RPC tools designed for AI agents and automations. Tool names align with the OpenAPI operationId fields.

---

Base URL

https://mcp.pressmonitor.com/wikidata/v1

---

Authentication

All MCP calls require:

Authorization: Bearer YOUR_API_KEY

---

MCP Configuration Example (mcp.json)

{ "mcpServers": { "wikidata": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.pressmonitor.com/wikidata/v1", "--header", "Authorization: Bearer ${WIKIDATA_API_TOKEN}" ], "env": { "WIKIDATA_API_TOKEN": "" } } } }

---

List Available Tools

curl -s -X POST "https://mcp.pressmonitor.com/wikidata/v1" -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

---

Tool Names & Arguments (mapped to REST)

Below tools correspond to all API paths:

1. search_entities_by_label → /search/by-label
   Args: query_text (required), lang_code, limit, offset

2. search_entities_by_description → /search/by-description
   Args: query_text (required), lang_code, limit, offset

3. search_entities_by_claim_value → /search/by-claim
   Args: property (required), value, mode (exact|prefix|fulltext), lang_code, limit, offset

4. suggest_entities → /suggest-entities
   Args: query_text (required), lang_code, limit, offset

5. search_entities_by_type → /search/by-type
   Args: type (Q-id, required), query_text (optional), lang_code, limit, offset

6. search_entities_by_property → /find/by-property
   Args: property (required), value, qualifier, rank, lang_code, limit, offset

7. search_entities_by_date_range → /search/temporal
   Args: property, from, to, value, lang_code, limit, offset

8. get_entity_by_id → /entities/{id}
   Args: id (Q-id, required), lang_code

9. get_entity_claims → /entities/{id}/claims
   Args: id (Q-id, required), lang_code, limit, offset

10. get_properties → /properties
    Args: (none)

---

Invoke a Tool - Example: Web Search

search_entities_by_label

curl -s -X POST "https://mcp.pressmonitor.com/wikidata/v1" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY" -d '{ "jsonrpc":"2.0", "id": 1, "method":"tools/call", "params":{ "name":"search_entities_by_label", "arguments": { "query_text": "Paris", "lang_code":"en", "limit": 10 } } }'

search_entities_by_claim_value

curl -s -X POST "https://mcp.pressmonitor.com/wikidata/v1" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY" -d '{ "jsonrpc":"2.0", "id": 2, "method":"tools/call", "params":{ "name":"search_entities_by_claim_value", "arguments": { "property":"P17", "value":"Q142", "mode":"exact", "limit": 20 } } }'

get_entity_by_id

curl -s -X POST "https://mcp.pressmonitor.com/wikidata/v1" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_API_KEY" -d '{ "jsonrpc":"2.0", "id": 3, "method":"tools/call", "params":{ "name":"get_entity_by_id", "arguments": { "id":"Q90", "lang_code":"en" } } }'

Result Envelope

MCP responses embed tool outputs in a JSON-RPC envelope. A typical success looks like:

{ "jsonrpc": "2.0", "id": 1, "result": { "content": [{ "type": "json", "json": { "data": [ /* results */ ], "meta": { /* search/claim metadata, totals, took, etc. */ } } }] } }

Best Practices

• Begin with label and description tools for discovery; refine with claim / property tools for graph-precise results.
• Keep limit between 10–50 for interactive usage; increase for batch workflows.
• Cache frequent /entities/{id} and /properties calls to minimize latency and cost.

---

Support

Docs: https://www.pressmonitor.com/en/docs/wikidata-api-mcp

Email: support@pressmonitor.com