The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Alpaca MCP Server
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…
Install
$
git clone https://github.com/alpacahq/alpaca-mcp-serverInstall command taken from the project's README or registry entry. Always review code before running it.
README excerpt
Read full README on GitHub →A comprehensive Model Context Protocol (MCP) server for Alpaca's Trading API. Enable natural language trading operations through AI assistants like Claude, Cursor, and VS Code. Supports stocks, options, crypto, portfolio management, and real-time market data.
Alpaca MCP Server v2 is here. This version is a complete rewrite built with FastMCP and OpenAPI. If you're upgrading from v1, please read the Upgrade Guide — tool names, parameters, and configuration have changed.
Table of Contents
- Upgrading from V1
- Prerequisites
- Getting Your API Keys
- Setup
- Configuration
- Features
- Example Prompts
- Available Tools
- Testing
- Project Structure
- Troubleshooting
- Disclosure
Upgrading from V1
V2 is a complete rewrite built with FastMCP and OpenAPI. None of the V1 tools exist in V2 — tool names, parameters, and schemas have changed. You cannot use V2 as a drop-in replacement if your setup depends on specific V1 tool names or parameters.
What changes
| Aspect | V1 | V2 |
|---|---|---|
| Tool names | Hand-crafted (e.g. get_account_info) |
Spec-derived with overrides (e.g. get_account_info — names may overlap but schemas differ) |
| Parameters | Custom schemas | Aligned with Alpaca API specs |
| Configuration | .env + init command |
Env vars in MCP client config only |
| Tool filtering | Not supported | ALPACA_TOOLSETS env var |
| Whitelisting | Not supported | Use ALPACA_TOOLSETS to restrict tools |
How to avoid V1-style usage in V2
MCP clients discover tools dynamically from the server. There is no config file where you "whitelist" tool names — the client gets whatever tools the server exposes. To avoid your client or AI assistant using V2 incorrectly:
Similar plugs
Reverse engineer anything with agents, from app behavior down to native binaries.
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype…
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)
A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Grok Build & Hermes Agent. Only official website: ccswitch.io