Alpaca MCP Server

Created By
tedlikeskixa year ago
Model Context Protocol (MCP) server for Alpaca trading API
Overview

what is Alpaca MCP Server?

Alpaca MCP Server is a Model Context Protocol (MCP) server designed for the Alpaca trading API, enabling interaction with trading functionalities through natural language.

how to use Alpaca MCP Server?

To use the server, clone the repository, install the required packages, set up your Alpaca API credentials in a .env file, and run the server using Python. Configure your MCP client (like Claude for Desktop) to connect to the server.

key features of Alpaca MCP Server?

  • 📊 Real-time market data and historical price information
  • 💵 Access to account balances and buying power
  • 📈 Management of current positions and their performance
  • 🛒 Natural language order placement for market and limit orders
  • 📋 Order management capabilities including tracking and cancellation

use cases of Alpaca MCP Server?

  1. Checking account balances and trading power
  2. Managing stock positions and performance tracking
  3. Placing and managing trades using natural language queries

FAQ from Alpaca MCP Server?

  • Can I use Alpaca MCP Server for real trading?

Yes, but ensure to change the configuration from paper trading to real trading in the server settings.

  • What programming language is used?

The server is built using Python.

  • Is there a license for this project?

Yes, it is licensed under the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tedlikeskix
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.

21 hours ago