Contributing to MCP changedcommunity/contributing
Nearest release: v2.1.280, published an hour 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 22 Sep 2026 14:26 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 22 Oct 2026 20:37 UTC.
Upstream edited
Recorded here
Lines+17added
Lines−17removed
From line
12
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits5to this page, all time
The whole hunk
from line 12, old and new numbered
/
from line 12
1212You don't need to have a change ready to get involved. Join the
1313[MCP Contributor Discord](https://discord.gg/6CSzBmMkjX) to connect with contributors and
1414maintainers, ask questions, and find out where help is needed. See the
15[Contributor Communication](/community/communication) guide for all channels - including
15[Contributor Communication](/community/communication.md) guide for all channels - including
1616[live calls](https://meet.modelcontextprotocol.io/) and GitHub Discussions - and when to use
1717each one, or jump to [Getting Help](#getting-help) below.
1818
from line 62
6262
6363Throughout this guide, **specification repository** refers to
6464`modelcontextprotocol/modelcontextprotocol`, which contains the protocol spec, this documentation
65site, and [Spec Enhancement Proposals (SEPs)](/community/sep-guidelines).
65site, and [Spec Enhancement Proposals (SEPs)](/community/sep-guidelines.md).
6666
6767### Project Roles
6868
69MCP follows a [governance model](/community/governance) with different levels of responsibility:
69MCP follows a [governance model](/community/governance.md) with different levels of responsibility:
7070
7171* **Contributors** - Anyone who files issues, submits PRs, or participates in discussions (that's
7272 you!)
7373* **Maintainers** - Steward specific areas like SDKs, documentation, or
74 [Working Groups](/community/working-interest-groups)
74 [Working Groups](/community/working-interest-groups.md)
7575* **Core Maintainers** - Guide overall project direction, review SEPs, and oversee the specification
7676
7777You can find the current list of maintainers in the
from line 222
222222> [!TIP]
223223>
224224> Not sure which category your change falls into? Ask in the [MCP Contributor
225> Discord](/community/communication#discord) before starting any significant
225> Discord](/community/communication.md#discord) before starting any significant
226226> work.
227227
228228### Small Changes (Direct PR)
from line 238
238238### Major Changes (SEP Required)
239239
240240Anything that changes the MCP specification requires following the
241[Specification Enhancement Proposal (SEP)](/community/sep-guidelines) process. This includes, but
241[Specification Enhancement Proposal (SEP)](/community/sep-guidelines.md) process. This includes, but
242242is not limited to:
243243
244244* New protocol features or API methods
from line 325
325325
326326### Major Protocol Changes
327327
328For significant changes, follow the [SEP process](/community/sep-guidelines). Prior to spending a
328For significant changes, follow the [SEP process](/community/sep-guidelines.md). Prior to spending a
329329lot of time on a spec proposal, make sure to follow these best practices.
330330
331331**1. Validate your idea first**
332332
333Discuss in an [Interest Group](/community/working-interest-groups) or on
333Discuss in an [Interest Group](/community/working-interest-groups.md) or on
334334[Discord](https://discord.gg/6CSzBmMkjX).
335335
336336**2. Build a prototype**
from line 346
346346
347347**4. Write the SEP**
348348
349Follow the [SEP Guidelines](/community/sep-guidelines).
349Follow the [SEP Guidelines](/community/sep-guidelines.md).
350350
351351### Finding a Sponsor for SEPs
352352
from line 451
451451
452452Got questions or need guidance? The MCP community is here to help.
453453
454* **[Discord](/community/communication#discord)** - Real-time discussion with contributors and
454* **[Discord](/community/communication.md#discord)** - Real-time discussion with contributors and
455455 maintainers, focused on MCP contributions (not general MCP support)
456456* **[GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions)**
457457 \- Exploration and conversation: **feature requests**, questions, roadmap planning, and proposals
from line 462
462462
463463This separation helps maintainers focus on work that's ready for implementation while giving ideas
464464room to develop. If you're unsure whether something is ready to be an issue, start with a
465discussion. For a complete guide, see our [Contributor Communication](/community/communication)
465discussion. For a complete guide, see our [Contributor Communication](/community/communication.md)
466466documentation.
467467
468For protocol discussions, join [Working Group](/community/working-interest-groups) channels like
468For protocol discussions, join [Working Group](/community/working-interest-groups.md) channels like
469469`#auth-wg` or `#server-identity-wg`. For SDK help, find your language's channel (e.g.,
470470`#typescript-sdk-dev`).
471471
from line 473
473473
474474Sometimes things don't go as planned - that's completely normal! Here are solutions to common
475475issues. If you're still stuck, don't hesitate to ask for help in
476[Discord](/community/communication#discord). The community is friendly and happy to help you get
476[Discord](/community/communication.md#discord). The community is friendly and happy to help you get
477477unstuck.
478478
479479### `npm run check` fails
from line 525
525525Building your own MCP servers, clients, or tools is **not** covered here. For guidance on building
526526with MCP, see our documentation:
527527
528* [Build a Server](/docs/develop/build-server)
529* [Build a Client](/docs/develop/build-client)
530* [Example Servers](/examples)
528* [Build a Server](/docs/develop/build-server.md)
529* [Build a Client](/docs/develop/build-client.md)
530* [Example Servers](/examples.md)
531531
532532If you build something you'd like to share with the community, you can submit it to the
533[MCP Registry](/registry/about).
533[MCP Registry](/registry/about.md).
534534
535535## AI Contributions
536536
No line in this hunk matches that.