ShipSwift Component MCP

ShipSwift Component MCP remote MCP for ShipSwift.

Paid remote MCP for ShipSwift, structured receipts, usage logs, and audit-ready JSON evidence.

Public Endpoints

• Website: https://shipswiftcomponents.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605r26_224703
• MCP endpoint: https://shipswiftcomponents.clauxel.com/mcp
• Server card: https://shipswiftcomponents.clauxel.com/server-card.json
• Registry name: com.clauxel.shipswiftcomponents/shipswiftcomponents-mcp

Access

This is a paid hosted remote MCP. Production calls require a bearer token issued from the product website.

Authorization: Bearer <token>

Unauthenticated browser visits to /mcp return a clear JSON error instead of internal details.

Tools

• search_swiftui_component
• generate_component_patch
• validate_dependency_policy
• export_component_receipt

Useful Links

• Product page: https://shipswiftcomponents.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605r26_224703
• Pricing: https://shipswiftcomponents.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605r26_224703#pricing
• Server card: https://shipswiftcomponents.clauxel.com/server-card.json
• MCP endpoint: https://shipswiftcomponents.clauxel.com/mcp

Status

This repository is a public documentation and directory-submission reference for the hosted service. It does not contain the private production source code.

Quick Start

1. Open the website and choose a plan.
2. Create or request an API token.
3. Add the endpoint to an MCP client that supports Streamable HTTP remote servers.
4. Send JSON-RPC requests with the bearer token.