Skip to main content
This page lists the policies that apply to everyone who takes part in the MCP project: in meetings, on Discord, and in every repository under the modelcontextprotocol organization. Group Leads and Facilitators link it from meeting agendas.

​
Code of Conduct

The Code of Conduct governs every channel, repository and meeting. Send reports to mcp-coc@anthropic.com. The Community Moderators handle them under the Contributor Ladder and escalate to Core Maintainers when needed.

​
Antitrust

Participants often work for competing organizations. MCP is organized as Model Context Protocol a Series of LF Projects, LLC, so the LF Projects policies, including its antitrust policy, apply to all participants. The project’s own Antitrust Policy sets out how meetings and standard-setting discussions are conducted.

​
Licensing and intellectual property

Code and specification contributions are made under the Apache License 2.0 and other documentation under CC-BY-4.0, with no copyright assignment. The governing text is General Project Policies.

​
AI-assisted contributions

Any AI assistance used for a contribution must be disclosed in the pull request or issue, together with its extent. This includes AI-written review responses and comments; trivial spacing or typo fixes are the only exception. The full policy is AI_POLICY.md, which applies to every repository in the organization.

​
Reporting a vulnerability

Do not report security issues in public issues, discussions or pull requests.
Open a private advisory on the affected repository at github.com/modelcontextprotocol/<repo>/security/advisories/new. Private vulnerability reporting is enabled on the specification repository and on every official SDK and project repository. Before filing, read SECURITY.md: it says what to include, describes the trust model and the behaviors that are intentional rather than vulnerabilities (stdio command execution, denial of service by a stdio peer, server side effects, LLM-driven tool invocation), and lists what remains in scope. The maintainers who receive a report coordinate the fix and advisory across every affected SDK so that advisories are released together, and raise it with the specification maintainers when the root cause is in the specification (see SDK Vulnerability Disclosure). CVEs are assigned through GitHub’s CNA. Questions that are not themselves a report, including which repository to file against, go to the Security Interest Group in #security-ig.

​
Communication and records

Communication sets out which channel is for what, when a channel may be private, and where decisions are recorded.