Read your Alpaca Trading API account summary, open positions and an existing order. Bind paper or live credentials explicitly in the connection. This subset performs three read operations and never trades, cancels orders, changes settings or polls market data. API key authentication is separate from Alpaca Broker and managed OAuth.
What you can do (3)
What you can do
Available commands: 3 (3 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
Read trading account summary — alpaca.account.get |
Read |
Read open position summaries — alpaca.positions.list |
Read |
Read an order summary — alpaca.orders.get |
Read |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for Alpaca, then enter the issued values in the connection form below.
- In your Alpaca Trading Dashboard choose Paper or Live, open API Keys and generate an API key ID and secret for that account. Copy the secret when shown. Enter the matching Alpaca environment, Alpaca API key ID and Alpaca API secret key in this connection. Paper and live credentials cannot be interchanged. Start with paper and account.get, select only the read commands you need and save, then create a scoped Tooluse.net API key. An existing order UUID is required for orders.get. Provider keys may grant trading permissions although these commands only read; rotate or revoke them in Alpaca and replace the values here. Broker client credentials and managed OAuth are not supported by this form.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| Alpaca environment | Required |
| Alpaca API key ID | Required |
| Alpaca API secret key | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
Read trading account summary — alpaca.account.get
Read account UID, status, currency and available balance fields from the explicitly selected paper or live Trading API. Account numbers and personal details are omitted. This never submits trades or changes account settings.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
This tool has no input parameters.
Full JSON Schema
Example input
{}
At most 1 provider requests per invocation; timeout: 30 seconds.
Read open position summaries — alpaca.positions.list
Read currently open positions for the selected account, including asset UUID, symbol, quantity, side and available valuation fields. The provider endpoint has no pagination parameters; one response is bounded by the existing 512 KiB transport limit. It does not close positions or subscribe to price data.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
This tool has no input parameters.
Full JSON Schema
Example input
{}
At most 1 provider requests per invocation; timeout: 30 seconds.
Read an order summary — alpaca.orders.get
Read one existing order by its Alpaca UUID in the selected account. Returns its status, symbol, side, quantities and available price/timestamp fields. Client order metadata is omitted. This never places, replaces or cancels an order.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.order_id |
string | Required | Alpaca order UUID belonging to the selected account. | format: "uuid" |
Full JSON Schema
Example input
{
"path": {
"order_id": "6ee704d9-ee24-4c36-b1a6-cb8ccf6a216c"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.