Skip to main content
Glama
enesjakozh
cesarvarela

Alpaca MCP Server

by cesarvarela
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Alpaca MCP Server

Expose Alpaca Market Data & Broker API as MCP tools.

Installation

Installing via Smithery

To install Alpaca Market Data Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @cesarvarela/alpaca-mcp --client claude

Manual Installation

npm install alpaca-mcp

Related MCP server: alpaca-mcp-server

Local Development

git clone <repo-url>
cd alpaca-mcp
npm install

Environment Variables

Create a .env at project root with:

ALPACA_ENDPOINT=https://data.alpaca.markets
ALPACA_BROKER_ENDPOINT=https://broker-api.alpaca.markets
ALPACA_API_KEY=YOUR_ALPACA_API_KEY
ALPACA_SECRET_KEY=YOUR_ALPACA_SECRET_KEY

Commands

  • start (dev): npm start (runs npx tsx index.ts)

  • build: npm run build (compiles to dist/)

  • run compiled: node dist/index.js

Usage

Once running, the MCP server listens on stdin/stdout. Use any MCP client or the CLI:

npm link      # optional
alpaca-mcp    # starts server globally

Available Tools

  • get-assets { assetClass?: "us_equity" | "crypto" }

  • get-stock-bars { symbols: string[]; start: string; end: string; timeframe: string }

  • get-market-days { start: string; end: string }

  • get-news { start: string; end: string; symbols: string[] }

Each returns JSON in content[0].text or an error.

MCP Client Configuration

To integrate via mcp.config.json, add the following under the mcpServers key:

{
  "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>"
      }
    }
  }
}

## Publishing

```bash
npm publish

License

ISC

Available Tools

4 tools
get-assetsD
ParametersJSON Schema
NameRequiredDescriptionDefault
assetClassNous_equity

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-market-daysD
ParametersJSON Schema
NameRequiredDescriptionDefault
endYes
startYes

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-newsD
ParametersJSON Schema
NameRequiredDescriptionDefault
endYes
startYes
symbolsYes

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-stock-barsD
ParametersJSON Schema
NameRequiredDescriptionDefault
endYes
startYes
symbolsYes
timeframeYes

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 4 tool updatesv1.0.0
    • First observedget-assets
    • First observedget-market-days
    • First observedget-news
    • First observedget-stock-bars
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.8/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: get-assets retrieves assets, get-market-days provides market schedule information, get-news fetches news data, and get-stock-bars obtains stock price bars. There is no overlap in functionality, making it easy for an agent to select the correct tool.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with hyphens (get-assets, get-market-days, get-news, get-stock-bars). This uniformity makes the tool set predictable and easy to understand.

Tool Count3/5

With only 4 tools, the set feels thin for a financial data server, potentially lacking operations like trading, account management, or more granular data queries. However, it covers basic data retrieval functions adequately.

Completeness2/5

The tool surface is severely incomplete for a financial domain, offering only read operations (get-*) with no create, update, delete, or trading capabilities. This limits agents to passive data access without supporting full investment workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Alpaca Trading MCP Server

    laukikk
    A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server that interfaces with Alpaca trading API, allowing users to manage portfolios, place trades, and access market data through natural language interactions.
    8
    35
    MIT
  • alpaca-mcp-server by alpacahq

    alpaca-mcp-serverofficial

    alpacahq
    A
    license
    B
    quality
    A
    maintenance
    Alpaca’s official MCP Server lets you trade stocks, ETFs, crypto, and options, run data analysis, and build strategies in plain English directly from your favorite LLM tools and IDEs
    72
    12,704 PyPI
    970
    MIT

  • Alpaca MCP Gold Standard

    JOravetz
    F
    license
    Not graded
    quality
    D
    maintenance
    A comprehensive MCP server for professional trading operations with Alpaca, providing 31 tools for account management, market data, order execution, custom strategy execution, and advanced portfolio analytics with intelligent position classification.
    2
    -

  • FinClaw

    IlyasFardaouix
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server that provides AI agents with financial tools including real-time quotes, backtesting, technical analysis, and multi-exchange data via a simple CLI interface.
    1
    MIT

Appeared in Searches