com.clauxel.shipswiftcomponents/shipswiftcomponents-mcp
A paid remote MCP for ShipSwift, built to return verdicts, receipts, usage logs, and audit-ready JSO
What can you do with com.clauxel.shipswiftcomponents/shipswiftcomponents-mcp?
search_swiftui_componentgenerate_component_patchvalidate_dependency_policyexport_component_receipt
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http shipswiftcomponents-mcp 'https://shipswiftcomponents.clauxel.com/mcp' --header 'Authorization: <Bearer token from the product website.>'
{
"mcpServers": {
"shipswiftcomponents-mcp": {
"type": "http",
"url": "https://shipswiftcomponents.clauxel.com/mcp",
"headers": {
"Authorization": "<Bearer token from the product website.>"
}
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
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_componentgenerate_component_patchvalidate_dependency_policyexport_component_receipt
Quick Start
- Open the website and choose a plan.
- Create or request an API token.
- Add the endpoint to an MCP client that supports Streamable HTTP remote servers.
- Send JSON-RPC requests with the bearer token.
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.
Frequently asked questions
What is com.clauxel.shipswiftcomponents/shipswiftcomponents-mcp?
A paid remote MCP for ShipSwift, built to return verdicts, receipts, usage logs, and audit-ready JSO
How do I install com.clauxel.shipswiftcomponents/shipswiftcomponents-mcp?
It runs as a remote server. In Claude Code: claude mcp add --transport http shipswiftcomponents-mcp 'https://shipswiftcomponents.clauxel.com/mcp' --header 'Authorization: <Bearer token from the product website.>'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does com.clauxel.shipswiftcomponents/shipswiftcomponents-mcp need an API key?
Yes. It expects Authorization, which you set in its configuration.
Is com.clauxel.shipswiftcomponents/shipswiftcomponents-mcp open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains com.clauxel.shipswiftcomponents/shipswiftcomponents-mcp?
It is published by clauxel. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.