ChatGPT
A custom connector, with a caveat about which mode you are in.
Kind MCP client
Transport Remote MCP connector, added in Settings.
Config Settings → Connectors
Setup
- Open Settings → Connectors and add a custom connector.
- Give it the URL below and your key as an x-api-key header.
- Enable it for the conversation or workspace you want it in.
- Ask a question that needs current reporting.
https://api.unzoi.com/mcp
x-api-key: nai_your_key_hereWhat differs here
- Custom connector availability differs by plan and by workspace, and the setting has moved more than once. If you cannot find it, check OpenAI’s current documentation rather than assuming the endpoint is wrong — it answers the MCP Inspector fine, which is the quick way to tell the two apart.
- Deep research has historically expected connectors to expose specific search and fetch tools. This server exposes a news-specific tool surface instead, so it is most reliable as a general connector in a normal conversation.
- ChatGPT tends to call a tool once and work from that result, so bias it toward list_stories in your prompt — a single clustered call carries far more ground per result than a single article search.
Next
- Get a key at console.unzoi.com, if you have not.
- The tool reference — what the model is reading when it chooses between the six tools.
- Stories for context windows — the one habit that most changes how well an agent works against this API.
- Limits — an agent that loops can spend a monthly quota faster than you expect.
- ChatGPT's own MCP documentation — authoritative for anything about the client itself, including config paths, which move.
Endpoint, for copying: https://api.unzoi.com/mcp