econewsapi-mcp
MCP server that exposes Brazilian financial news from econewsapi to Claude Desktop, Claude Code, and other Model Context Protocol compatible AI agents.
What it does
Lets you (or your AI agent) talk to econewsapi in natural language:
"Como tá o setor de petróleo hoje?" "Tem fato relevante novo da Vale?" "Quem foram os tickers mais comentados ontem?" "Sumarize os resultados anuais dos bancos"
Behind the scenes the agent picks the right tool, calls the API with HMAC-signed requests, and synthesizes a response.
Tools (v0.5.0)
| Tool | What it does |
|---|---|
search_news |
Filter news by ticker / source / channel / scores / time window |
get_news |
Full content + summary + entities for one news item |
trending_tickers |
B3 tickers with highest news velocity |
list_sectors |
All B3 sectors (energy, financials, ...) with PT labels |
list_tickers_by_sector |
Resolve a sector to its B3 tickers (use before search_news) |
list_topics |
Curated news topics (commodities, dividends, M&A, ...) |
sentiment_overview |
Aggregate positive/negative/neutral counts for any filter slice |
sentiment_trend |
Sentiment evolution over time (bucketed) — improving/worsening detection |
upcoming_events |
Calendar of upcoming events: COPOM decisions, Brazilian earnings (DFP/ITR), monetary reports |
get_event |
Full detail of a single calendar event (incl. AI enrichment fields when available) |
More tools coming: get_related_news, news_price_impact.
Install
pip install econewsapi-mcp
Or run directly without installing:
uvx econewsapi-mcp
Configure (Claude Desktop)
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"economatica": {
"command": "uvx",
"args": ["econewsapi-mcp"],
"env": {
"ECONEWSAPI_API_KEY": "your-api-key",
"ECONEWSAPI_API_SECRET": "your-api-secret"
}
}
}
}
Restart Claude Desktop. Open a chat — the 🔧 icon should show
Economatica News as a connected server.
Note: the package name (
econewsapi-mcp) and the env vars (ECONEWSAPI_*) keep the legacyeconewsapiprefix for backward compatibility. The display name and config key (economatica) reflect the parent brand.
Configure (Claude Code)
Add the same mcpServers block to ~/.claude/settings.json (or
.claude/settings.json in a project) and restart Claude Code.
Updating
uvx caches packages aggressively — a Claude Desktop restart alone won't
pick up a new release. Three ways to upgrade:
Option A — Pin the version (recommended for prod):
"args": ["econewsapi-mcp@0.5.0"]
Edit the JSON each time you bump. Deterministic — no cache surprises.
Option B — Always-fresh (dev-friendly, ~1-2s cold start cost):
"args": ["--refresh", "econewsapi-mcp"]
uvx checks PyPI for newer versions on every Claude Desktop launch.
Option C — One-shot manual refresh (keep config simple):
uvx --refresh econewsapi-mcp --help
# or just bust the cache:
uv cache clean econewsapi-mcp
Then restart Claude Desktop. Next launch picks up the new version.
If you installed via uv tool install:
uv tool upgrade econewsapi-mcp
If you installed via pip in a venv:
pip install --upgrade econewsapi-mcp
Configure (dev / local source)
{
"mcpServers": {
"econewsapi": {
"command": "uvx",
"args": ["--from", "/abs/path/to/EcoNewsApi-MCP", "econewsapi-mcp"],
"env": { "ECONEWSAPI_API_KEY": "...", "ECONEWSAPI_API_SECRET": "..." }
}
}
}
Environment variables
| name | required | default |
|---|---|---|
ECONEWSAPI_API_KEY |
yes | — |
ECONEWSAPI_API_SECRET |
yes | — |
ECONEWSAPI_BASE_URL |
no | https://news-api.economatica.com |
ECONEWSAPI_LOG_LEVEL |
no | INFO |
Development
git clone <this-repo>
cd EcoNewsApi-MCP
python3 -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
# run smoke test against prod (requires test API key)
export ECONEWSAPI_API_KEY=...
export ECONEWSAPI_API_SECRET=...
pytest tests/ -v
# run the MCP server manually to inspect stdio output
econewsapi-mcp
License
MIT
Metadata
Release files for econewsapi-mcp 0.7.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| econewsapi_mcp-0.7.5.tar.gz | 19.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| econewsapi_mcp-0.7.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.9 kB
Release files / econewsapi_mcp-0.7.5.tar.gz
| Download URL | econewsapi_mcp-0.7.5.tar.gz |
|---|---|
| Size | 19.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a737d92f96311b8c2793e621d972b44fa558355d149087610a1b4b1e98ddf27
|
|
BLAKE2b-256 checksum How to use checksums |
3b1d37886c7ea9077d65e4457ff9aa9ed23ece4c8a128a281269675c01477628
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 5, 2026.
Transparency logRelease files / econewsapi_mcp-0.7.5-py3-none-any.whl
| Download URL | econewsapi_mcp-0.7.5-py3-none-any.whl |
|---|---|
| Size | 17.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
500aeab1ed165b4027c08cc269ee743825e9702641c9e5399260d8974f8a8276
|
|
BLAKE2b-256 checksum How to use checksums |
28305a72a9a4a4e50f67fc968bfc46c9ae2c437c2d386e05e81efcddaa9afca7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 5, 2026.
Transparency log