Overview
typeship turns your OpenAPI or GraphQL spec into the SDK, CLI, and MCP server your users install, and keeps them current with a pull request on every spec change.
typeship generates the client-side of your API and maintains it. Point a project at your spec, and typeship produces a typed SDK with zero runtime dependencies in TypeScript, Python, or Go, plus a CLI and an MCP server for the TypeScript package. When the spec changes, typeship regenerates everything and opens a pull request per language with the API changes written out.
Examples use the Acme API throughout, so you will see acme, AcmeClient, and ACME_TOKEN. Your names come from your spec.
Start here
Quickstart
Create a project, generate your first package, make a call. Ten minutes.
Concepts
Projects, platforms, languages, generations, and how they fit together.
Regeneration
How a spec change becomes a pull request, and what is in it.
typeship API
Drive typeship from a pipeline or an agent.
What you get
SDK
Typed results and errors, auto-pagination, retries, hooks, validation, webhooks, streaming. TypeScript, Python, Go.
CLI
Every operation as a command with typed flags and JSON output, plus login, config, docs, and completion.
MCP server
Every operation as a tool for coding agents, with docs tools and a hosted endpoint.
Drive typeship itself
typeship CLI
npm install -g typeship-ax. Every console action as a command, JSON out, built for agents and pipelines.
typeship SDKs
typeship-ax on npm, typeship on PyPI, github.com/typeship-ax/go. Generated from typeship's own spec.
typeship MCP server
Hosted at typeship.dev/mcp and in the MCP registry as dev.typeship/typeship; local over stdio from the npm package.
Try it without an account
The generator on the homepage runs on any spec without signing up, capped at one platform and the first 25 operations, and keeps nothing. It is the fastest way to see what your package will look like. Everything that keeps a package current happens in a project.