Shipswiftcomponents MCP

What the shipswiftcomponents-mcp MCP server does

The shipswiftcomponents-mcp MCP server provides a remote interface to ShipSwift component workflows. It is delivered as a paid hosted service rather than as source code that you run locally. The public repository documents the service and its directory submission; it does not contain the private production implementation.

The service exposes four MCP tools:

• search_swiftui_component for searching SwiftUI components.
• generate_component_patch for generating a component patch.
• validate_dependency_policy for validating dependency policy.
• export_component_receipt for exporting a component receipt.

The surrounding service is designed to provide structured receipts, usage logs, and JSON evidence suitable for audit-oriented workflows. The available material does not specify the request fields, response schemas, component catalog, or policy rules for these tools, so those details should be confirmed through the product documentation or server metadata.

How it works

The hosted MCP endpoint is available at https://shipswiftcomponents.clauxel.com/mcp. An MCP client sends JSON-RPC requests to that endpoint using Streamable HTTP. Each production request must include a bearer token in the HTTP authorization header:

Authorization: Bearer <token>

Unauthenticated browser requests to the endpoint return a JSON error rather than exposing internal service details. This behavior does not replace authentication for production tool calls; clients still need a valid token.

The service also publishes a server card at https://shipswiftcomponents.clauxel.com/server-card.json. The registry name is com.clauxel.shipswiftcomponents/shipswiftcomponents-mcp.

Setup and configuration

To use the shipswiftcomponents-mcp MCP server, choose a plan on the product website and create or request an API token. Add the MCP endpoint to a client that supports remote Streamable HTTP servers, then configure the client to send the token as a bearer credential. The README does not define a local command, package installation, Docker image, or required environment variable.

The product page and pricing information are available at the hosted website. Because access is paid and token-based, deployment decisions should account for subscription access and credential handling. The repository itself is not the production service, so cloning it will not provide a local equivalent of the endpoint.

Tools and capabilities

The shipswiftcomponents-mcp MCP server groups its exposed capabilities around four operations: finding SwiftUI components, producing patches, checking dependency policy, and exporting receipts. These operations can support an agent workflow that starts with component discovery, evaluates dependency constraints, produces a change, and records an output artifact. The README lists the operations but does not document whether they must be called in that order or what inputs each accepts.

Receipts, usage logs, and audit-ready JSON evidence are part of the hosted service description. If a workflow requires a particular receipt schema, retention period, validation rule, or patch format, verify that behavior before integrating it into automation.