1,040 pages for comm.

Quickstart: Publish an MCP Server to the MCP Registry Model Context Protocol · in the page registry/quickstart …packages). In particular, you will probably need to run the following commands: ```bash theme={null} # If necessary, authenticate to npm npm adduser # Publish the package npm publish --access public… MCP Registry Aggregators Model Context Protocol · in the page registry/registry-aggregators …ld which may be updated to, e.g., `"deprecated"` or `"deleted"`. We recommend that aggregators keep their copy of each server's `status` up to date. The `"deleted"` status typically indicates that a… Official MCP Registry Terms of Service Model Context Protocol · in the page registry/terms-of-service …s intended to be a centralized repository of MCP servers developed by community members to facilitate easy access by AI applications. These terms are governed by the laws of the State of California.… Versioning Published MCP Servers Model Context Protocol · in the page registry/versioning …r metadata) cannot be changed. ## Version Format The MCP Registry recommends [semantic versioning](https://semver.org/), but supports any version string format. When a server is published, the MCP R… SEP-1024: MCP Client Security Requirements for Local Server Installation Model Context Protocol · in the page seps/1024-mcp-client-security-requirements-for-local-server- …de installation flows, allowing malicious actors to execute arbitrary commands on user systems through crafted MCP server configurations distributed via links or social engineering. This proposal est… SEP-1034: Support default values for all primitive types in elicitation schemas Model Context Protocol · in the page seps/1034--support-default-values-for-all-primitive-types-in …tocol/modelcontextprotocol/pull/1034) | *** ## Abstract This SEP recommends adding support for default values to all primitive types in the MCP elicitation schema (StringSchema, NumberSchema, and E… SEP-1036: URL Mode Elicitation for secure out-of-band interactions Model Context Protocol · in the page seps/1036-url-mode-elicitation-for-secure-out-of-band-intera …ive information from users through structured, in-band requests (most commonly imagined as the MCP client rendering a form to collect data from the end-user). However, several critical use cases requi… SEP-1046: Support OAuth client credentials flow in authorization Model Context Protocol · in the page seps/1046-support-oauth-client-credentials-flow-in-authoriza …ontextprotocol/modelcontextprotocol/pull/1046) | *** ## Abstract Recommends adding the OAuth client credentials flow to the authorization spec to enable machine-to-machine scenarios. ### Motivatio… SEP-1302: Formalize Working Groups and Interest Groups in MCP Governance Model Context Protocol · in the page seps/1302-formalize-working-groups-and-interest-groups-in-mc …ion of “Working Groups” and “Interest Groups” that facilitate MCP sub-communities for discussion and collaboration. This SEP aims to formally define those two terms: what they are meant to achieve, ho… SEP-1319: Decouple Request Payload from RPC Methods Definition Model Context Protocol · in the page seps/1319-decouple-request-payload-from-rpc-methods-definiti …transports like **gRPC** (which is currently a [popular ask from the community](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/966)), a transport-agnostic definition of its reque… SEP-1330: Elicitation Enum Schema Improvements and Standards Compliance Model Context Protocol · in the page seps/1330-elicitation-enum-schema-improvements-and-standards …dopt `EnumSchema` in the future) to a single selection model. It is a common pattern to ask the user to select multiple entries. In the UI, this amounts to the difference between using checkboxes or r… SEP-1577: Sampling With Tools Model Context Protocol · in the page seps/1577--sampling-with-tools …* `toolChoice.mode` can be `“auto" | "required" | "none"` to allow common structured outputs use case (see below for possible follow up improvements) * Fenced by new capability (`sampling { tools… SEP-1613: Establish JSON Schema 2020-12 as Default Dialect for MCP Model Context Protocol · in the page seps/1613-establish-json-schema-2020-12-as-default-dialect-f …osystems * Developer uncertainty requiring arbitrary version choices Community discussion (GitHub Discussion #366, PR #655) revealed that implementations were split between draft-07 and 2020-12, with… SEP-1686: Tasks Model Context Protocol · in the page seps/1686-tasks …to support this pattern, splitting it into three separate tools to accommodate this: 1. `start_long_running_tool`: This would start the work represented by `long_running_tool` and return a tracking… SEP-1730: SDKs Tiering System Model Context Protocol · in the page seps/1730-sdks-tiering-system …SDKs to establish clear expectations for feature support, maintenance commitments, and quality standards. The system defines three tiers of SDK support with objective, measurable criteria for classifi… SEP-1850: PR-Based SEP Workflow Model Context Protocol · in the page seps/1850-pr-based-sep-workflow …b/main/MAINTAINERS.md) 4. **After the PR number is known**, amend the commit to rename the file to `{PR-number}-{slug}.md` and update the header (`SEP-{PR-number}` and `PR: #{PR-number}`) 5. **Wait fo… SEP-1865: MCP Apps - Interactive User Interfaces for MCP Model Context Protocol · in the page seps/1865-mcp-apps-interactive-user-interfaces-for-mcp …ing them with tools through metadata, and facilitating bi-directional communication between the UI and the host using MCP's JSON-RPC base protocol. This extension addresses the growing community need… SEP-2085: Governance Succession and Amendment Procedures Model Context Protocol · in the page seps/2085-governance-succession-and-amendment …ority. 2. **Governance Evolution**: As the MCP project grows and the community evolves, the governance structure may need to adapt. Currently, there is no defined process for how the governance docum… SEP-2106: Tools `inputSchema` & `outputSchema` Conform to JSON Schema 2020-12 Model Context Protocol · in the page seps/2106-json-schema-2020-12 …wn }` (an object with string keys), which prevents returning arrays—a common API response pattern. ### Real-World Impact Consider a weather API tool that returns hourly forecasts: ```json theme={nu… SEP-2127: MCP Server Cards - HTTP Server Discovery Model Context Protocol · in the page seps/2127-mcp-server-cards …erved URI, with `<streamable-http-url>/server-card` reserved as the recommended location. These documents provide static server information without requiring connection establishment. ### Enabled Use… SEP-2133: Extensions Model Context Protocol · in the page seps/2133-extensions …across all implementations, providing clear extension points for the community to propose, review, and adopt enhanced functionality. This SEP defines both official extensions (maintained by MCP main… SEP-2148: MCP Contributor Ladder Model Context Protocol · in the page seps/2148-contributor-ladder …through Core Maintainer. The ladder provides transparent pathways for community members to understand how they can grow their involvement and influence within the project. This SEP is a companion to… SEP-2149: MCP Group Governance and Charter Template Model Context Protocol · in the page seps/2149-working-group-charter-template …specific mission, scope, leadership, and work. Together they address community feedback about unclear authority delegation and inconsistent processes across groups. This SEP is a companion to [SEP-2… SEP-2164: Standardize Resource Not Found Error Code Model Context Protocol · in the page seps/2164-resource-not-found-error …ocol/pull/2164) | *** ## Abstract The current MCP specification [recommends `-32002`](https://modelcontextprotocol.io/specification/draft/server/resources#error-handling) as the error code for reso… SEP-2243: HTTP Header Standardization for Streamable HTTP Transport Model Context Protocol · in the page seps/2243-http-standardization …cker.ietf.org/doc/html/rfc9110)) does not specify header size limits. Common HTTP infrastructure imposes its own limits — ranging from 4–8 KB on some servers (e.g., Apache at \~8190 bytes) to 128 KB o… SEP-2260: Require Server requests to be associated with a Client request. Model Context Protocol · in the page seps/2260-Require-Server-requests-to-be-associated-with-Client-requests …on from Server to Client; they only need request-scoped bidirectional communication 2. **Clarifies user experience** - Users understand that sampling/elicitation happens *because* they initiated an ac… SEP-2322: Multi Round-Trip Requests Model Context Protocol · in the page seps/2322-MRTR …ignificantly reduce the cost of operating MCP servers at scale in the common case. It also reduces the HTTP transport's dependence on SSE streams, which cause problems in a lot of environments that ca… SEP-2484: Require Conformance Tests for Standards Track SEPs to Reach Final Status Model Context Protocol · in the page seps/2484-conformance-tests-required-for-final-seps …following are **exempt**: * **Process SEPs** (governance, workflow, community structure) * **Informational SEPs** (guidelines, best practices without normative force) * **Standards Track SEPs with n… SEP-2567: Sessionless MCP via Explicit State Handles Model Context Protocol · in the page seps/2567-sessionless-mcp …tor tool calls generating fresh MCP session each invocation"](https://community.openai.com/t/connector-tool-calls-generating-fresh-mcp-session-each-invocation/1364975), OpenAI Developer Community, Nov… SEP-2575: Make MCP Stateless Model Context Protocol · in the page seps/2575-stateless-mcp …d eventually garbage-collect per-client session state. This is a common source of bugs and memory leaks. * **Client-side:** Developers must write complex code to manage a persistent… SEP-2596: Specification Feature Lifecycle and Deprecation Policy Model Context Protocol · in the page seps/2596-spec-feature-lifecycle-and-deprecation …mean different things, or how long either state lasts before removal. Community questions such as [discussion #2177][disc-2177] (asking when the SSE transport will actually be removed) have no policy… SEP-2640: Skills Extension Model Context Protocol · in the page seps/2640-skills-extension …"description": "Follow this team's Git conventions for branching and commits" }, "resources": [ { "uri": "skill://git-workflow/SKILL.md", "digest": "… SEP-2663: Tasks Extension Model Context Protocol · in the page seps/2663-tasks-extension …uest types in the future; implementations **SHOULD** be designed to accommodate additional request types in future revisions of this specification. ### Polymorphic Results A request that is eligible… SEP-3392: Extension Lifecycle Model Context Protocol · in the page seps/3392-extension-lifecycle …llowing its [decision-making process](https://modelcontextprotocol.io/community/working-interest-groups.md#making-decisions). The Core Maintainers keep the authority SEP-2133 gives them over every ex… SEP-3398: Release Cycle Updates Model Context Protocol · in the page seps/3398-release-cycle-updates …leased. The current [SEP guidelines](https://modelcontextprotocol.io/community/sep-guidelines.md) define sponsorship, review, acceptance, and finalization, but do not connect those stages to a recurr… SEP-932: Model Context Protocol Governance Model Context Protocol · in the page seps/932-model-context-protocol-governance …current informal decision-making process lacks: 1. **Transparency**: Community members have no clear visibility into how decisions are made 2. **Participation Pathways**: Contributors lack defined wa… SEP-973: Expose additional metadata for Implementations, Resources, Tools and Prompts Model Context Protocol · in the page seps/973-expose-additional-metadata-for-implementations-res …ervers/clients are providing an implementation e.g. a tool in a slash command interface:  * **Visual Affordan… SEP-985: Align OAuth 2.0 Protected Resource Metadata with RFC 9728 Model Context Protocol · in the page seps/985-align-oauth-20-protected-resource-metadata-with-rf …sier MCP adoption. Requiring only the header would impose significant communication overhead between components, especially when hundreds or thousands of MCP instances are created and destroyed dynami… SEP-986: Specify Format for Tool Names Model Context Protocol · in the page seps/986-specify-format-for-tool-names …ity, clarity, and interoperability across MCP implementations while accommodating a wide range of naming conventions. ## Motivation Without a prescribed format for tool names, MCP implementations ha… SEP-991: Enable URL-based Client Registration using OAuth Client ID Metadata Documents Model Context Protocol · in the page seps/991-enable-url-based-client-registration-using-oauth-c …document containing client metadata. This specifically addresses the common MCP scenario where servers and clients have no pre-existing relationship, enabling servers to trust clients without pre-coo… Specification Enhancement Proposals (SEPs) Model Context Protocol · in the page seps/index …s/1850.md)). > [card] [Submit a SEP](https://modelcontextprotocol.io/community/sep-guidelines.md) > > Learn how to submit your own Specification Enhancement Proposal ## Summary * **Accepted**: 1 *… Lifecycle Model Context Protocol · in the page specification/2024-11-05/basic/lifecycle …tion and protocol version agreement 2. **Operation**: Normal protocol communication 3. **Shutdown**: Graceful termination of the connection ```mermaid theme={null} sequenceDiagram participant Cli… Transports Model Context Protocol · in the page specification/2024-11-05/basic/transports …currently defines two standard transport mechanisms for client-server communication: 1. [stdio](#stdio), communication over standard in and standard out 2. [HTTP with Server-Sent Events](#http-with-s… Cancellation Model Context Protocol · in the page specification/2024-11-05/basic/utilities/cancellation …e of notifications while allowing for race conditions in asynchronous communication. Roots Model Context Protocol · in the page specification/2024-11-05/client/roots …rror Handling Clients **SHOULD** return standard JSON-RPC errors for common failure cases: * Client does not support roots: `-32601` (Method not found) * Internal errors: `-32603` Example error: `… Sampling Model Context Protocol · in the page specification/2024-11-05/client/sampling …apabilities. ## Error Handling Clients **SHOULD** return errors for common failure cases: Example error: ```json theme={null} { "jsonrpc": "2.0", "id": 1, "error": { "code": -1, "mes… Specification Model Context Protocol · in the page specification/2024-11-05/index …ST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [BCP 14](https://datat… Overview Model Context Protocol · in the page specification/2024-11-05/server/index …ser-controlled | Interactive templates invoked by user choice | Slash commands, menu options | | Resources | Application-controlled | Contextual data attached and managed by the client | File contents… Prompts Model Context Protocol · in the page specification/2024-11-05/server/prompts …or use. Typically, prompts would be triggered through user-initiated commands in the user interface, which allows users to naturally discover and invoke available prompts. For example, as slash comm… Resources Model Context Protocol · in the page specification/2024-11-05/server/resources …"mimeType": "image/png", "blob": "base64-encoded-data" } ``` ## Common URI Schemes The protocol defines several standard URI schemes. This list not exhaustive—implementations are always free to…