Communication changedcommunity/communication
Nearest release: v2.1.321, published 5 hours after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 9 Nov 2026 13:29 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 9 Nov 2026 13:37 UTC.
Upstream edited
Recorded here
Lines+18added
Lines−96removed
From line
1
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits5to this page, all time
# Communication ## Channels ## Decision records # Contributor Communication ## Communication Channels ### Public Channels (Default) ### Private Channels (Exceptions) ## GitHub Discussions ## GitHub Issues ## Security Issues ## Decision Records
The whole hunk
from line 1, old and new numbered
/
from line 1
1# Contributor Communication
1# Communication
22
3> Communication strategy and framework for the Model Context Protocol community
3> The MCP project's communication channels, when a channel may be private, and where decisions are recorded.
44
5This document explains how to communicate and collaborate within the Model Context Protocol (MCP) project.
5This 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](https://modelcontextprotocol.io/seps/994.md), a Specification Enhancement Proposal (SEP), and is changed by a Process SEP. The [Code of Conduct](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/CODE_OF_CONDUCT.md) governs every channel. If you are new to the project, start at [Contributing](https://modelcontextprotocol.io/community/contributing.md).
66
7## Communication Channels
7## Channels
88
9| Channel | Purpose | When to Use |
10| - | - | - |
11| [Discord](https://discord.gg/6CSzBmMkjX) | Real-time discussion | Quick questions, coordination, WG/IG discussions |
12| [Live calls](https://meet.modelcontextprotocol.io/) | Sync up | WG/IG presentations, progress reports |
13| [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions) | Structured discussion | Proposals, roadmap planning, longer-form debate |
14| [GitHub Issues](https://github.com/modelcontextprotocol/modelcontextprotocol/issues) | Actionable tasks | Bug reports, documentation fixes |
15| [Vulnerability reports](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/SECURITY.md) | Security issues | Vulnerabilities - **never post publicly** |
9| Channel | Use it for |
10| - | - |
11| [Discord](https://discord.gg/6CSzBmMkjX) | Real-time coordination among contributors, including working group, interest group and SDK discussion |
12| [Meeting calendar](https://meet.modelcontextprotocol.io/) | Open group and maintainer meetings. For how meetings run, see [Meetings and channels](https://modelcontextprotocol.io/community/working-interest-groups.md#meetings-and-channels) |
13| [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions) | Ideas, feature requests with rationale, questions, roadmap discussion, announcements and releases, and meeting agendas and notes (Meeting Notes category) |
14| [GitHub Issues](https://github.com/modelcontextprotocol/modelcontextprotocol/issues) | Reproducible bugs, scoped documentation tasks, and CI and release tasks, filed through the issue forms. [SEPs](https://modelcontextprotocol.io/community/sep-guidelines.md) are pull requests to `seps/`, not issues |
15| [Security advisories](https://modelcontextprotocol.io/community/policies.md#reporting-a-vulnerability) | Vulnerabilities. Never post one in a public channel |
1616
17All communication is governed by our [Code of Conduct](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/CODE_OF_CONDUCT.md). We expect respectful, professional, and inclusive interactions across all channels.
17Each 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](https://modelcontextprotocol.io/community/policies.md#reporting-a-vulnerability).
1818
1919## Discord
2020
21The [MCP Contributor Discord](https://discord.gg/6CSzBmMkjX) is for real-time contributor discussion and collaboration. The server is designed for **MCP contributors** and is not intended for general MCP support.
21The [MCP Contributor Discord](https://discord.gg/6CSzBmMkjX) 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.
2222
23### Public Channels (Default)
23Channels 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.
2424
25**Purpose:** Open community engagement, collaborative development, and transparent project coordination.
25Channels 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.
2626
27**Primary use cases:**
27## Decision records
2828
29* SDK and tooling development (e.g., `#typescript-sdk-dev`, `#inspector-dev`)
30* [Working Group and Interest Group](https://modelcontextprotocol.io/community/working-interest-groups.md) discussions (e.g., `#auth-wg`, `#security-ig`)
31* Community onboarding and contribution guidance
32* Community feedback and collaborative brainstorming
33* Public office hours and maintainer availability
29Discord 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](https://modelcontextprotocol.io/specification/draft/changelog.md), and process changes in these community pages.
3430
35**Avoid:**
36
37* MCP user support - Read official documentation and use GitHub Discussions for questions
38* Service or product marketing - Keep discussions vendor-neutral; mentions of brands are discouraged except as examples relevant to the specification
39
40### Private Channels (Exceptions)
41
42**Purpose:** Confidential coordination and sensitive matters. Access is restricted to designated maintainers.
43
44**Criteria for private use:**
45
46* Security incidents (CVEs, protocol vulnerabilities)
47* People matters (maintainer discussions, code of conduct issues)
48* Coordination requiring immediate or focused response with a limited audience
49* Some channels are read-only for maintainer decision-making
50
51**Transparency requirements:**
52
53* All technical and governance decisions affecting the community must be documented in GitHub Discussions and/or Issues, labeled with `notes`
54* Private channels are temporary "incident rooms," not for routine development
55* Some matters related to individual contributors may remain private when appropriate
56
57Any significant discussion on Discord that leads to a potential decision or proposal must be moved to GitHub Discussion or Issue for a persistent, searchable record.
58
59## GitHub Discussions
60
61Use for structured, long-form discussion and debate on project direction.
62
63**When to use:**
64
65* Project roadmap planning and milestone discussions
66* Announcements and release communications
67* Community polls and consensus-building
68* Feature requests with context and rationale
69* If a repository doesn't have Discussions enabled, use GitHub Issues instead
70
71## GitHub Issues
72
73Use for bug reports and actionable development tasks. Feature requests should go to [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions).
74
75**When to use:**
76
77* Bug reports with reproducible steps
78* Documentation improvements with specific scope
79* CI/CD problems and infrastructure issues
80* Release tasks and milestone tracking
81
82**Note:** SEP proposals are submitted as pull requests to the [`seps/` directory](https://github.com/modelcontextprotocol/modelcontextprotocol/tree/main/seps), not as GitHub Issues. See the [SEP Guidelines](https://modelcontextprotocol.io/community/sep-guidelines.md).
83
84## Security Issues
85
86**Do not post security issues publicly.**
87
881. Use the private security reporting process in [SECURITY.md](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/SECURITY.md)
892. Contact Lead or [Core Maintainers](https://modelcontextprotocol.io/community/governance.md#current-core-maintainers) directly
903. Follow responsible disclosure guidelines
91
92## Decision Records
93
94All MCP decisions are documented in public channels:
95
96| Type | Location |
97| - | - |
98| Technical decisions | [GitHub Issues](https://github.com/modelcontextprotocol/modelcontextprotocol/issues) and SEPs |
99| Specification changes | [Changelog](https://modelcontextprotocol.io/specification/draft/changelog.md) |
100| Process changes | [Community documentation](https://modelcontextprotocol.io/community/governance.md) |
101| Governance decisions | [GitHub Issues](https://github.com/modelcontextprotocol/modelcontextprotocol/issues) and SEPs |
102
103When documenting decisions, we retain as much context as possible:
104
105* Decision makers
106* Background context and motivation
107* Options considered
108* Rationale for chosen approach
109* Implementation steps
31A record names who decided, the context, the options considered, the rationale, and the next steps. For meeting agendas and notes, see [Meetings and channels](https://modelcontextprotocol.io/community/working-interest-groups.md#meetings-and-channels).
11032
No line in this hunk matches that.