Shippp

ai.shipppPublished by shippp.aiOfficial publisherv0.4.0Updated Nov 8, 2026

A connected canvas for the builders of the next era.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Shippp's MCP server connects an assistant to a Shippp workspace canvas, available as a remote endpoint or a local npm package.

What you can do
  • The listing does not name any tools, so the exact actions are unclear.
  • It connects an assistant to Shippp, described as a connected canvas for builders.
  • It can run as a hosted remote endpoint or as a local stdio process via the npm package.
  • Access is tied to a Shippp workspace through an API key or OAuth.
When to use it
Worth considering if you already use Shippp and want an assistant to work with your workspace canvas from inside a chat client. Without a tool list, check the vendor documentation first to confirm what it can actually do.
Requirements
A Shippp account and workspace. Authentication is required: OAuth, or a Shippp API key supplied as SHIPPP_API_KEY. An optional SHIPPP_API_URL overrides the default production API base URL. The local option needs Node.js for the npm package; the remote option needs network access to the hosted endpoint.
Before you install
The API key is a workspace credential; keep it out of shared configuration and logs. The tool list is not published, so what the assistant can read or change in your workspace is unknown before connecting. Pointing SHIPPP_API_URL at a non-default host sends your key and requests to that host.

Installation

In SourceWeft

  1. Open Shippp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.shippp%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "shippp": {
      "type": "http",
      "url": "https://app.shippp.ai/api/mcp/mcp"
    }
  }
}

README

This repository has no README.

Tools

8

shippp_list_units

List a Shippp file's screens and master components (id + name). Call this FIRST to discover the ids for shippp_get_component.

ParametersfileIdrequired

shippp_get_component

Get ONE component's deterministic Chakra UI code + a reproducibility receipt. `unitType` is 'master' (a design-system component) or 'screen' (a depth-0 artboard). Get ids from shippp_list_units.

ParametersfileIdrequiredunitIdrequiredunitTyperequired

shippp_get_tokens

Get the design system's tokens as a Chakra theme (createSystem) + receipt.

ParametersfileIdrequired

shippp_get_design_system

Get the whole design system as a publishable package (tokens + theme + recipes + every component + stories + package.json).

ParametersfileIdrequired

shippp_get_project

Get the whole file as a runnable Next.js project (screens as pages + the design system).

ParametersfileIdrequired

shippp_diff

Diff your CURRENT code against a fresh deterministic generation of a unit — shows exactly what a designer changed. Pass the same unit params as the get tools, plus `baseline` (the files you currently have for that unit).

ParametersunitrequiredfileIdrequiredunitIdbaselinerequiredunitType

shippp_sync_plan

Preview the repository's Shippp sync as a deterministic plan — NO writes. The repo root comes from the developer's own configuration (SHIPPP_REPO_ROOT env, or the server's working directory), never from tool input. Requires a committed shippp.target.json binding (created via shippp_bind_repository on the remote MCP). Returns the create/update/delete entries, hand-modified-file conflicts and any pending compiler/IR/adapter delta that shippp_sync_apply would need explicit approval for.

Takes no parameters.

shippp_sync_apply

Run the full repository sync with the bundled deterministic runner: fetch the bound unit's artifact, plan against the real on-disk state, apply atomically with rollback, run the repo's checks (SHIPPP_SYNC_CHECKS env), and write the receipt ONLY on full success. Writes are confined to the generated root of the repo's own binding; hand-modified generated files are structured conflicts and are never overwritten. If the plan or a refusal reports a compilerDelta, present it to the user and re-call with approvedCompilerDelta set to EXACTLY those lines ONLY after their explicit approval. After an approved re-bind, pass acceptReboundBaseline to adopt the previous binding's receipt as baseline.

ParametersacceptReboundBaselineapprovedCompilerDelta

Version history

2
  1. v0.4.0LatestOct 26, 2026
  2. v0.1.1Sep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.