Documentation
mcpose sits between any LLM client and any MCP server, routing every tool call through composable onion middleware and recording it in a tamper-evident, compliance-grade audit trail — nothing upstream changes. These docs cover the core workflow, the concepts behind the proxy, and the reference for every published package.
Start here
Quick Start →
Wrap an upstream MCP server with a logging middleware and serve it over stdio — ten lines of glue.
Introduction →
What mcpose is and why it exists.
Explore the docs
Concepts →
The proxy model, the middleware onion, identity and sessions, and rejection reasons.
Packages →
Reference for mcpose, @mcpose/audit, and @mcpose/testing.
Recipes →
PII redaction with audit, list-tools rewriting, and OAuth against an upstream server.
Project →
Roadmap, ADRs, contributing, and the security policy.