To install Alpaca Market Data Server for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@cesarvarela/alpaca-mcp):
Alpaca mcp mcp server connects Alpaca MCP to AI assistants that speak the Model Context Protocol. To install Alpaca Market Data Server for Claude Desktop automatically via Smithery:.
To install Alpaca Market Data Server for Claude Desktop automatically via Smithery:
Once connected, the assistant can call these 4 tools directly:
build — npm run build (compiles to dist/)get — assets** { assetClass?: "us_equity" | "crypto" }get-stock — bars** { symbols: string[]; start: string; end: string; timeframe: string }get-market — days** { start: string; end: string }The server is distributed via npm as @smithery/cli, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
Before the server will start you need to supply 8 environment variables: ALPACA_ENDPOINT, ALPACA_BROKER_ENDPOINT, ALPACA_API_KEY, ALPACA_SECRET_KEY, YOUR_ALPACA_API_KEY, YOUR_ALPACA_SECRET_KEY, YOUR_API_KEY, YOUR_SECRET_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Alpaca MCP sits in that group, and the shape of its toolset — build, get, get-stock among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| build | npm run build (compiles to dist/) |
| get | assets** { assetClass?: "us_equity" | "crypto" } |
| get-stock | bars** { symbols: string[]; start: string; end: string; timeframe: string } |
| get-market | days** { start: string; end: string } |
{
"mcpServers": {
"alpaca": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"ALPACA_ENDPOINT": "your-value",
"ALPACA_BROKER_ENDPOINT": "your-value",
"ALPACA_API_KEY": "your-value",
"ALPACA_SECRET_KEY": "your-value",
"YOUR_ALPACA_API_KEY": "your-value",
"YOUR_ALPACA_SECRET_KEY": "your-value",
"YOUR_API_KEY": "your-value",
"YOUR_SECRET_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| ALPACA_ENDPOINT | Configuration value read at startup. | Optional |
| ALPACA_BROKER_ENDPOINT | Configuration value read at startup. | Optional |
| ALPACA_API_KEY | Credential the server authenticates with. | Yes |
| ALPACA_SECRET_KEY | Credential the server authenticates with. | Yes |
| YOUR_ALPACA_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_ALPACA_SECRET_KEY | Credential the server authenticates with. | Yes |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_SECRET_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.