TypeChain technical documentation

Continue the typed Petstore workflow at the composition boundary.

Published · 0.1.1

Continue the workspace with typed tools, policy intent, and a composition boundary your application controls.

Continue the canonical workspace

Petstore workflow

Continue the TypeMCP workspace with typed tools and explicit composition choices. TypeChain does not provide models, credentials, policy enforcement, or transport.

Your learning path

Petstore workflow
6 focused stepsStep 4 of 6Ready to continue
Step 4 of 6Continue the Petstore workspace

Petstore TypeChain foundation: Define and inspect a typed Petstore tool in the workspace created by the TypeMCP path.

Continue Build →Step 5 of 6Petstore policy and composition

Record policy intent and choose one application-owned composition boundary.

Step 6 of 6Petstore walkthrough

Build one typed catalog tool, then choose a LangChain, agent, or in-process TypeMCP boundary.

First package contact

Get started

Getting startedInstall TypeChain, configure Stage 3 decorators, and declare a first tool.

Typed-tool vocabulary

Learn

Core conceptsUnderstand tool metadata, immutable definitions, policy intent, and explicit integration boundaries.Tools and definitionsThe @Tool() contract, immutable definitions, and inheritance.

Choose an application boundary

Integrate

LangChain integrationAdapt decorated methods into standard LangChain tools.Agent builderBuild LangChain agents while retaining application control.TypeMCP bridgeCompose a TypeMCP server into LangChain tools in process.

Exact contracts and composition choices

Reference

Choose a composition boundaryChoose metadata, LangChain, agent, or in-process TypeMCP composition.Decorator API contractPublished exports and integration boundaries.

Documentation source pinned to 90152f97834d (opens in a new tab)