Skip to main content
This page sets out the project’s communication channels, when a channel may be private, and where decisions are recorded. It was adopted by SEP-994, a Specification Enhancement Proposal (SEP), and is changed by a Process SEP. The Code of Conduct governs every channel. If you are new to the project, start at Contributing.

Channels

Each SDK and project repository has its own issue tracker and Discord channel. Most have Discussions turned off and use Issues instead; this repository and the registry are the main exceptions. Vulnerability reports follow the Security Policy.

Discord

The MCP Contributor Discord is for people working on the protocol and its projects, and is where discussion of the protocol and its design starts. It is not a support channel: report a reproducible bug as an issue on the repository it affects, and start from the documentation for questions about using MCP. Do not market products or services on the server, and mention vendors only as examples relevant to the specification. Channels are named #general for project-wide discussion, #<name>-wg and #<name>-ig for each working group and interest group, and #<lang>-sdk-dev for each SDK. Other projects have a channel such as #inspector-dev. Propose a new group in #wg-ig-group-creation. Responses are best-effort. Channels are public by default. Private channels are restricted to designated maintainers and Community Moderators and exist only for security incidents (CVEs and protocol vulnerabilities), people and Code of Conduct matters, and coordination that needs an immediate or focused response from a limited audience. Some maintainer decision channels are read-only. A private channel is a temporary incident room, not a place for routine development. Matters concerning an individual contributor may remain private.

Decision records

Discord is not the record. A Discord discussion heading toward a technical or governance decision must move to a GitHub Discussion. Every technical or governance decision, including a Core Maintainer outcome on a SEP, is written up in a Discussion with the notes label, or on the SEP’s pull request. Specification changes are also recorded in the changelog, and process changes in these community pages. A record names who decided, the context, the options considered, the rationale, and the next steps. For meeting agendas and notes, see Meetings and channels.