Alpaca MCP Server

Created By
idsts2670a year ago
Overview

what is Alpaca MCP Server?

Alpaca MCP Server is a Model Context Protocol (MCP) server implementation that allows large language models (LLMs) to interact with Alpaca's trading infrastructure using natural language, facilitating stock and options trading, portfolio management, and real-time market data access.

how to use Alpaca MCP Server?

To use the server, clone the repository, install the required packages, configure your API keys in a .env file, and start the server using Python. Connect it with compatible MCP clients like Claude for Desktop.

key features of Alpaca MCP Server?

  • Real-time market data and historical price access
  • Account and position management
  • Order management for stocks and options
  • Watchlist management for tracking assets
  • Support for natural language queries for trading actions

use cases of Alpaca MCP Server?

  1. Automating stock trading through natural language commands.
  2. Managing investment portfolios and tracking performance.
  3. Accessing real-time market data for informed trading decisions.

FAQ from Alpaca MCP Server?

  • Can I use this server for live trading?

Yes, but ensure to configure your API keys for live trading in the settings.

  • Is there a cost associated with using Alpaca MCP Server?

The server itself is free to use, but trading fees may apply based on Alpaca's policies.

  • What programming language is used for this server?

The server is implemented in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
idsts2670
Star
0
Language
Python
License
MIT license
Category
finance
Tags

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago