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.
- All 8 read-only tools, 6 resources, and 2 prompts described in the reference.
- 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.
Not yet available
- A public self-service MCP URL. Invited workspaces receive their server URL during onboarding.
- A published compatibility matrix for desktop, CLI, and IDE clients. Claude Code, Claude, and Cursor are exercised today; other streamable HTTP clients are expected to work but are not yet individually verified.
- Uptime or support commitments. The invitation-only release does not include a service-level agreement.
- Write tools of any kind. Approval, GitHub delivery, merge, and deployment stay in the console with an approval decision, and there is no timeline for changing that.
Next steps
- MCP overview: connect an authorized client.
- Authorization: the grant model behind the isolation guarantees.
