Using this with Claude

Setup

1. Create a key on the free tier.
2. Add the server to your MCP configuration file.
3. Restart the client so it re-reads the config and registers the tools.
4. Ask a question that needs current reporting — the tool call is visible in the transcript.

Configuration:

{
  "mcpServers": {
    "unzoi": {
      "url": "https://api.unzoi.com/mcp/sse",
      "headers": { "x-api-key": "your-key" }
    }
  }
}

Tool selection is unusually reliable here

This client reads tool descriptions carefully and picks between similar tools better than most. In practice that means it will reach for story grouping when the question is about an event and article search when the question is about coverage, without being told to. That changes what you should put in your system prompt: you generally do not need to script which tool to use, and over-specifying tends to make things worse by overriding a judgement that was already correct.

Summarised results change what you should request

Long tool results get summarised rather than pasted wholesale into the reply, which interacts well with clustered stories and badly with raw article lists. A clustered result carries one item per event with its outlet list, so a summary of it preserves the useful structure. A list of forty near-identical articles summarises to a single sentence that throws away everything except the fact that there were forty of them.

Local versus remote

The server is hosted, so there is nothing to install and no local process to keep alive — you point the client at a URL and give it your key. That also means a team rollout is a config file rather than a deployment, and revoking access is revoking a key rather than chasing down machines. If your client only speaks stdio, any standard MCP HTTP proxy will bridge it.

Notes and the usual pitfall

• Tool descriptions are read carefully by this client, so it reliably picks story grouping over article search when the question is about an event rather than about coverage.
• Long result sets are summarised rather than dumped, which makes clustered results noticeably more useful than raw articles.

Watch for: Configuration is only read at startup. If the tools do not appear, the cause is almost always that the client was not restarted, not that the config is wrong.