Concepts
- What an MCP server is, and what yours has to doLearn what an MCP server exposes, how assistants call its tools, and the responsibilities that turn an API integration into a reliable service.
- Tool design: reads, writes and guarded actionsThe three kinds of tool every integration needs, the rules each one follows, and the four-tool interface that all the example servers implement identically.
Build
- The Sample Shop API every example wrapsExplore the Sample Shop API used by our MCP examples: product search, order lookup, an idempotent cart update, and a guarded checkout action.
- Build an MCP server in TypeScriptBuild a TypeScript MCP server for the Sample Shop API with typed tools, annotations, error handling, and a Streamable HTTP endpoint using Express.
- Build an MCP server in PythonBuild a Python MCP server for the Sample Shop API with typed tools, input descriptions, actionable errors, and a Streamable HTTP endpoint.
- Build an MCP server in C# (.NET)Build a C# MCP server for the Sample Shop API with annotated tools, parameter descriptions, error handling, and an ASP.NET Core HTTP endpoint.
- Build an MCP server in PHPBuild a PHP MCP server for the Sample Shop API with attribute-based tools, input schemas, actionable errors, and a PSR-7 HTTP entry point.
- Conformance testing: one scenario, four serversTest four MCP servers with one shared scenario. Check tool schemas, annotations, errors, and behaviour across TypeScript, Python, C#, and PHP.
Connect
- Connect your MCP server to ClaudeConnect a remote MCP server to Claude on the web, desktop, or Claude Code. Test with the MCP Inspector and check the workflow before launch.
- Connect your MCP server to ChatGPTPrepare your remote MCP server for ChatGPT. Review HTTPS access, authorization, connection setup, and the tool behaviours to test before launch.
Generators
Production
REA
- How REA worksA plain explanation of REA, the open-source reverse engineering MCP server: the investigation loop, what your assistant receives, and how evidence stays honest.
- REA's major componentsThe parts of REA: the CLI, the stdio MCP server, the analysis providers it wraps, agent setup and skill, readiness checks, and the evidence it keeps.
- Requirements to run REA locally and in the cloudWhat REA needs on a laptop: Node.js, engines per target, memory and OS notes. And what changes when you host it: transport, isolation, licences and sizing.
- What REA can and cannot doRealistic expectations for REA: the questions it answers well per target, what it will not do, and the limits set by engines, formats and the law.
Website builder
- Website builder overviewWhat the website builder is, what a conversation with ChatGPT or Claude produces, who owns the result, and what is in the coming-soon release.
- Connect from ChatGPT or ClaudeHow the website builder appears in ChatGPT and Claude as a remote MCP connector, the tools it exposes, and what a first conversation looks like.
- Your code and repositoryWhat is inside a generated website repository, how the builder and your developers work in it at the same time, and the rules that keep its history clean.
- Transfer and maintainHow to move a generated website to your own infrastructure, and how to keep maintaining it from your chat afterwards or without the builder at all.