Current availability
The Seamward MCP server is available to invited workspaces. This page states what the current release supports and the service boundaries that still apply.
Reviewed access
Browser consent selects one workspace, Test or Live, and an exact connection set before OAuth approval. An empty selection grants no connection evidence. Newly created connections are not silently added to an existing grant.
Included with invitation access
- Streamable HTTP transport, automatic client registration, and exact-scope browser consent.
- The read tools, 6 resources, and 2 prompts described in the reference, and the one tool that writes,
submit_repair_candidate. - Exact workspace, mode and connection grant enforcement, scope enforcement, membership revalidation, and audience-bound 15-minute tokens on every request.
- The connected-clients screen in Workspace settings → MCP, with immediate revocation.
- Approved repair bundle export: the manifest, the readable report, and the TypeScript patch.
Client connection guidance
The MCP overview includes ChatGPT web and
Codex desktop, CLI, and IDE connection instructions alongside Claude and
Cursor. ChatGPT and Codex configuration is documented from official OpenAI
guidance, but these clients are not yet individually verified with Seamward.
Verify browser consent and a get_workspace_overview call with your invited
workspace before relying on either connection. Report registration or tool
discovery errors to your onboarding contact without sending credentials.
ChatGPT web connects to the hosted server. Codex can also use the separate local setup MCP through automatic setup. Hosted access currently exposes read tools only; the proposed hosted onboarding and management write tools are planned and unavailable in this release.
Not yet available
- Self-service MCP access for every workspace. The hosted endpoint is
https://mcp.seamward.com/mcp; workspace access still requires an invitation and browser authorization. - A published compatibility matrix for desktop, CLI, and IDE clients. Configuration examples are guidance, not certification of a particular client version. Confirm OAuth and tool access with your invited workspace.
- Uptime or support commitments. The invitation-only release does not include a service-level agreement.
- Hosted write tools. Approval and GitHub delivery stay in the console with an approval decision. Merge and deployment require their separate reviewed workflows. Local coding-agent setup is a separate capability, not a hosted write tool.
Next steps
- MCP overview: connect an authorized client.
- Authorization: the grant model behind the isolation guarantees.
