TypeMCP technical documentation

Build a typed Petstore workflow, one boundary at a time.

Published · 0.2.2

Start with a small application-owned workspace. Learn the declaration, compiler, and runtime seams before you compose a real MCP server.

A canonical, source-owned curriculum

Petstore workflow

Start with an explicit resolver and runtime boundary; the reader retains application lifecycle ownership while making each runtime choice explicitly.

Your learning path

Petstore workflow
6 focused stepsStep 1 of 6Ready to start

Step 1 of 3Start the Petstore workspace

Create the strict TypeScript workspace and application-owned client seam.

Begin Build →Step 2 of 3Petstore TypeMCP foundation

Declare, inspect, compile, and run a TypeMCP server over local stdio.

Step 3 of 3Petstore walkthrough

Build one catalog tool and select a published TypeMCP runtime boundary.

First package contact

Get started

Getting startedInstall TypeMCP and inspect a declaration with the published package.

Vocabulary and compatibility

Learn

Core conceptsLearn declarations, immutable definitions, compiler boundaries, and application-owned responsibilities.Configuration and compatibilityConfigure standard decorators, Node, and module loading.

Choose a runtime boundary

Integrate

HTTP framework integrationPublished Streamable HTTP and Next.js integration shape.LangChain and LangGraphPublished tools-only LangChain adapter and consumer-owned LangGraph ToolNode composition.Choose a runtime boundaryChoose the published root, stdio, HTTP, or tools-only LangChain surface.

Exact contracts and compatibility

Reference

Decorator API contractPublished decorator declarations, runtime compilation, and transport boundaries.Architecture overviewPublished metadata, compiler, resolver, and transport architecture.

Documentation source pinned to 9124c25519f3 (opens in a new tab)