Integrate Seamward

API overview

Choose the supported interface for sending data to or reading data from Seamward.

Two interfaces, separate credentials

Use the ingestion API to send redacted observations from a backend. The read-only MCP pilot lets an authorized client inspect one workspace through an explicit OAuth grant.

Ingestion API

Send redacted observation batches from a backend application.

Use POST /ingest to send redacted observation batches from a backend service. Authenticate with a secret ingest token created for the workspace application environment.

The ingestion credential is write-only. It cannot read workspace data, incidents, repairs, members, or settings.

Available: backend observation ingestion
Available: Node.js collector and direct REST delivery
Not exposed: the session-cookie endpoints used by the Seamward console

MCP

Connect an authorized client to the read-only MCP pilot.

Connect an MCP client to the deployment value of MCP_PUBLIC_URL; the URL must end in /mcp. Local development uses http://127.0.0.1:4200/mcp by default.

The pilot exposes workspace overview, integration, incident, replay, repair proposal, and approved repair export data through stateless Streamable HTTP.

Available in pilot: OAuth authorization code with PKCE
Available in pilot: 8 read-only tools, 6 resource patterns, and 2 prompts
Available in pilot: connected-client review and immediate revocation in Workspace settings

Authentication boundaries

Use a credential that matches the interface and its permitted actions.

Do not reuse a browser cookie or an ingest token in an MCP client. These credentials serve different trust boundaries and are not interchangeable.

Ingest token: backend-only, write-only observation delivery
Browser session: Seamward console access for a signed-in user
MCP access token: short-lived, audience-bound, workspace-scoped read access with explicit scopes