Documentation

Astral MCP

Astral’s remote Model Context Protocol endpoint lets a compatible AI client connect to Astral after you authorize access. The public setup page is available at Astral MCP.

Endpoint

Remote endpoint available 
https://stream.astral-prod.heyastral.ai/api/mcp

Use a streamable HTTP or remote MCP server configuration named astral. The client should open Astral’s sign-in and consent flow when authorization is required.

Client setup

  1. Add the remote server

    Use the client-specific installer or add the endpoint to the client’s MCP configuration. The MCP setup page provides current instructions for ChatGPT, Claude, Cursor, Codex, Gemini, and generic compatible clients.

  2. Sign in to Astral

    Complete the browser sign-in flow with the Astral account whose data and entitlements you intend to use.

  3. Review and approve consent

    Read the requested access before approving it. Decline or close the flow if the client or requested connection is unfamiliar.

  4. Confirm the connection in your client

    Return to the client and check its server or tools status. Tool availability can depend on your Astral account, current rollout, and the client’s MCP implementation.

Command examples

Choose your client to see a copyable setup command or configuration.

Terminal command
codex mcp add astral --url https://stream.astral-prod.heyastral.ai/api/mcp

Security and troubleshooting

  • Only authorize clients you trust.
  • Treat actions involving strategies, alerts, or trading as consequential and review them in Astral.
  • If authorization stalls, remove the server from the client, add it again, and complete sign-in in the newly opened browser flow.
  • If the server connects but a capability is unavailable, check your Astral plan, feature access, and the client’s support for remote OAuth MCP servers.
  • Disconnect the integration from the client if a device or configuration is no longer trusted.

What the connection means

MCP is a protocol connection between a compatible client and Astral’s remote server. It does not copy your entire Astral account into the client. The available tools and data remain subject to the authorized account, Astral feature access, server rollout, and the client’s implementation.

Adding the server configuration identifies the endpoint. Signing in identifies the Astral account. Approving consent authorizes the requested connection. These are distinct steps, and removing only the text configuration may not be equivalent to revoking an existing authorization in every client.

Use MCP safely

  • Verify the endpoint exactly before authorizing.
  • Read the client’s tool confirmation and Astral consent screens.
  • Use an Astral account appropriate for the work context.
  • Review consequential output in Astral, especially strategies, alerts, orders, or account-related state.
  • Remove or revoke connections on lost, shared, or untrusted devices.
  • Never paste an Astral password or one-time code into an ordinary chat message.

An AI client can misunderstand a request or choose the wrong available tool. Phrase instructions with the same specificity you would use in Terminal: symbol, interval, dates, intended record, and whether the request is research-only.

Multiple clients and accounts

Each client can store server configuration and authorization differently. If you use more than one client, do not assume disconnecting one removes the others. Confirm which Astral account completed each consent flow.

When switching accounts, remove the existing server authorization or sign out through the client’s supported flow before reconnecting. A stale authorization can make an account mismatch look like missing product data.

Diagnose a connection

No browser authorization opensThe client may not support remote OAuth MCP correctly.
Confirm the server uses streamable HTTP and the exact endpoint. Remove the configuration, add it again, and check the client’s MCP logs or server status.
Authorization completes but tools are missingTool visibility can depend on account access and rollout.
Confirm the account used in the browser, refresh the client’s server list, and compare with the current Astral feature-access state.
The client shows disconnectedConfiguration, network, authorization, or client state may have expired.
Reconnect once. If the state remains ambiguous, remove the server, restart the client where appropriate, and complete a fresh authorization flow.
The wrong Astral account appearsA browser or client may have reused an existing session.
Disconnect the server, sign out of the unintended Astral account, and repeat authorization with the intended account. Review active client connections afterward.

Reporting an MCP issue

Include the client name and version, operating system, endpoint, stage that failed, approximate time, and non-sensitive error text. Do not include access tokens, authorization codes, passwords, or complete request headers.