get-assetsLABSCO SUMMARY
There is no order tool here, which makes this a data client rather than a trading one.
Assets, bars, calendar and news are all reads, so a key handed to this server cannot place a trade through it — a meaningful property when the caller is a model. get-market-days is the one that keeps an analysis honest, since a gap in the bars over a holiday is otherwise indistinguishable from missing data. The parameter names carry the contract: symbols, start, end and timeframe shape every request, and assetClass is the only filter on the asset list.
What it is
An Alpaca client with four read tools — assets, historical bars, market days and news.
What you get
- get-assets returns the tradable assets, filterable by asset class.
- get-stock-bars returns historical price bars for a set of symbols over a start and end date at a chosen timeframe.
- get-market-days returns the market calendar between a start and end date.
- get-news returns news for a set of symbols over a start and end date.
Requirements
An Alpaca API key and secret in ALPACA_API_KEY and ALPACA_SECRET_KEY, with the endpoints named by ALPACA_ENDPOINT and ALPACA_BROKER_ENDPOINT.
Setup effort
One command plus a key — npx -y alpaca-mcp, then supply credentials
USE CASES
Pulling a price history to analyse
Symbols, a date range and a timeframe are the whole request, and the asset list is where the symbols come from.
Separating a market holiday from missing data
A gap in the bars is ambiguous on its own; the calendar is what says whether the market was open at all.
Checking what news landed around a move in the price
Both reads take the same symbols and date range, so the headlines and the bars line up without a second source.
Finding out what is tradable in an asset class
The asset class filter is the only narrowing here, and the result is what every other call has to draw its symbols from.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get-market-daysget-newsget-stock-barsBEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected. The server is read-only: nothing places orders or changes an account.
Requires
- npx on PATH
- ALPACA_API_KEY in your environment
- ALPACA_SECRET_KEY in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
npx -y alpaca-mcpMCP Clients
Any MCP client
{
"mcpServers": {
"alpaca-mcp": {
"command": "npx",
"args": [
"-y",
"alpaca-mcp"
],
"env": {
"ALPACA_ENDPOINT": "https://data.alpaca.markets",
"ALPACA_BROKER_ENDPOINT": "https://broker-api.alpaca.markets",
"ALPACA_API_KEY": "<YOUR_API_KEY>",
"ALPACA_SECRET_KEY": "<YOUR_SECRET_KEY>"
}
}
}
}<YOUR_API_KEY> and <YOUR_SECRET_KEY> are your Alpaca API key and secret. The two endpoint values are Alpaca's own.