Alpaca Trading MCP Server

Created By
MardiantoSa year ago
Overview

what is Alpaca Trading MCP Server?

Alpaca Trading MCP Server is a Python implementation of the Model Context Protocol (MCP) Server designed for Alpaca Trading, enabling Large Language Models (LLMs) to interact with Alpaca's trading API.

how to use Alpaca Trading MCP Server?

To use the server, clone the repository, set up your environment, and configure it with your Alpaca API credentials. You can then interact with the server using the Claude for Desktop application.

key features of Alpaca Trading MCP Server?

  • Account Management: View account information and portfolio summary.
  • Market Data: Access real-time quotes and historical price bars.
  • Trading Operations: Place market and limit orders.
  • Position Tracking: Monitor current positions and recent orders.

use cases of Alpaca Trading MCP Server?

  1. Automating trading strategies using LLMs.
  2. Accessing real-time market data for analysis.
  3. Managing trading operations programmatically.

FAQ from Alpaca Trading MCP Server?

  • Is this server safe to use for live trading?

The server uses paper trading by default, which is recommended for testing before live trading.

  • What programming language is used?

The server is implemented in Python.

  • Can I use it with any trading strategy?

Yes, you can integrate it with various trading strategies as long as they comply with Alpaca's API.

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

Recommend Servers

View All
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.

8 hours ago