Alpaca MCP Server: trading tools plus in-context API docs

Broker and market-data APIs are a natural MCP surface: list positions, fetch bars, submit a paper order. The failure mode is familiar — the model has tools but not the manual: bracket vs simple order, replace constraints, options chain shape, auth headers. Builders paste half the docs into the system prompt or hope the model remembers.

On 10 Aug 2026 Alpaca shipped documentation access on the same Trading MCP Server that already exposes market data, account, and trading tools. Announcement: Alpaca’s MCP Server for Trading API Adds Documentation Access.

What shipped

Read-only documentation tools covering:

Trading API
Market Data API
Authentication references

Through those tools a connected assistant can search supported API references, pick an operation for a task, and inspect parameters, request shape, response fields, constraints, and source documentation links. They do not change accounts or order state.

V2 already built most action tools from OpenAPI (operations, params, schemas). Docs tools add the surrounding intent layer OpenAPI usually lacks: what the operation is for, what can go wrong, what to check before calling it.

Why it matters for agent builders

Before vs after
Before	After (docs tools)
Paste docs into prompt or RAG yourself	Retrieve scoped API context on demand
Tools without “which endpoint?” reasoning	Intent → documented operation → optional tool call
Easy to invent fields	Review request against docs + source links
Docs browse in a browser tab	Same MCP session as trading/data tools

This is the same pattern good Solana agent stacks want: executable tools + authoritative docs retrieval, not tools alone. Related DevRels threads: MCP + payments, Solana developer MCP, protocol “docs as tools.”

Example prompts Alpaca highlights

Bracket order: show operation, required params, request shape, response fields
Replace order: which operation, constraints, auth requirements
Review a draft order payload against docs; flag missing/unsupported fields; include source links
Option chain: only the docs needed for the operation and inputs
Explain behaviour and constraints without placing or modifying orders

Operational habit: start sessions with “use documentation tools only” until the plan is solid, then allow trading tools (preferably paper keys first).

Setup

New install

Alpaca Trading API account + paper API keys
Connect per MCP server docs or alpacahq/alpaca-mcp-server
Restart the MCP client after config save
New chat → docs-only verify prompt (below)

Existing V2 users

Documentation access requires Trading MCP Server 2.2.1+. With uvx:

bash

uvx alpaca-mcp-server@latest --version
# expect 2.2.1 or newer
# fully restart MCP client; open a NEW conversation

V1 users should migrate to V2 first (see Alpaca’s V1→V2 notes). If docs tools missing: confirm version, full client restart, new conversation, then troubleshooting in their MCP docs.

Verify prompt

text

Find the Alpaca API documentation for replacing an existing order.
Return the operation, required parameters, constraints, response fields,
and source links. Use documentation tools only.

Design takeaway for your own MCP servers

Generate mutative/read tools from OpenAPI (or IDL) so schemas stay true
Add read-only doc search over the human docs site (and link canonical URLs)
Separate tool classes so agents can be instructed “docs only” before “trade”
Default examples to paper / sandbox credentials
Never treat model output as compliance or investment advice — Alpaca’s own disclaimer applies; same for any agent trading stack

Ecosystem context

Alpaca is also pushing a Skills library for AI agents and a Trading API CLI. Docs-in-MCP is the glue between “agent can call APIs” and “agent knows which call is legal.”

This is equities/options brokerage infrastructure (Alpaca Securities / FINRA/SIPC), not a Solana program — still relevant to DevRels readers building agent toolchains, multi-agent trading demos, or MCP servers for their own APIs.

Summary

Alpaca’s Trading MCP Server 2.2.1 adds read-only API documentation tools alongside market data, account, and trading tools so agents can resolve intent to documented operations with parameters, constraints, and source links—without stuffing the prompt with manuals. Update with uvx alpaca-mcp-server@latest, restart the client, verify with a docs-only prompt, and keep order tools gated until review is done. For anyone shipping MCP on a real API: OpenAPI tools + docs retrieval is becoming table stakes.