Skip to main content

Integrating AI agents

AutoSat supports the industry standard Model Context Protocol (MCP), allowing compatible AI agents to access data from your workspaces and assist operations in AI powered workflows. AutoSat does not feature any AI capability embedded within the product. The choice to integrate an AI agent is entirely within your control.

Once connected, you can ask your agent questions like:

  • “What’s the best pass for my-sat over the next 24 hours?”
  • “Is my-sat reachable right now, and what’s its latest battery voltage?”
  • “Summarize the console activity for my-sat since yesterday’s pass.”
  • “Plot battery_voltage for my-sat over the last week.”
note

MCP access requires a plan that includes API access (Pro or Enterprise). If you don’t see MCP connections in your workspace settings, check your organization’s plan.

What an agent can do​

AutoSat’s MCP access is read only. An agent can look up information about your workspace, but it cannot send commands, run workflows, or change any configuration.

ToolWhat it does
get_workspaceReports the workspace, organization and permission level the connection is using.
list_satellitesLists the satellites in the workspace, with their most recent TLE.
list_ground_stationsLists the ground stations in the workspace.
get_upcoming_passesLists upcoming passes, soonest first, optionally filtered by satellite and/or ground station.
get_pass_polar_plotRenders the polar az/el plot of a pass — the same chart shown in the console.
get_satellite_statusReports live status: ping reachability, ground station agent connectivity and latest telemetry.
get_telemetry_historyRetrieves recorded values over time for a telemetry field, optionally within a time range.
get_console_logsRetrieves recent console history: commands sent, their output, workflow events and received packets.

Satellites can be referred to by their slug (e.g. my-sat) or UUID, so you can name them naturally when talking to your agent.

Connecting an AI agent to AutoSat​

To connect a compatible AI agent you will need to provide it with your workspace’s MCP endpoint. MCP access is configured per workspace and uses the same permissions as the user who authorizes the connection.

1. Find your workspace’s MCP endpoint​

  1. Open the workspace you want to connect and go to Settings.

  2. Select MCP connections.

  3. Copy the URL shown under Workspace MCP endpoint. It looks like:

    https://example.autosat.space/mcp/workspace/unistar
The Workspace MCP endpoint card, showing the endpoint URL and a copy button

Each workspace has its own endpoint. To give an agent access to more than one workspace, add a separate connection for each.

2. Add the endpoint to your AI agent​

How you add an MCP server depends on your agent. AutoSat uses the Streamable HTTP transport with OAuth sign-in, so any client supporting remote MCP servers can connect directly — no API keys or local proxy required. Instructions for some popular agents follow; menus change from time to time, so check your agent’s own documentation if a step doesn’t match what you see.

In claude.ai or Claude Desktop:

  1. Open Settings → Connectors.
  2. Choose Add custom connector.
  3. Give it a name (e.g. AutoSat – Operations) and paste the MCP endpoint as the URL.
  4. Select Connect.

All of AutoSat’s tools are marked read-only, so agents that ask for approval before actions that make changes generally won’t ask before calling them.

3. Authorize the connection​

When the agent first connects, a browser window will open to AutoSat:

  1. Sign in to AutoSat if you aren’t already.
  2. Review the request. AutoSat shows which app is asking for access, and to which workspace and organization, along with the account it will act as.
  3. Select Approve to grant access, or Deny to refuse.
AutoSat's authorization screen asking whether to allow Claude to access the UniStar workspace, with Deny and Approve buttons

You’ll be returned to your agent, which can now use AutoSat’s tools. A good first check is to ask it “Which AutoSat workspace are you connected to?”.

Permissions and data access​

An agent acts on your behalf, and sees only what you can see in the workspace:

  • A connection is bound to the single workspace it was authorized for. It cannot reach other workspaces, even ones you have access to.
  • Restricted users (such as customer roles) only see console activity for the subsystems they have been granted access to.
  • Telemetry is only available if your account can read telemetry in the workspace.
  • If your access to the workspace is removed, or your organization’s plan no longer includes API access, the connection stops working.
warning

Data returned by AutoSat — telemetry, console logs, pass predictions — is sent to your AI agent and its provider. Make sure your use of AI tools complies with your organization’s data handling policies before connecting.

Managing connections​

The MCP connections page in workspace settings lists the apps that have been authorized to access the workspace.

The MCP connections settings page, listing a connection from Claude with its user, last active time, and a Revoke button
  • Users see the connections they have authorized themselves.
  • Workspace admins see every user’s connections.

Select Revoke next to a connection to remove it. The app immediately loses access and will need to be authorized again before it can reconnect.

Connections stay signed in while they’re in use. If one is left unused for an extended period (around 90 days) you’ll be asked to authorize it again.

Troubleshooting​

I can’t find MCP connections in settings.
Your organization’s plan may not include API access. Contact your organization’s administrator.

The agent says it’s unauthorized, or keeps asking me to sign in.
The connection may have been revoked, or your access to the workspace changed. Remove the server from your agent and add it again to re-authorize.

The agent can’t see any AutoSat tools.
It most likely hasn’t signed in. Most agents prompt you to sign in when they first connect; if yours doesn’t, look for an option to authenticate or log in to the server. For Codex, run codex mcp login autosat.

The agent reports “Too many requests”.
Each connection is limited to 60 requests per minute. Wait a minute and try again — interactive use rarely reaches this limit.

The agent can’t find a satellite or telemetry field.
Ask it to list the satellites in the workspace first, or to check the satellite’s status to see which telemetry fields currently have values. Confirm it’s connected to the workspace you expect using get_workspace.