Alpaca MCP integration for AI agents.
Connect AI agents to Alpaca through 22 structured actions, including get account, get account config, and get account portfolio history. Review authenticatio…
- ACTION CONTRACTS
- 22
- AUTHENTICATION
- OAuth 2.0 + API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Alpaca integration exposes
The Alpaca Agent App exposes 22 provider-backed actions for finance and data work. Its current contract lets an authorized agent get alpaca trading api account details for the connected paper or live account, get alpaca account configuration values, and get alpaca account equity and profit/loss time series. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0 and API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Alpaca account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Alpaca capabilities.
Showing 12 of 22 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_accountREADGet Alpaca Trading API account details for the connected paper or live account.
get_account_configREADGet Alpaca account configuration values.
get_account_portfolio_historyREADGet Alpaca account equity and profit/loss time series.
INPUTS: period / timeframe / intradayReporting / start / end
get_assetREADGet one Alpaca asset by symbol or asset ID.
INPUTS: symbolOrAssetId
get_crypto_barsREADGet historical OHLC crypto bars from Alpaca Market Data API.
INPUTS: symbols / timeframe / location / start / end
get_crypto_snapshotsREADGet latest crypto snapshots from Alpaca Market Data API.
INPUTS: symbols / location
get_market_calendarREADGet Alpaca Trading API US market calendar days.
INPUTS: start / end / dateType
get_market_clockREADGet Alpaca Trading API US market clock information.
get_option_contractREADGet one Alpaca option contract by contract symbol or ID.
INPUTS: symbolOrId
get_orderREADGet one Alpaca order by order ID or client order ID.
get_positionREADGet one open Alpaca position by symbol or asset ID.
INPUTS: symbolOrAssetId
get_stock_barsREADGet historical OHLC stock bars from Alpaca Market Data API.
INPUTS: symbols / timeframe / start / end / limit
INPUT CONTRACTS
Know what the action needs before it runs.
get_account_portfolio_history
periodOPTIONAL- Duration such as 1D, 1W, 1M, or 1A.
timeframeOPTIONAL- Time window size such as 1Min, 5Min, 15Min, 1H, or 1D.
intradayReportingOPTIONAL- Intraday reporting mode.
startOPTIONAL- A date or RFC-3339 timestamp accepted by Alpaca.
endOPTIONAL- A date or RFC-3339 timestamp accepted by Alpaca.
get_asset
symbolOrAssetIdOPTIONAL- Asset symbol or asset ID.
get_crypto_bars
symbolsREQUIRED- A non-empty list of symbols.
timeframeREQUIRED- Bar aggregation timeframe such as 1Min, 1Hour, or 1Day.
locationOPTIONAL- Crypto market-data location.
startOPTIONAL- A date or RFC-3339 timestamp accepted by Alpaca.
endOPTIONAL- A date or RFC-3339 timestamp accepted by Alpaca.
get_crypto_snapshots
symbolsREQUIRED- A non-empty list of symbols.
locationOPTIONAL- Crypto latest market-data location.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account
Get Alpaca Trading API account details for the connected paper or live account. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_accountVerify with Get Account Config
Get Alpaca account configuration values. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_account_configSAFETY BOUNDARY
Operate Alpaca with explicit limits
- Authorize Alpaca with OAuth 2.0 and API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Alpaca data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- The sampled contract declares provider scopes including `data`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Alpaca task completed successfully.
CONNECTION MODEL
OAuth 2.0 + API key
Alpaca API secret key sent with the APCA-API-SECRET-KEY header. Generate paper or live API keys from the Alpaca dashboard API Keys page: https://app.alpaca.markets/paper/dashboard/overview
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 22
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Alpaca.