Stock MCP Server

MCP server for Indian stock market analysis — fundamentals, technicals, DCF, peer comparison. Exposed over MCP by the stock mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

Adding it to your client

The server ships on PyPI as stock-analyst-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

• analyze_stock — Full analysis: fundamentals + technicals + peers + DCF + forecast + news
• get_fundamentals — Financial ratios: profitability, liquidity, leverage, efficiency, valuation
• get_technicals — Technical signals: EMA trend, RSI, MACD, Bollinger position
• get_peer_comparison — Peer fundamental + technical metrics with rankings
• get_dcf_valuation — DCF: WACC (India-adjusted), equity value/share, sensitivity range
• get_revenue_forecast — Revenue forecast: base/bull/bear scenarios
• get_news — Recent headlines + analyst recommendation summary
• compare_stocks — Side-by-side comparison of multiple stocks
• get_raw_data — Fetch cached raw financials for deep dives
• get_config — View current configuration settings for all analysis tools
• set_config — Update configuration settings dynamically (e.g., technical analysis period)
• Key — Type

Configuration

You will need one environment variable: SA_REDIS_URL. 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.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Stock.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the stock mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Stock's toolset — analyze_stock, get_fundamentals, get_technicals and 11 more — is a fair guide to whether it matches your workflow. It is maintained by Stock Analyst Contributors; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.