Typeship

dev.typeshipPublished by typeship.devOfficial publisherv0.23.0Updated Oct 24, 2026

Generate a typed SDK, CLI, and MCP server from any OpenAPI or GraphQL spec, and keep them current.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Typeship's MCP server lets an assistant search its docs, read API operations, and execute them to resolve OpenAPI or GraphQL specs and keep generated SDK, CLI,

What you can do
Search and read Typeship documentation and API operations, including arguments, examples and safety classification before running anything. Execute Typeship API operations, with input schemas derived from the OpenAPI spec and arguments validated before reaching the API. Resolve an OpenAPI or GraphQL spec, diagnose it, and keep selected CLI, MCP and SDK targets current. Trim results to chosen keys with a fields parameter and receive stable error codes with next steps. Limit the exposed surface with a read-only mode, a tool subset, or a result size cap.
When to use it
Useful when you want an assistant to work with Typeship from inside a coding client: inspecting and running Typeship API operations, or maintaining generated SDKs, CLIs and MCP servers from an OpenAPI or GraphQL spec. Choose the read-only variant when the assistant should only inspect and never write.
Requirements
Either the hosted endpoint at typeship.dev over streamable HTTP, or the local npm package run with npx, which needs Node.js 20 or later. Authentication is required: an OAuth login or a TYPESHIP_TOKEN API key supplied through the client's environment or secret settings. Network access to Typeship.
Before you install
The token is a credential: keep it out of URLs and command arguments and use the client's secret storage. The default server can write, so prefer the read-only mode or a restricted tool subset when changes are not wanted. Executing operations may change Typeship projects, specs and generated targets, and data is sent to the Typeship service.

Installation

In SourceWeft

  1. Open Typeship 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/dev.typeship%2Ftypeship/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": {
    "typeship": {
      "type": "http",
      "url": "https://typeship.dev/mcp"
    }
  }
}

README

@typeship-ax/mcp

MCP server for the Typeship API. API reference

Resolve an OpenAPI or GraphQL Spec, diagnose it, and keep every selected CLI, MCP, and SDK Target current.

Installation

MCP clients start the server with npx, so it needs no separate installation (see Connect an MCP client). To install the typeship-mcp command globally instead:

sh
npm install --global @typeship-ax/[email protected]

Requires Node.js 20+.

Connect an MCP client

Provide TYPESHIP_TOKEN through the MCP client's environment or secret settings. Keep credential values out of URLs and command arguments.

Local

  • Claude Code: claude mcp add typeship -- npx -y --package @typeship-ax/mcp typeship-mcp
  • Codex: codex mcp add typeship -- npx -y --package @typeship-ax/mcp typeship-mcp
  • Install in VS Code

Local · read-only

  • Claude Code: claude mcp add typeship-readonly -- npx -y --package @typeship-ax/mcp typeship-mcp --read-only
  • Codex: codex mcp add typeship-readonly -- npx -y --package @typeship-ax/mcp typeship-mcp --read-only
  • Install in VS Code

Hosted

  • Claude Code: claude mcp add --transport http typeship https://typeship.dev/mcp
  • Codex: codex mcp add typeship --url https://typeship.dev/mcp
  • Install in VS Code

Hosted · read-only

  • Claude Code: claude mcp add --transport http typeship-readonly https://typeship.dev/mcp/readonly
  • Codex: codex mcp add typeship-readonly --url https://typeship.dev/mcp/readonly
  • Install in VS Code

Other clients

Add a server entry to your client's MCP configuration. For Cursor, merge it into mcpServers in .cursor/mcp.json, then enable the server in Cursor's MCP settings:

json
{  "mcpServers": {    "typeship": {      "command": "npx",      "args": [        "-y",        "--package",        "@typeship-ax/mcp",        "typeship-mcp"      ],      "env": {        "TYPESHIP_TOKEN": "replace-with-your-credential"      }    }  }}

Replace the credential placeholder using the MCP client's secret storage when it has one. The server reads TYPESHIP_TOKEN from its environment; credentials never belong in command arguments.

The server supports MCP 2025-11-25 and 2026-07-28 and picks the version automatically, so clients need no protocol settings. After registering it with Claude Code, claude mcp list shows the connection.

Tools

The server runs over stdio with no runtime dependencies and exposes a compact discovery surface: search_docs, read_docs, and execute. Read an operation before executing it to get its arguments, an example, and its safety classification.

Tool input schemas come from the OpenAPI spec, so agents see real parameter types and required fields. Arguments are checked before anything reaches the API (unknown or mistyped ones come back as one isError result, nothing is dropped), every tool takes fields to keep only the result keys it needs, and errors carry a stable code and next_steps.

Add --read-only to args (or set TYPESHIP_MCP_READ_ONLY=1) for a server that cannot write, --tools projects,specs (or TYPESHIP_MCP_TOOLS) to expose a subset, and TYPESHIP_MCP_MAX_RESULT_CHARS to change the result size cap (64,000).

Generated from the OpenAPI spec by Typeship.

Source: README.md at commit 3224d49

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

4
  1. v0.23.0LatestSep 30, 2026
  2. v0.22.0Sep 29, 2026
  3. v0.21.0Sep 26, 2026
  4. v0.10.0Sep 16, 2026

Score

85% 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

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts