Connect your AI client - Cursor, Claude, ChatGPT, or n8n - to Webz.io News Search. The client gets a news_search_by_webz tool and can search global news by itself.
https://news-search-mcp.webz.io/mcp
Don't have an account? Sign up for free to get your API token.
Log in at webz.io and copy the API token from your dashboard. It is the same token you use for the News Search API.
Replace YOUR_WEBZ_TOKEN with your token.
Add this to ~/.cursor/mcp.json (%USERPROFILE%\.cursor\mcp.json on Windows) and restart Cursor:
{
"mcpServers": {
"webz-news-search": {
"url": "https://news-search-mcp.webz.io/mcp",
"headers": {
"Authorization": "Bearer YOUR_WEBZ_TOKEN"
}
}
}
}Merge the same webz-news-search entry into your Claude Desktop config file - do not replace the whole file - then restart Claude Desktop:
| OS | Config file |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Linux | ~/.config/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
Run in your project root:
claude mcp add --transport http webz-news-search https://news-search-mcp.webz.io/mcp --header "Authorization: Bearer YOUR_WEBZ_TOKEN"
Add an MCP Client Tool node and connect it to an AI Agent node's Tool input:
| Field | Value |
|---|---|
| Endpoint | https://news-search-mcp.webz.io/mcp |
| Server Transport | HTTP Streamable |
| Authentication | Bearer Auth |
| Tools to Include | All |
Create a Bearer Auth credential and paste your Webz.io API token as the bearer token. For the community node, standalone workflows, and ready-made templates, see the n8n integration.
Add https://news-search-mcp.webz.io/mcp as a custom connector (Claude.ai: Settings > Connectors; ChatGPT: Settings > Apps & Connectors with Developer mode on). Both use OAuth: leave Client ID and Secret empty, then paste your Webz token on the authorize page. Full step-by-step walkthroughs: news-search-mcp.webz.io.
Opening the /mcp endpoint in a browser returns 401 Unauthorized by design - browsers do not send your token. Use an MCP client.
Ask your AI client naturally - mentioning "news" or "Webz" helps it pick the tool:
news_search_by_webz
| Parameter | Default | Description |
|---|---|---|
| query | required | Natural-language topic or question |
| k | 10 | Articles to return (1-50) |
| days | 7 | How many days back to search |
| allow_all_dates | false | Search the full coverage window instead of days |
| score_gte | 4 | Minimum match score, 0-10 (set 0 to disable the floor) |
| score_lte | - | Maximum match score, 0-10 |
| domain | - | Only these source domains, e.g. cnn.com, yahoo.com |
| exclude_domain | - | Skip these source domains; a domain cannot be in both lists |
| language, country, sentiment, category | - | Same values as Filters; country codes are ISO-2 uppercase (US, GB) |
| topic | - | Topic tags (case-insensitive) |
| person, organization, location | - | Entity names (case-insensitive) |
| ticker | - | Stock ticker symbols, e.g. AAPL (case-insensitive) |
| political_bias | - | Source political bias: left, center, right |
| domain_rank_gte, domain_rank_lte | - | Source domain rank range (integers) |
| allow_multiple_chunks_per_article | false | When true, return more than one relevant chunk from the same article |
Each result returns the article title, URL, publish date, matching text excerpt, and metadata (topic, person, organization, location, ticker, political_bias, domain_rank).
Every tool call runs a regular News Search request with your token - the same credits and rate limits apply. See Errors, Rate Limits & Credits.
Never commit your token to git or put it in a URL.
Set it once as an environment variable and reference it from the config:
"Authorization": "Bearer ${env:WEBZ_API_TOKEN}"