Skip to main content
hc
Submit
3 compared

Finance data MCP servers compared

Financial-data MCP servers that bring banking and market data into Claude, compared on trust, setup, and safety.

Open in the interactive comparison tool
FieldPlaid MCP Server for Claude

Analyze, troubleshoot, and optimize Plaid integrations for banking data and financial account linking

Open dossier 		Alpaca MCP Server

Official Alpaca MCP server for Trading API workflows, including account and portfolio data, orders, positions, watchlists, assets, stocks, crypto, options, news, corporate actions, and market data.

Open dossier 		Financial Datasets MCP Server

Python MCP server that lets Claude query Financial Datasets for stock statements, prices, company news, crypto prices, and SEC filings.

Open dossier
Trust
Install riskLow riskReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Categorymcpmcpmcp
Sourcefirst-partysource-backedsource-backed
AuthorPlaidAlpacaFinancial Datasets
Added2025-09-182026-06-062026-06-05
Platforms
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo———
Safety notes✓Use sandbox or restricted Plaid credentials and avoid exposing production banking tokens outside the required workflow.✓Alpaca MCP Server can expose account balances, buying power, positions, orders, activities, watchlists, assets, market data, news, corporate actions, stocks, crypto, options data, and trading tools to the MCP client. Trading tools can place stock, ETF, crypto, and option orders, cancel orders, close positions, liquidate portfolios, replace orders, and exercise or mark do-not-exercise option contracts. Paper trading is the default documented mode; setting `ALPACA_PAPER_TRADE=false` points trading calls at live Alpaca accounts and can result in real financial losses. Require explicit human approval before any order placement, cancellation, liquidation, option exercise, live-account change, or strategy involving leverage, margin, extended hours, crypto, or options. Use `ALPACA_TOOLSETS` to restrict the server to read-only or data-only toolsets when trading tools are not needed. The upstream order override code warns that read timeouts may happen after an order was sent; users should check open orders before retrying to avoid duplicate trades.✓This server retrieves financial market data; do not treat tool output or model summaries as investment, trading, tax, or legal advice. Current prices, crypto prices, filings, and news can be delayed, incomplete, rate limited, or unavailable depending on API plan and market conditions. Review generated analysis before using it in portfolio decisions, trading workflows, client reports, or compliance-sensitive research. The server sends ticker symbols, date ranges, filing filters, and research queries to the Financial Datasets API.
Privacy notes✓Account-linking data, balances, transactions, institution identifiers, and financial metadata may be sent through model context.✓Alpaca API keys, secret keys, account IDs, balances, buying power, portfolio history, activities, positions, orders, watchlists, option contracts, crypto holdings, and trade history can be exposed to the MCP client. Prompts and responses may include private trading strategy, portfolio allocation, order intent, symbols, quantities, prices, client order IDs, and market data queries. MCP clients, model providers, terminal history, logs, and chat transcripts may retain financial data and trading instructions. Upstream documentation states the server sends an Alpaca MCP user agent string for API calls; review Alpaca privacy and disclosure materials for account data handling.✓API keys must be stored in environment variables or local secret managers and never committed to configuration files. Queried tickers, crypto symbols, time ranges, filings, and news requests can reveal research interests, watchlists, client assignments, or trading hypotheses. Tool outputs may include financial statements, prices, filings, and news that become part of the model context and logs. Avoid sending private portfolio holdings, customer identifiers, or material non-public information through prompts or tool arguments.
Prerequisites
  • Plaid account (create account on Plaid Dashboard to get API credentials)
  • API credentials (client_id and secret from Plaid Dashboard)
  • SSE or HTTP transport support (remote MCP server at https://api.dashboard.plaid.com/mcp/sse or https://api.dashboard.plaid.com/mcp)
  • Internet connection (remote Plaid API access required)
  • Python 3.10 or newer and uv or uvx available.
  • Alpaca API key and secret key for a paper trading account or an explicitly approved live account.
  • Review of Alpaca account permissions, paper versus live mode, options approval, crypto availability, and market data subscription limits.
  • A narrow `ALPACA_TOOLSETS` allowlist for the workflow whenever full trading access is not required.
  • Python 3.11 or newer, matching the upstream project metadata.
  • uv installed on the machine running the MCP server.
  • A cloned checkout of `financial-datasets/mcp-server`.
  • Financial Datasets API key stored as `FINANCIAL_DATASETS_API_KEY`.
Install
claude mcp list && claude mcp status plaid
uvx alpaca-mcp-server
uv run server.py
Config
{
  "mcpServers": {
    "plaid": {
      "url": "https://api.dashboard.plaid.com/mcp/sse",
      "type": "sse"
    }
  }
}
Manual-only setup:
claude mcp add alpaca --scope user --transport stdio uvx alpaca-mcp-server --env ALPACA_API_KEY=YOUR_ALPACA_API_KEY --env ALPACA_SECRET_KEY=YOUR_ALPACA_SECRET_KEY
{
  "mcpServers": {
    "financial-datasets": {
      "command": "uv",
      "args": ["--directory", "PATH_TO_FINANCIAL_DATASETS_MCP", "run", "server.py"],
      "env": {
        "FINANCIAL_DATASETS_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimed
More comparisons, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.