alpaca-mcp-server
OfficialRelated Servers
Alternatives to alpaca-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server implementation for Alpaca's Trading API that enables LLMs to interact with Alpaca's trading infrastructure using natural language, supporting stock, options, and crypto trading, portfolio management, watchlists, and market data.4MIT
- FlicenseNot gradedqualityCmaintenanceMCP server and CLI for trading stocks, ETFs, and crypto via Alpaca, enabling natural language trading through AI assistants and terminal with paper trading defaults.-
- AlicenseDqualityDmaintenanceMCP server that exposes Alpaca Market Data & Broker API as tools, enabling access to financial data like stock bars, assets, market days, and news through the Message Control Protocol.417 npm2ISC
- AlicenseBqualityCmaintenanceA comprehensive Model Context Protocol server for Alpaca's Trading API that enables natural language trading operations through AI assistants, supporting stocks, options, crypto, portfolio management, and real-time market data.69MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server enabling LLMs like Claude to interact with the Alpaca trading API through natural language for stock trading, checking positions, fetching market data, and managing your account.28MIT
- AlicenseAqualityDmaintenanceAn MCP server that exposes trading analytics — technical indicators, portfolio state, risk metrics, and backtest results — as tools an LLM agent can call.5MIT
TDQS
Scored across 72 tools
Most tools target distinct Alpaca endpoints (stocks vs crypto vs options, historical vs latest, account vs trading) and descriptions are explicit. However, a few pairs overlap: get_corporate_actions vs get_corporate_action_announcements, and get_most_active_stocks vs get_market_movers could be confused. Overall mostly distinct.
All tool names use snake_case with a verb_noun structure (get_, place_, cancel_, close_, create_, update_, delete_, add_, remove_, search_, fetch_, list_). Minor variations like list_ and fetch_ are contextually appropriate and consistent. No mixing of conventions.
72 tools is far beyond the recommended 3-15 range and exceeds the 'extreme mismatch' threshold of 50+. Even though the Alpaca API is broad, this many tools will overwhelm an agent's selection process.
The surface covers account, orders, positions, watchlists, assets, market data (stocks, crypto, options, fixed income), news, corporate actions, locates, calendar, clock, and docs. Nearly all major Alpaca API endpoints and lifecycles are represented, with no obvious critical gaps.