TradeMCP News DocsConnect via MCP
Use the data from Claude, Cursor or another MCP client with your API key.
The hosted MCP server speaks Streamable HTTP at https://mcp.trademcp.dev/mcp and uses your normal API key, scopes, rate limit and plan.
Send the key as X-API-Key: dp_… or Authorization: Bearer dp_….
Tools
| Tool | Scope | Use |
|---|---|---|
search_news | news:read | Recent articles by keyword and symbols |
list_events | news:read | Story events with reactions |
get_event | news:read | One event in detail |
why_is_it_moving | sentiment:read | Recent moves of a symbol and likely causes |
asset_context | sentiment:read | Sentiment, flags, moves, upcoming releases |
event_type_stats | sentiment:read | What the market did after earlier stories of a type |
upcoming_calendar | sentiment:read | Scheduled releases |
Results are short and capped. A key without the needed scope gets a tool error. Each tool call counts as one request against your rate limit and usage; listing tools and connecting are free.
Clients
Claude Code:
claude mcp add --transport http trademcp https://mcp.trademcp.dev/mcp --header "X-API-Key: dp_YOUR_KEY"Other clients that support remote HTTP servers with custom headers (for example Cursor, through mcp.json) take the same URL and header:
{ "mcpServers": { "trademcp": { "url": "https://mcp.trademcp.dev/mcp", "headers": { "X-API-Key": "dp_YOUR_KEY" } } } }Clients that only support OAuth sign-in cannot use this endpoint yet. Keep the key private; anything the assistant sees is sent to its provider.