screener-mcp-server

An MCP server for Screener.in — search Indian listed companies, pull key ratios, multi-year financial statements, peer comparisons, and run custom fundamental screens, all from Claude (or any MCP client).

Important: no official API

Screener.in explicitly states they don't provide an API — only CSV export from the UI. This server works by reading the same public, signed-out pages a browser would see (search, company pages, and the /screen/raw/ query endpoint). It does not require login for the core tools.

Because this isn't an official API:

• Please keep request volume reasonable — the server throttles and caches requests for you (5 min cache, ~600ms min gap between requests), don't work around that.

• Guest (logged-out) access to custom screens is capped by Screener to a small number of result rows. If you want more rows or CSV-export-only data, set SCREENER_SESSION_COOKIE (see below) to a cookie from your own logged-in session.

• Screener's HTML structure can change without notice; if a tool starts erroring, the CSS selectors in src/services/scraper.ts likely need a small update.

• Review Screener's Terms before heavy or commercial use.

Related MCP server: Daito

Tools

Setup

npm install
npm run build

Run locally (stdio) — for Claude Desktop / Claude Code

Add to your MCP client config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "screener": {
      "command": "node",
      "args": ["/absolute/path/to/screener-mcp-server/dist/index.js"]
    }
  }
}

Run as a remote HTTP server

TRANSPORT=http PORT=3000 npm start

Then point your MCP client at http://localhost:3000/mcp.

Optional: logged-in session for more screen results

export SCREENER_SESSION_COOKIE="csrftoken=...; sessionid=..."

Grab this from your browser's DevTools → Network tab → any request to screener.in → Cookie request header, while logged into your own Screener account. Never share this value; it's your personal session.

Development

npm run dev    # tsc --watch

If Screener changes their page markup and a tool starts failing, check the selectors in src/services/scraper.ts (#top-ratios, .pros/.cons, #profit-loss/#balance-sheet/etc. table sections, #peers table) against the current HTML.