This repository is the official home of the Model Context Protocol (MCP), an open standard defining how AI assistants discover and invoke external tools, resources, and prompts over JSON-RPC. In production it operates as a specification and governance hub: versioned TypeScript protocol schemas (2024-11-05 through 2026-07-28 plus draft) are compiled into JSON Schema artifacts, human-readable specification docs are generated and published, and a SEP (Specification Enhancement Proposal) process is automated by a GitHub bot that detects proposals, enforces lifecycle transitions, pings authors, and sends Discord notifications. The architecture is not a monolithic service or microservices; it is a mixed content-plus-tooling repository. The primary code components are the TypeScript schema sources, the schema/doc generation scripts (scripts/generate-schemas.ts, scripts/render-seps.ts), and the sep-automation Node.js application (tools/sep-automation), which uses explicit interfaces for the GitHub client, hooks, and workflow rules. Core data flows are: TypeScript interfaces -> JSON Schema -> published schema files and examples; SEP markdown -> rendered MDX documentation; and GitHub issue/PR events -> SEP state machine -> comments and Discord webhooks. External dependencies include Octokit/GitHub App auth, Discord webhooks, TypeDoc/typescript-json-schema, Mintlify for docs, and Hugo for the blog. Although classified as an application repo because of its runnable tooling, CI/CD, and unit tests, the dominant character is an open-standards documentation and governance project. It is actively maintained, enforces a conformance-testing mandate for SDKs, and contains well-crafted modular code. The main risks are content-version overhead (six dated spec snapshots plus draft, duplicated docs, frozen historical SEPs) and process/doc drift, not software decay.