MCP documentation

The MCP adapter is published. Package @shiproom/[email protected]. Production-verified with Codex CLI.

How it fits

A reviewer marks an issue on the live UI. Shiproom captures the contextual evidence. Compatible coding agents can then inspect that feedback packet through MCP and implement the change. Shiproom does not edit your repository or claim to fix issues on its own. See the Model Context Protocol specification for the underlying protocol.

Run the adapter

Create a personal token with the published [email protected] CLI, then start the adapter:

SHIPROOM_TOKEN='shr_mcp_...' \
SHIPROOM_API_URL='https://api.shiproom.live' \
npx -y @shiproom/mcp

Codex CLI is the directly verified end-to-end client. Cursor, Claude Code, and other MCP clients can use the same generic stdio contract, but Shiproom does not publish them as directly verified without a recorded end-to-end run. The environment variables above are the adapter inputs; only each client's registration command differs. Codex CLI:

codex mcp add shiproom \
  --env SHIPROOM_TOKEN="$SHIPROOM_TOKEN" \
  --env SHIPROOM_API_URL=https://api.shiproom.live \
  -- npx -y @shiproom/mcp

Package on npm: @shiproom/mcp.

Token management

The published [email protected] CLI creates, lists and revokes account-scoped personal tokens for the feedback-focused MCP adapter:

shiproom mcp setup "Local coding agent"
shiproom mcp token create "Local coding agent" --expires-in-days 90
shiproom mcp token list
shiproom mcp token revoke <token-id>
SHIPROOM_TOKEN='shr_mcp_...' shiproom mcp test

Token creation displays the secret exactly once. Shiproom stores only a one-way hash and the token's metadata, and listing never reveals a full token value. Revoke any token that may have been exposed. Never put a token in a repository, a URL, an issue or a ticket.

What the commands do

shiproom mcp setup verifies your normal Shiproom session, creates a personal token, and prints client configuration. It does not edit any third-party configuration file.

shiproom mcp test performs a real, read-only check of token format, API connectivity, personal-token authentication and account access. It does not launch the adapter and does not claim to discover tools at runtime.

Tools

The adapter exposes shiproom_list_projects, shiproom_list_feedback, shiproom_get_feedback, and shiproom_update_feedback_status. A feedback packet can include project context, page path and title, selected DOM element metadata, accessible name, CSS selector, computed styles, parent chain, viewport, browser and OS, visual annotations, screenshot metadata, an attachment endpoint, and deterministic Markdown. The adapter never reads a repository, runs shell commands, or calls an AI model.

Verified clients

Production end-to-end verification on 2026-08-09 covered personal-token creation, authentication against production, project and feedback listing, full contextual feedback retrieval, token revocation, and rejection of a revoked token. The recorded run used Codex CLI. Other agents that speak the same generic stdio contract may work, but are not presented here as directly tested.

This is a compatibility result and nothing more. Shiproom has no partnership with, and no endorsement or certification from, the vendors of those clients.

Exports still work without MCP

Deterministic Markdown and JSON exports already work with any tool that reads text. See the CLI documentation for shiproom feedback export.

Shiproom prepares the task; it does not read your source code and does not change your code. Questions: [email protected].