Press Monitor Wikidata NewsFlow MCP Server — Usage Guide

This guide shows how to call the MCP tools that mirror the News-Wikidata API endpoints. Ideal for AI agents and automations using JSON-RPC.

MCP Base URL

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

Authentication

All MCP calls require:

Authorization: Bearer YOUR_API_KEY

MCP Configuration Example (mcp.json)

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

---

List Available Tools

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

---

Invoke a Tool - Example

1) news_headlines

curl -s -X POST "https://mcp.pressmonitor.com/news-wikidata/v1" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_SECRET_KEY:SUBSCRIPTION_ID" -d '{ "jsonrpc":"2.0", "id": 1, "method":"tools/call", "params":{ "name":"news_headlines", "arguments": { "wikidata_id": "Q90", "count": 10, "sort": "latest" } } }'

2) news_fulltext_metadata_translated

curl -s -X POST "https://mcp.pressmonitor.com/news-wikidata/v1" -H "Content-Type: application/json" -H "Authorization: Bearer YOUR_SECRET_KEY:SUBSCRIPTION_ID" -d '{ "jsonrpc":"2.0", "id": 2, "method":"tools/call", "params":{ "name":"news_fulltext_metadata_translated", "arguments": { "wikidata_id": "Q90", "target_lang_code": "en", "count": 5 } } }'

Result Envelope (typical)

MCP responses embed tool output in a JSON-RPC envelope:

{ "jsonrpc": "2.0", "id": 1, "result": { "content": [{ "type": "json", "json": { "items": [ /* array of story objects */ ], "credits": { /* rate, quantity, total, request_id */ }, "next": { /* search_after, count, sort */ } } }] } }

Tool → Endpoint Mapping & Arguments

Each tool corresponds 1:1 with an API route and accepts the same arguments.

1. news_headlines → GET /news-headlines Args: wikidata_id (required), country_code, lang_code, count, sort, search_after

2. news_briefs → GET /news-briefs Args: same as above

3. news_fulltext → GET /news-fulltext Args: same as above

4. news_fulltext_metadata → GET /news-fulltext-metadata Args: same as above

5. news_headlines_translated → GET /news-headlines-translated Args: wikidata_id (required), target_lang_code (required), plus country_code, lang_code, count, sort, search_after

6. news_briefs_translated → GET /news-briefs-translated Args: as above (items include a tr translation block)

7. news_fulltext_translated → GET /news-fulltext-translated Args: as above (items include tr)

8. news_fulltext_metadata_translated → GET /news-fulltext-metadata-translated Args: as above (items include tr)

Tips

• Use sort=latest for polling + next.search_after to page forward efficiently.
• For multilingual workflows, prefer the translated tools and store both original fields and the tr.* translations.
• Headlines/briefs are cost-effective for monitoring; fulltext/metadata are ideal for analytics and model finetuning.

---

Support

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

Email: support@pressmonitor.com