Financial MCP Server

Financial MCP server exists for a simple reason — assistants are far more useful when they can act on Financial directly instead of describing what you should do. Azure / Render / GCP Cloud Run host the MCP backend · Cloudflare deploys the optional HTTPS proxy.

What you get

• Core Stock Toolkit — Quotes, company overview, and price history tools for practical analysis workflows
• Portfolio With Live Values — Maintain a watchlist/positions store and return portfolio-level valuation context
• Configurable Price Alerts — Set per-ticker above / below thresholds and evaluate triggered alert events
• News + Context Layer — Retrieve market news and optional sentiment-rich context summaries for research workflows
• Secure Streamable HTTP — Static bearer (MCP_ACCESS_TOKEN) or OAuth JWT validation (MCP_AUTH_MODE=oauth) for public deployments
• Cloud-Ready Deployment — Docker + one-click deploys for Azure Container Apps, Render, Google Cloud Run, and Cloudflare Worker proxy

What the assistant can call

Once Financial is connected, these are the calls the assistant has available:

• Prerequisites — The Prerequisites tool exposed by this server

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need 8 environment variables: SERPAPI_API_KEY, TELEGRAM_BOT_TOKEN, TELEGRAM_USER_ID, OPENAI_API_KEY, MCP_ACCESS_TOKEN, OAUTH_ISSUER_URL, OAUTH_JWKS_URL, MCP_RESOURCE_SERVER_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.

• Python 3.7+ - Claude Desktop (or any MCP-compatible client) - Telegram bot credentials (for alerting) - Internet connection (for market/news data)

Choosing this one

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Financial's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by osamadev; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Financial's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• 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.
• 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 financial mcp server does with a few real requests.