APITube News

Overview

The APITube MCP server gives an assistant live access to the world's news as structured data, not scraped HTML. It exposes 2 tools:

• search_news — most of the News API filter set in one call: keywords, language, country, source domain and quality rank, sentiment range, named entities, media, date ranges, sorting, faceting and highlighting.
• suggest — resolves a name like "Tesla" into the entity, category, topic and industry IDs the precise filters need.

Every article comes back enriched by the pipeline behind it: sentiment scores, extracted entities (people, organizations, locations, brands, events), IPTC categories, topics and industries.

MCP client  →  mcp.apitube.io  →  api.apitube.io               (this server)      (News API)
JSON-RPC over HTTP, Authorization: Bearer <API_KEY>

Quick Start

1. Get an API key at apitube.io.
2. Add the server to your client with the block below — each one is also a ready file in configs/.
3. Restart the client and ask it something like "find positive breaking news about Tesla in English from the last week".

claude mcp add --transport http apitube-news https://mcp.apitube.io/ \  --header "Authorization: Bearer YOUR_API_KEY"

{  "mcpServers": {    "apitube-news": {      "type": "streamableHttp",      "url": "https://mcp.apitube.io/",      "headers": { "Authorization": "Bearer YOUR_API_KEY" },      "disabled": false,      "autoApprove": []    }  }}

{  "mcpServers": {    "apitube-news": {      "url": "https://mcp.apitube.io/",      "headers": { "Authorization": "Bearer YOUR_API_KEY" }    }  }}

{  "mcpServers": {    "apitube-news": {      "command": "npx",      "args": [        "-y",        "mcp-remote",        "https://mcp.apitube.io/",        "--header",        "Authorization: Bearer YOUR_API_KEY"      ]    }  }}

{  "inputs": [    { "type": "promptString", "id": "apitube-key", "description": "APITube API Key", "password": true }  ],  "servers": {    "apitube-news": {      "type": "http",      "url": "https://mcp.apitube.io/",      "headers": { "Authorization": "Bearer ${input:apitube-key}" }    }  }}

{  "mcpServers": {    "apitube-news": {      "serverUrl": "https://mcp.apitube.io/",      "headers": { "Authorization": "Bearer YOUR_API_KEY" }    }  }}

curl -s -X POST https://mcp.apitube.io/ \  -H "Content-Type: application/json" \  -d '{"jsonrpc":"2.0","method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"curl","version":"1.0.0"}},"id":1}'

{  "jsonrpc": "2.0",  "result": {    "protocolVersion": "2024-11-05",    "serverInfo": { "name": "APITube News MCP-Server", "version": "1.0.0" },    "capabilities": { "tools": { "listChanged": true }, "prompts": { "listChanged": true } }  }}

curl -s -X POST https://mcp.apitube.io/ \  -H "Content-Type: application/json" \  -H "Authorization: Bearer YOUR_API_KEY" \  -d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"search_news","arguments":{"title":"Bitcoin","language":{"code":"en"},"per_page":5}},"id":1}'

Tools

search_news

Arguments are nested objects, never dotted strings:

{ "language": { "code": "en" } }      // ✅{ "language.code": "en" }             // ❌ rejected

Three things worth knowing before the first call:

• The article body is not returned by default. The default field list is id,title,href,published_at,description,source.domain. Ask for the text explicitly with fl: "title,href,body".
• One response carries at most 25 articles. per_page defaults to 10 and is clamped to 25; walk further with page. If a result set still has to be cut — 25 articles of full text can be large — the response gains an _mcp_truncated field saying how many were omitted.
• A title search spans at most 31 days. With no dates it covers the last 31 days; a wider explicit range fails with 400 ER0110. Split longer periods into month-sized windows. Searches without a title filter have no range limit.

Misspelled arguments are rejected with JSON-RPC -32602 and a suggestion, instead of being silently ignored:

Unknown parameter 'langauge.code'. Did you mean 'language.code'?

export, query and prompt are deliberately not exposed.

suggest

The precise filters take IDs you cannot guess, so resolve them first:

suggest({ type: "entities", prefix: "Tesla" })// → [{ id: 474, name: "Tesla Robotaxi", type: "brand", … }, …]
search_news({ entity: { id: "474" }, language: { code: "en" } })

type is one of entities, categories, topics, industries; prefix is a name or its beginning. Both are required. Matching is by prefix, so read the names before filtering on the first hit.

Filters

Everything below belongs to search_news. Content, taxonomy, language, author and source filters have an ignore.* twin for exclusion (ignore.title, ignore.entity.id, ignore.source.domain, …); sentiment, media and time filters do not. Multi-value filters take up to 3 comma-separated values. has_* and is_* take 0 or 1, not true/false.

Prompts

Slash commands in clients that support MCP prompts:

Use cases

Pricing

The MCP server is part of the paid plans; the free tier covers the REST API only.

Annual billing takes 20% off. Current numbers always live at apitube.io/pricing.

Page size is capped separately: through MCP one response holds at most 25 articles on every plan, regardless of the larger per_page the REST API allows.

Troubleshooting

Auth and transport failures arrive as JSON-RPC -32000 with an APITube code in the message and the matching HTTP status.

Documentation

Registry

Published in the official MCP Registry from server.json in this repository:

mcp-name: io.apitube/news

See more on Claude Market's MCP directory.

Support

Found an argument that behaves differently from what is written here? Open an issue with the request you sent and the response you got — those corrections are the most useful thing you can file.

License

MIT — see LICENSE.