Typeship

What the typeship MCP server does

The typeship MCP server is part of a generation workflow built around OpenAPI and GraphQL specifications. Typeship resolves a specification, diagnoses it, and produces selected targets for MCP, a command-line interface, and a typed TypeScript SDK. The exact MCP operations depend on the source specification, so the repository excerpt does not define a fixed tool list.

Generated outputs are intended to stay aligned with the selected specification. This makes the typeship MCP server relevant when an API contract is the source of truth and an agent needs operations derived from that contract rather than a hand-written, unrelated tool layer.

The supplied package is the TypeScript SDK for the Typeship API. It exposes methods for working with Typeship resources, including an organization lookup and project listing in the examples. It is separate from the generated MCP target, so the SDK documentation should not be treated as a complete description of the generated agent tools.

How it works

Typeship takes an OpenAPI or GraphQL specification as its input, resolves and diagnoses that specification, and uses it to generate the selected SDK, CLI, and MCP targets. Keeping targets current means rerunning or updating the generation workflow when the specification changes; the excerpt does not document an automatic synchronization process or a specific watch mode.

The TypeScript SDK is an ESM package that uses HTTP requests to the Typeship API. It requires Node.js 20 or a modern browser or edge runtime with fetch, AbortController, and Web Streams. Requests use a bearer token through the Authorization header. The SDK supports configurable base URLs, request timeouts, retry limits, custom fetch implementations, request and response hooks, and optional runtime schema validation.

List methods can return a page or be consumed through lazy async iteration. HTTP failures, response parsing failures, validation failures, and transport failures use distinct typed error classes. Errors include status, code, request ID, response body, and a message; successful paginated responses expose response metadata.

Setup and configuration

Install the documented SDK package with npm install @typeship-ax/sdk@0.27.0, then construct TypeshipClient with a bearer token. The default API base URL is https://typeship.dev/api/v1, and the default timeout is 60 seconds. The SDK allows per-call overrides for timeout, retry count, headers, and abort signals.

Set TYPESHIP_TOKEN for the token used in the quickstart. The excerpt does not provide an MCP-specific installation command, transport configuration, launch command, or client setup instructions. It also does not state whether a generated MCP target requires the SDK package at runtime.

Tools and capabilities

The typeship MCP server can be used to generate MCP tools from an OpenAPI or GraphQL schema, but individual tool names and parameters are determined by that schema. Supported generation outputs also include a typed SDK and CLI. The Typeship SDK provides organization access and project pagination in the documented examples, plus configurable authentication, retries, validation, instrumentation hooks, and typed error handling.

Limitations and notes

The available material does not identify a fixed set of MCP tools, an MCP transport, supported MCP clients, or a standalone server package. It also does not provide a license declaration. Treat the source specification as the authority for generated operations and inspect the generated output before relying on particular names, parameters, or response shapes.