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 gradedqualityDmaintenanceMCP 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.42ISC
- AlicenseBqualityDmaintenanceA 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 cleanly separate by resource and asset class (stock vs crypto vs option × bars/quotes/trades/snapshot), but there is real overlap: get_corporate_actions vs get_corporate_action_announcements are near-duplicates, and get_locate vs get_locates vs get_locate_quotes vs create_locate require careful reading. get_account_activities vs get_account_activities_by_type also blur together.
Predominantly consistent snake_case verb_noun (get_*, place_*, cancel_*, create_*, update_*, delete_*). Minor deviations: singular vs plural drift (get_option_* vs get_options docs, get_locate/get_locates), and the phrase-style do_not_exercise_options_position breaks the verb_noun pattern.
72 tools is far too many for a coherent agent-facing surface; many are granular variants (latest vs historical across three asset classes, locate quoting, doc search). The underlying trading API breadth justifies a large count, but this exceeds a manageable set and pressures selection.
Coverage is extensive: orders (place/replace/cancel/get/list), positions (get/close/close all), watchlists (full CRUD), assets, account config/activities, locates, corporate actions, and rich market data for stocks, crypto, and options, plus docs lookup. Nearly every lifecycle stage is reachable without dead ends.