MCP overview

The Seamward MCP server gives an AI client access to one workspace mode and a reviewed connection set. Access is read-only unless you also approve the one scope that lets a client submit a repair candidate for your team to review. The server enforces that selection on every request. Browser consent binds the selected Test or Live mode and exact connections before approval.

Invitation-only access

The Seamward MCP server is available to invited workspaces at https://mcp.seamward.com/mcp, and the interface may change before broader access. See current availability for the supported connection and service boundaries.

What you can do

After connecting, ask your client questions like these:

"Which of our integrations have open incidents right now?"
"Summarise the newest incident and the evidence behind it."
"Did replay validation pass for the payout-webhook repair proposal?"
"Fetch the approved repair bundle for proposal rep_7f3k2m and prepare a local patch from it."

The client answers by calling Seamward's read tools. The resources and tools reference lists every tool with its parameters and example results.

Requirements

A Seamward account with membership in the workspace you want to connect. Your role does not matter for connecting a client that reads. Only an owner or admin can grant a client the scope that submits a repair candidate.
The hosted MCP server URL: https://mcp.seamward.com/mcp. If your workspace uses a custom deployment, use the URL provided during onboarding instead.
An MCP client that supports Streamable HTTP and OAuth. Connection instructions below cover ChatGPT web, Codex desktop/CLI/IDE, Claude Code, Claude, and Cursor. Check current availability for the distinction between documented configuration and verified Seamward compatibility.

This hosted workspace MCP does not need an API key, ingest token, or any other manually copied credential. Authorization happens entirely through your browser sign-in. Never paste a Seamward ingest token or browser cookie into this hosted MCP client; the server does not accept them.

The local coding-agent setup MCP is a different server. It changes and verifies one codebase and uses its own browser authorization bound to one exact workspace environment. It previews the exact Integrations it will create or reuse before any remote write. See automatic setup for the one-command project installation.

Client configuration

The following client settings start the reviewed browser consent flow. Invitation access and service boundaries are described in current availability.

Use https://mcp.seamward.com/mcp in the client examples below. Custom deployments use their onboarding URL instead. Knowing the endpoint does not grant access; complete browser authorization for an invited workspace.

ChatGPT (web)

Use a custom remote MCP app in an eligible ChatGPT account. Availability and workspace administrator permissions determine whether the creation controls appear.

Enable Developer mode in ChatGPT settings. OpenAI currently documents Settings → Security and login; workspace policy can restrict access.
Open ChatGPT Plugins, select the plus button, and create a developer-mode app named Seamward.
Enter https://mcp.seamward.com/mcp, choose OAuth, and use dynamic client registration if offered. Seamward supports that registration flow; you do not supply an ingest token, API key, or OAuth client secret.
Complete the Seamward browser consent below, then finish creating the app.
Select Seamward in the chat's tools/app picker and ask: "Use Seamward's get_workspace_overview to show my authorized workspace."

If creation is unavailable or registration fails, ask your workspace administrator or Seamward onboarding contact. Do not bypass OAuth. See OpenAI's developer-mode instructions for current eligibility and controls.

This connects the hosted server with read scopes. It does not install a collector or give a ChatGPT web conversation access to your local project.

Codex (desktop, CLI, and IDE extension)

Add the hosted server and start browser authorization using the Codex CLI:

Code example

codex mcp add seamward --url https://mcp.seamward.com/mcpcodex mcp login seamwardcodex mcp list

These are Codex commands; installing the Seamward CLI is unnecessary for hosted MCP access. Alternatively, add this entry to ~/.codex/config.toml, then authenticate the server in your client's MCP settings or with codex mcp login seamward:

Code example

[mcp_servers.seamward]url = "https://mcp.seamward.com/mcp"

Codex desktop, CLI, and IDE clients share this configuration. Restart or reload your client after changing it. Ask Codex to call get_workspace_overview and confirm the workspace and selected connections. See OpenAI's MCP configuration guide.

Use seamward for hosted evidence access and seamward-setup for the separate local setup server. Connecting the hosted server does not provision an Integration or instrument code. Follow automatic setup for today's local coding-agent workflow.

Claude Code

Add the server from your terminal:

Code example

claude mcp add --transport http seamward https://mcp.seamward.com/mcp

Then run /mcp inside Claude Code and choose seamward to start authentication. Your browser opens the Seamward approval flow described below.

Claude (web and desktop)

Open Settings, then Connectors, then choose Add custom connector. Name it Seamward, paste https://mcp.seamward.com/mcp, and save. Claude starts the browser approval flow the first time you use the connector.

Cursor

Add the server to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for all projects):

Code example

{  "mcpServers": {    "seamward": {      "url": "https://mcp.seamward.com/mcp"    }  }}

Cursor shows a Needs login state for the server; click it to start the browser approval flow.

Other Streamable HTTP and OAuth clients may be compatible. Follow their registration instructions and verify a tool call before relying on the connection; protocol support alone is not a Seamward compatibility test.

Approve access

Approve access through this browser flow:

Your browser opens the Seamward sign-in page. Sign in with your verified account.
Seamward shows the consent screen. Choose one workspace, one mode, and the exact connections this client may read. An empty selection grants no connection evidence.
Review the requested read scopes. The authorization page explains exactly what each scope unlocks.
Choose Allow only after the screen confirms that exact selection. The client then receives a short-lived access token bound to it.

Access tokens expire after 15 minutes. Clients that request offline access can store a refresh token and refresh access in the background; otherwise the client asks you to approve again when the token expires. OAuth tokens are managed by the client and must not be pasted into prompts or application configuration. They are separate from collector credentials.

Verify the connection

Ask the client for a workspace overview, for example: "Give me an overview of my Seamward workspace." The client calls the get_workspace_overview tool and receives a result like this:

Code example

{  "schemaVersion": "seamward.mcp/1",  "workspace": {    "id": "wks_2ac9017e",    "name": "Acme",    "slug": "acme"  },  "data": {    "tenant": { "id": "ten_4b7e2f81", "name": "Acme" },    "integrations": 4,    "incidents": { "open": 1, "total": 7 },    "latestObservationAt": "2026-08-14T18:22:31.000Z"  }}

The connection also appears under Workspace settings → MCP with its reviewed mode, connection set, scopes and connection date. That page is also where you revoke access. A changed mode or connection set requires a new review; a removed connection invalidates the previous selection.

Troubleshooting

ChatGPT has no app creation control. Check Developer mode and workspace policy with your administrator. An eligible account and permission to create custom apps are required. Ordinary chat access does not establish that access.

Codex lists the server but its tools are unavailable. Run codex mcp login seamward, complete browser consent, and reload your client. If registration fails, share the error with your onboarding contact without including tokens. Do not substitute a collector credential for OAuth.

The client reports unauthorized or a 401. The access token has expired and the client has no refresh token, or the client's access was revoked in Workspace settings → MCP. Reconnect the client and approve again.

A tool call returns forbidden. The grant does not include the scope that tool needs. This is most common with get_approved_repair_bundle, because the export scope is not part of the default request. Reconnect and approve a request that includes seamward:repairs:export.

A tool call returns not_found. The id is outside the reviewed workspace, mode, or connection set, or no longer exists. The server does not reveal which case applies. Check the reviewed selection and renew authorization if the client needs another mode or connection.

The server does not appear in the client. Check the URL is exactly the one from onboarding, including the /mcp path, with no trailing slash. Opening the URL in a normal browser tab returns a method_not_allowed error; that is expected and confirms the server is reachable, because the server only accepts POST /mcp requests from MCP clients.

Analysis health

Integration list and detail tools include the same structuralAnalysis and behavioralAnalysis state as the Workspace API. A connection with observations and no open incidents can still have structural or behavioral analysis paused. Check status, lastSuccessAt, and the capacity code before describing a connection as healthy. See structural capacity recovery and behavioral capacity recovery for limits and recovery behavior.

Next steps

Resources and tools: every tool, resource, and prompt with parameters and examples.
Authorization: scopes, token lifetimes, revocation, and the safety boundary.
Current availability: supported capabilities and current service boundaries.