MCP Creator

Build the smallest MCP surface that serves the active workflow. Preserve existing supported operations and deployment constraints when reviewing or extending a server.

Establish the project's installed SDK, target host, transport, and supported revisions first. For new servers, consider MCP 2026-07-28; verify compatibility against the official specification and the selected SDK release. Do not migrate a working server merely to repair its launch configuration. Load protocol-v2.md before changing wire behavior or making an MCP conformance claim. Distinguish:

• MCP Core 2026-07-28 — normative core protocol requirement;
• Official MCP Extension — optional, negotiated, disabled by default;
• Custom Application Pattern — architecture built with ordinary tools, resources, and explicit handles;
• Deprecated / Legacy — retained only in an isolated compatibility path;
• Experimental / Incubating — only when an official MCP source assigns that status.

Never present a custom pattern as an MCP primitive, or an official extension as core behavior.

Workflow