Read-only catalog of the @blueprint-modular/core design system (104 components) exposed over MCP. Four tools: list_components (browse the catalog by category), search_components (find a component by need or function in free text), get_component (full contract — props, types, usage example, related components, semantic role), and suggest_composition (propose a set of components for a described need). Use it to discover and correctly assemble Blueprint Modular components when generating React or Python UIs. Public, no auth, Streamable HTTP. Apache-2.0.
How do I install blueprint-modular in Claude Code?
Run: claude mcp add --transport http blueprint-modular https://blueprint-modular--remicabrit.run.tools
Can I add blueprint-modular as a connector in ChatGPT or Claude.ai?
Yes — it’s a remote MCP server, so no local install is needed. ChatGPT: Settings → Connectors → Advanced → Developer mode → Add connector, then paste https://blueprint-modular--remicabrit.run.tools. Claude.ai: Settings → Connectors → Add custom connector, then paste the same URL.
Secureship MCP gives AI assistants access to a multi-carrier shipping API covering rate comparison, label generation, package tracking, pickup scheduling, address book management, shipment history, customs documents, and more — across carriers like UPS, FedEx, Purolator, Canpar, and others. Browse 150+ live endpoint schemas, parameters, and auth details — always current, never stale.
Secureship isn't just for shipping with one carrier — it's a multi-carrier shipping platform, and this MCP server gives AI assistants full access to the API documentation for every supported action: compare rates across carriers, generate shipping labels, track packages, schedule pickups, manage address books, review shipment history, produce customs documents, handle invoices, and even perform actions available on the Secureship web dashboard — all through a single API.
The MCP documentation server exposes live endpoint metadata pulled directly from the running application — not static docs that go stale. That means AI assistants always get the correct paths, parameters, request bodies, response schemas, and authentication requirements for 150+ endpoints.
Read-only, public, no API key needed to browse. Authentication for the actual shipping API uses a simple X-API-KEY header.
**Tools exposed:**
- SearchDocs — keyword search across all API endpoints
- GetEndpointDetail — full schema for a specific endpoint (params, request body, responses, auth)
- ListEndpoints — list all endpoints, optionally filtered by category
- GetAuthInfo — authentication instructions (X-API-KEY header)
**Categories:** Shipping, logistics, e-commerce, carriers, rates, labels, tracking, address book, customs documents, shipment history
