Skip to main content

Integrations: data in, results out, API and MCP

Integrations is where Constellation meets your systems: what sends data in, where workflow results go out, and the keys and MCP server your own code and agents use. The page is three panes side by side: Connections on the left, Flow in the middle, and on the right the connection you chose or, with none chosen, Telemetry.

Connections​

One list of every connection the account has, in three groups:

GroupRows
Data inThe Fleet agent, once anything reports through it, with how many of your own antennas and satellites reported in the last five minutes ("2 of 5 reporting"); with only a key made for it, Key made, no agent reporting yet. The demo fleet's assets and simulated telemetry are never counted. Its keys are under it, not with the API keys
Results outEach mission control system (MCS) a bridge reads as or a workflow sends to, each custom connector, and each destination
API and MCPYour keys in this workspace, other than the fleet agent's, and the MCP server. Create key, on its heading, opens the key form with every permission to choose

Each row is a dot, a name and one quiet line, with its last activity at the right. The marker says it by shape as well as color: a green dot when it works, an amber triangle when it needs a look, a red cross when it failed and a gray ring when there is nothing to say yet. A row's name is read with its status word, such as "Yamcs, needs a permission". The title row counts them ("3 fine · 1 needs a look"). A read that fails says it could not be read rather than that a group is empty. Choose a row anywhere to open it on the right; Escape closes it.

A bridge is heard from each time it reads the feed (every 15 seconds by default) or checks in. One not heard from for five minutes reads Quiet, here, on Automations and in the bell alike.

A link to a group (/integrations?view=in, ?view=out, ?view=api, or an older #results-out or #developer) lands on that group.

Add connection, at the foot of the list, asks what kind:

ChoiceOpens
Fleet agentIts detail: Create a key for the fleet agent (with telemetry:write, topology:read and config:{read/write} ticked; the secret shows once), then its install steps. See Fleet agent
Pass log uploadPass logs: a CSV of flown passes, for an audit. Download the CSV template gives one with your own ids; a log with a bad row writes nothing. Then run the audit on Passes, under Past, Audit
OpenC3 COSMOS, Anduril Lattice, YamcsIts detail: Send, Key and Install its bridge (below). Once Create its key has made the bridge's key, the system is a row under Results out and a node on the Flow, reading Key made, no bridge reading yet until the bridge starts
Open MCTTwo ways. Read the API directly: send a workflow to Open MCT (its openmct connection), Create its key, which reads results and nothing else (results:read), and load one file into your Open MCT page. Or read through Yamcs: with the Yamcs connector set up, its plugin reads what the bridge writes and needs no key
Your own connectorCreate its key and the steps to build a bridge for any other system. Once it checks in, it is a row Waiting for approval: open it to read what it asks for, then Approve or Remove. It receives your results only once approved
Grafana Cloud, Amazon S3, WebhookThe destination's connect form; see Results out. Once connected it opens on the right, with Send filled in
API keyNew key asks what the key is for and opens the form with its scopes ticked (below). Live and test keys are both listed under API and MCP, a test key marked Test key, and each can be revoked from its detail
MCP clientThe MCP server detail

Plans: a mission control output to Yamcs, Open MCT or your own connector, and every destination, need Operator; Lattice and COSMOS need Enterprise, as their choices say. Test runs and scenario runs send nothing to any of them.

Flow​

How data moves for this account: Data in on the left (the fleet agent, and Pass logs), Constellation in the middle with how many workflows you have, and Results out on the right (each MCS, custom connector and destination, then API and MCP with how many live keys). Each node has its dot and one line; choose one to open it on the right. A link data moves along now (records arriving, a bridge reading, deliveries going out) carries moving orange dashes; the rest stay still and gray, and with reduced motion a live link stays orange without moving. On a narrower window the flow sits under the list.

Until an account has done all five setup steps, Get set up sits at the head of the flow and counts how many are done. The steps run in order, joined by arrows (down the card on a phone), with the step to take now marked. A step made on another tab links to it (Open Fleet, Open Automations); a step made here opens its picker (Create a key, Open the fleet agent, Add connection). Any live key that has not expired completes the key step; Create a key opens New key, which asks what the key is for. Once every step is done the checklist is gone for the workspace, and a pause in telemetry does not bring it back. The steps are in Onboarding. Questions go to contact@constellation.space, as it says.

The detail pane​

With a connection chosen, the right pane shows it as label and value pairs, then its groups:

  • Fleet agent: Reporting (your own antennas and satellites with a record in the last five minutes, with See each on Fleet), Quiet, Last record, then Set up. The demo fleet is left out of all three.

While the workspace holds the demo fleet, the line under the top bar labels it here too, and Telemetry leaves out the demo's records and says so: "The demo fleet's simulated telemetry is not counted here."

  • A mission control system: Status, Bridge, Last read, Checked in, From and Version, and the one thing wrong in a sentence when something is. Send: pick a workflow (the one that already sends to it, else the one that prices passes) and Send it to the system, which saves a new version with a mission control output. Key: Create its key, with predictions:read (Lattice also config:read). Install its bridge: the steps and files, and its install guide. Downloads come from the public connectors releases.
  • A destination: Send, as for a system, which adds a destination output naming it; then its status, where it sends, its last delivery, Send a test and Remove, and for Grafana Cloud Download dashboard.
  • A key: its prefix, when it was created, last used and expires, its scopes, and Revoke.
  • MCP server: the snippet that adds the Constellation MCP server to your client with one of your keys, Setup guide, the tools your agent gets, what to try asking, and API activity (when a live key last reached the API). See AI agents and MCP.

With nothing chosen, Telemetry lists the newest record from each source, newest first: its time, the antenna and satellite, and how many fields it held. It covers the last five minutes, keeps the newest 50 and refreshes while the page is open.

New keys start from what the key is for:

ForScopes
Fleet agenttelemetry:write, topology:read, config:{read/write}
Mission control bridgepredictions:read (a Lattice bridge's own key also config:read)
MCP clienttopology:read, predictions:read, config:{read/write}, telemetry:write, workflows:write, so it can also load the demo fleet
Your own scriptspredictions:read, workflows:write
Open MCT in a browserresults:read: reads results and nothing else
Approve actions from your own toolspredictions:read, act:approve

config:{read/write} is the API's config:write, which also reads the network config. Every scope is in Auth and scopes. Only the last takes act:approve, for deciding held recommendations from a script or an agent. On Passes you decide with your sign-in, which holds it: no key needed.

In the API​

On screenCall
Fleet agent, TelemetryGET /topology
A pass logPOST /telemetry/pass-logs
Bridge status and last readGET /predictions/feed/readers; see the results protocol
Custom connectors, Approve, RemoveGET /predictions/connectors, POST /predictions/connectors/{name}/approve, DELETE /predictions/connectors/{name}
Send an automation to a system or a destinationPUT /predictions/workflows/{slug} with a mission control or destination output; see the node reference

Next: connect your mission control system.