MCP server for the NewsData.io REST API (latest/archive/crypto/market news, source discovery, aggregate counts).
MCP server for the NewsData.io REST API (latest/archive/crypto/market news, source discovery, aggregate counts). Exposed over MCP by the newsdata mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
The official MCP server for the Newsdata.io News API. It exposes real-time, historical, crypto, and market news — plus source discovery and aggregate counts — as tools for Claude Desktop, Claude Code, Cursor, Zed, Cline, VS Code Copilot, Windsurf, ChatGPT Desktop, and any other MCP-compatible AI assistant. Ask questions in natural language; the assistant calls the right tool and returns formatted news.
Everything the assistant can do here goes through one of these:
get_latest_news — /api/1/latestget_archive_news — /api/1/archiveget_crypto_news — /api/1/cryptoget_market_news — /api/1/marketget_news_sources — /api/1/sourcesget_news_counts — /api/1/countget_crypto_counts — /api/1/crypto/countget_market_counts — /api/1/market/countCursor — Create or edit .cursor/mcp.json in your project root (or ~/.cursor/mcp.json globally) — same JSON block. Restart Cursor; the server appears underWindsurf — Edit ~/.codeium/windsurf/mcp_config.json — same JSON block as the Claude Code example. Restart WindsurfReleasing — 1. Bump version in src/newsdata_mcp/init.py. 2. Commit and tag: git tag vX.Y.Z && git push --tags. 3. .github/workflows/release.yml buildsYou will need 3 environment variables: NEWSDATA_API_KEY, NEWSDATA_BASE_URL, NEWSDATA_INTEGRATION_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at newsdata-mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Newsdata's toolset — get_latest_news, get_archive_news, get_crypto_news and 8 more — is a fair guide to whether it matches your workflow.
This entry was verified against Newsdata's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| get_latest_news | /api/1/latest |
| get_archive_news | /api/1/archive |
| get_crypto_news | /api/1/crypto |
| get_market_news | /api/1/market |
| get_news_sources | /api/1/sources |
| get_news_counts | /api/1/count |
| get_crypto_counts | /api/1/crypto/count |
| get_market_counts | /api/1/market/count |
| Cursor | Create or edit .cursor/mcp.json in your project root (or ~/.cursor/mcp.json globally) — same JSON block. Restart Cursor; the server appears under **Cursor Settings → MCP**. |
| Windsurf | Edit ~/.codeium/windsurf/mcp_config.json — same JSON block as the Claude Code example. Restart Windsurf. |
| Releasing | 1. Bump __version__ in src/newsdata_mcp/__init__.py. 2. Commit and tag: git tag vX.Y.Z && git push --tags. 3. .github/workflows/release.yml builds the sdist + wheel, publishes to PyPI via Trusted Publishing (no token), a |
{
"mcpServers": {
"newsdata": {
"command": "uvx",
"args": ["newsdata-mcp"],
"env": {
"NEWSDATA_API_KEY": "your-value",
"NEWSDATA_BASE_URL": "your-value",
"NEWSDATA_INTEGRATION_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| NEWSDATA_API_KEY | Credential the server authenticates with. | Yes |
| NEWSDATA_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| NEWSDATA_INTEGRATION_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.