MCP Turns One: 17 SEPs Rewiring AI Agents
MCP 1-year: 17 SEPs tighten security, decentralize governance & let AI agents run long tasks serverless.
“Top Python Libraries” Publication 400 Subscriptions 20% Discount Offer Link.
SEP (Specification Enhancement Proposal) is a design documentation mechanism in the MCP community used to propose, discuss, and document suggestions for significant new features or changes to the MCP protocol or its processes.
Governance Level
Over the past year, MCP’s development has been primarily driven by core maintainers (mainly Anthropic). While this centralized model was highly efficient in the early stages, bottlenecks emerged as the ecosystem exploded. This update first addresses the issue of decentralizing the governance structure.
Decentralization of Governance Structure (SEP-1302 and SEP-1630)
Through SEP-1302, MCP established mechanisms for working groups and interest groups. This is not merely a change in management form, but signifies that the production of technical specifications has shifted from official releases to community-driven collective wisdom. For example, the tool naming convention (SEP-986) mentioned later was a consensus reached after intense community discussion. This mechanism has absorbed wisdom from security researchers and open-source experts across various fields, ensuring that the protocol is no longer one company’s private garden.
Combined with SEP-1630’s SDK tiering system, community developers now have clearer guidance, with explicit standards for both choosing technology stacks and contributing code.