Contributor Ladder changedcommunity/contributor-ladder
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+86added
Lines−305removed
From line
1
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits7to this page, all time
## Roles at a glance ## Leading a working or interest group ## Advancement process ## Escalation ## Inactivity, stepping down and removal ### Inactivity ### Stepping down ### Emeritus status ### Removal ## Guiding Principles ## Roles at a Glance ## Working Group and Interest Group Leadership ## Advancement Process ### Self-Nomination vs. Recognition ### Process Steps ## Decision-Making and Escalation ### Delegation as Default ### Escalation Matrix ## Contribution Pathways ## Stepping Down and Emeritus Status ## Recognition and Visibility
The whole hunk
from line 1, old and new numbered
/
from line 1
11# Contributor Ladder
22
3> Roles, responsibilities, and advancement criteria for MCP contributors, from first contribution to Core Maintainer
3> The contributor roles in the MCP project, what each requires and grants, and how people move between them.
44
5The Model Context Protocol contributor ladder defines roles, responsibilities, and advancement criteria for the project. It shows community members how to grow their involvement from a first contribution to project leadership.
5This page defines the contributor roles in the MCP project, what each requires and grants, and how people move between them. It was adopted by [SEP-2148](https://modelcontextprotocol.io/seps/2148.md), a Specification Enhancement Proposal (SEP), and is changed by a Process SEP. Authority between roles is defined in [Governance](https://modelcontextprotocol.io/community/governance.md#roles), and the group-level roles (WG Member, WG Lead, IG Facilitator) in [Working Groups and Interest Groups](https://modelcontextprotocol.io/community/working-interest-groups.md).
66
7This document implements [SEP-2148](https://modelcontextprotocol.io/seps/2148-contributor-ladder.md). For Working Group and Interest Group governance, see [SEP-2149](https://modelcontextprotocol.io/seps/2149-working-group-charter-template.md).
7## Roles at a glance
88
9## Guiding Principles
10
11* **Earned Trust.** Advancement follows from demonstrated contributions, good judgment, and sustained engagement. Tenure alone is not enough.
12* **Multiple Growth Pathways.** Code, specification work, documentation, and community building all lead to advancement.
13* **Transparency.** Criteria for advancement are explicit and applied consistently.
14* **Alignment With MCP Goals.** Contributors must show commitment to MCP beyond any single employer's interests.
15
16## Roles at a Glance
17
18| Role | Summary | Key Privileges | Minimum Timeline |
9| Role | What it is | Access granted | Minimum time |
1910| - | - | - | - |
20| [**Contributor**](#contributor) | Anyone who contributes to MCP | Submit issues, PRs, participate in discussions | Immediate |
21| [**Member**](#member) | Established, active contributor | GitHub org membership, triage rights, eligible for WG/IG leadership | 2-3 months of meaningful contributions |
22| [**Maintainer**](#maintainer) | Area steward with operational responsibility | Merge rights, release participation | 6+ months as Member |
23| [**Core Maintainer**](#core-maintainer) | Technical leadership and protocol stewardship | Final decision authority, governance participation | By invitation after sustained Maintainer contribution |
24| [**Lead Maintainer**](#lead-maintainer) | Ultimate project authority (founders) | All Core Maintainer privileges, veto authority, appoints Core Maintainers | Reserved for project founders; succession only |
25| [**Community Moderator**](#community-moderator) | CoC enforcement and community health | Moderation rights on community platforms, incident handling | Parallel track: Member status + appointment |
11| [Contributor](#contributor) | Anyone who has contributed to MCP in any form | None; issues, pull requests and discussions are open to all | None |
12| [Member](#member) | Established, active contributor | GitHub organization membership, triage rights | 2-3 months of active participation |
13| [Maintainer](#maintainer) | Steward of a named area (an SDK, a tool, a docs area, a group) | Merge rights in the area, listed in [`MAINTAINERS.md`](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md) | 6 months as Member |
14| [Core Maintainer](#core-maintainer) | Project-wide technical leadership; authority in [Governance](https://modelcontextprotocol.io/community/governance.md#roles) | Administrative rights on all repositories | By invitation after sustained Maintainer contribution |
15| [Lead Maintainer](#lead-maintainer) | Founding role; authority in [Governance](https://modelcontextprotocol.io/community/governance.md#roles) | Administrative rights on all repositories and infrastructure | Founders and their successors only |
16| [Community Moderator](#community-moderator) | Code of Conduct enforcement and incident handling | Moderation tools on Discord and GitHub Discussions | Member status; parallel track |
2617
27> [!NOTE]
28>
29> Timelines are minimums, not guarantees. They protect the project from rapid
30> privilege escalation and ensure a high bar of demonstrated commitment. Actual
31> advancement is discretionary and may take longer. Exceptions require explicit
32> Core Maintainer approval with documented rationale.
18Timelines are minimums, advancement is discretionary, and an exception requires Core Maintainer approval with written rationale. Code, specification text, documentation, triage, security work, community work and moderation all count equally toward every role.
3319
34***
35
3620## Contributor
3721
38Anyone who has contributed to MCP in any form is a Contributor. This includes opening issues, submitting pull requests, participating in working group discussions, improving documentation, or helping other community members.
22A Contributor is anyone who has contributed to MCP in any form: issues, pull requests, group discussion, documentation, or help to others. There are no formal requirements. Start at [Contributing](https://modelcontextprotocol.io/community/contributing.md#where-to-start) and join the channels listed in [Communication](https://modelcontextprotocol.io/community/communication.md).
3923
40**There are no formal requirements.** We welcome all contributions that follow our contributing guidelines.
41
42**Getting started:**
43
44* Review the [Contributing Guide](https://modelcontextprotocol.io/community/contributing.md)
45* Join community channels (Discord, GitHub Discussions)
46* Look for issues tagged `good-first-issue` or `help-wanted`
47* Attend working group meetings
48
49***
50
5124## Member
5225
53Members are established contributors with a record of ongoing commitment to MCP.
26**Requirements.** Several contributions to MCP, including at least one merged pull request or accepted contribution. Ongoing engagement over 2-3 months rather than one-off contributions. Two-factor authentication enabled on GitHub. No objection from existing Members within 7 days of nomination.
5427
55**Requirements:**
28**Sponsorship and approval.** Sponsored by two Members or Maintainers from different organizations, or by one Core Maintainer or Lead Maintainer. Approved by no-objection.
5629
57* Multiple contributions to MCP (code, documentation, and/or community)
58* At least one merged PR or accepted contribution
59* Ongoing engagement with the community, not just one-off contributions
60* Two-factor authentication enabled on GitHub
61* No objections from existing Members within 7 days
30**Duties.** Respond to issues and pull requests assigned to you. Help onboard new contributors when you can. Follow the [Code of Conduct](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/CODE_OF_CONDUCT.md).
6231
63**Sponsorship:**
32**Privileges.** GitHub organization membership with triage rights. Can be assigned issues and pull requests and use review commands such as `/lgtm`. Pull request creation on the specification repository follows [Contributing](https://modelcontextprotocol.io/community/contributing.md#change-the-specification-or-docs). Eligible to serve as WG Lead or IG Facilitator. The member lists in the [access repository](https://github.com/modelcontextprotocol/access) are the roster. No separate list is published.
6433
65* Sponsored by two existing Members or Maintainers from different organizations, **or**
66* Sponsored by one Core Maintainer or Lead Maintainer
34**Minimum time.** 2-3 months of active participation.
6735
68**Minimum timeline:** 2-3 months of active participation
69
70**Responsibilities:**
71
72* Continue contributing in good faith
73* Respond to assigned issues and PRs
74* Follow community guidelines and the code of conduct
75* Help onboard new contributors when possible
76
77**Privileges:**
78
79* GitHub organization membership with triage rights
80* Can be assigned to issues and PRs
81* Can use shortcut approval or review commands on PRs, such as `/lgtm`
82* Listed in the community membership roster
83* Can create PRs in restricted repositories
84* Eligible for Working Group Lead or Interest Group Facilitator roles
85
86**Inactivity:** Members with no contributions for 3 months may be moved to emeritus status. Re-engagement follows a simplified re-familiarization process.
87
88***
89
9036## Maintainer
9137
92Maintainers are trusted stewards who take operational responsibility for specific areas.
38**Requirements.** Six or more months as a Member with sustained contributions. Leadership or ownership of something concrete: an SDK, a tool, a documentation area, a working or interest group, or a significant initiative. Acting for the project over the interests of any employer. Knowledge of the [roadmap](https://modelcontextprotocol.io/development/roadmap.md), the [design principles](https://modelcontextprotocol.io/community/design-principles.md) and how the area is used in practice. Completed security and governance onboarding.
9339
94**Requirements:**
40**Sponsorship and approval.** Sponsored by one Maintainer or Core Maintainer. Approved by Core Maintainers.
9541
96* Member for at least 6 months with sustained, high-quality contributions
97* Demonstrated leadership in working groups or significant initiatives
98* Ability to represent MCP's interests above those of any single employer or organization
99* Deep understanding of the MCP vision, roadmap, and design principles
100* Understanding of how the area impacts real-world AI integration and model interaction patterns
101* Completed security and governance onboarding
42**Duties.**
10243
103**Sponsorship and Approval:**
44* Own the operational health of the area, including test stability, documentation currency, the release process and milestone planning.
45* Review escalated decisions within the timelines under [Escalation](#escalation), and make sure proposals that reach Core Maintainers are refined and account for ecosystem-wide impact.
46* Mentor Members and sponsor future Maintainers.
47* Speak for the area's users, represent MCP externally when asked, and take part in roadmap and governance discussions and in the project's GitHub and Discord channels.
10448
105* Sponsored by an existing Maintainer or Core Maintainer
106* Approved by Core Maintainers
49**Privileges.** Merge rights in owned areas. May sponsor Members, Maintainers and SEPs (see [SEP Guidelines](https://modelcontextprotocol.io/community/sep-guidelines.md#sponsors)). Included in roadmap and prioritization discussions. Listed in [`MAINTAINERS.md`](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md).
10750
108**Responsibilities:**
51**Minimum time.** 6 months as Member.
10952
110* Own the operational health of the area (test stability, documentation currency)
111* Run release processes and milestone planning for the scope
112* Provide timely review of escalated decisions
113* Participate actively in governance discussions
114* Mentor Members and develop future Maintainers
115* Represent MCP in external contexts when appropriate
116* Engage with the area ecosystem and stakeholders; understand real-world usage and represent community needs
117* Ensure proposals reaching Core Maintainers are refined, well-considered, and account for ecosystem-wide impact
118* Participate actively in discussions on communication channels (GitHub issues, Discord)
119
120**Privileges:**
121
122* Merge privileges for owned areas
123* Can sponsor new Maintainers
124* Participate in roadmap and prioritization discussions
125* Listed in `MAINTAINERS.md`
126
127**Inactivity:** Maintainers with no contributions for 6 months may be moved to emeritus status following review by Core Maintainers. Merge rights are revoked upon emeritus transition. Re-engagement requires completing security and governance onboarding again.
128
129All contribution pathways can lead to Maintainer. The specific scope will align with the contribution type.
130
131***
132
13353## Core Maintainer
13454
135Core Maintainers hold final decision-making authority for MCP's technical direction. This is the highest level of trust in the community.
55**Requirements.** Six or more months as a Maintainer or in equivalent standing. Demonstrated judgment on project-wide decisions. Trusted across organizations.
13656
137> [!NOTE]
138>
139> The Core Maintainer role is intentionally limited. This ensures a coherent
140> technical vision while the project scales. Bandwidth concerns are addressed
141> through delegation to Maintainers, Working Group Leads, and Interest Group
142> Facilitators, not by expanding Core Maintainer numbers.
57**Sponsorship and approval.** Nominated by a majority of Core Maintainers and approved by Lead Maintainers, or appointed directly by Lead Maintainers. Removal is by Lead Maintainers (see [Governance](https://modelcontextprotocol.io/community/governance.md#roles)).
14358
144**Requirements:**
59**Duties.** Steward the design principles and the roadmap, and hold to long-term restraint in protocol evolution. Decide contested and cross-cutting technical questions and governance matters under the [decision process](https://modelcontextprotocol.io/community/governance.md#decision-process). Represent the project externally, plan succession, and watch community health. Attend the Core Maintainer meeting every two weeks and [Steering Group](https://modelcontextprotocol.io/community/governance.md#roles) meetups.
14560
146* Sustained contribution as Maintainer or similar role over at least 6 months
147* Demonstrated judgment on complex, project-wide decisions
148* Trust and respect across organizational boundaries
149* Deep commitment to MCP's long-term success
61**Privileges.** Vote on SEPs and governance matters. Approve Maintainers, breaking changes and major specification revisions. Administrative rights on all MCP repositories. Listed in [`MAINTAINERS.md`](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md).
15062
151**Appointment:**
63**Minimum time.** By invitation after sustained Maintainer contribution.
15264
153* Nominated by a majority of Core Maintainers and approved by Lead Maintainers, **or**
154* Direct appointment by Lead Maintainers
65The group is kept small and delegates to Maintainers, WG Leads and IG Facilitators rather than growing. When evaluating candidates, Core Maintainers consider whether it reflects the breadth of MCP adoption, including enterprise adopters running MCP in production.
15566
156When evaluating candidates, Core Maintainers should consider whether the current composition adequately represents the breadth of the MCP ecosystem. This includes enterprise adopters deploying MCP in production.
157
158**Responsibilities:**
159
160* Final technical decision authority for contested or cross-cutting issues
161* Stewardship of project vision and design principles
162* Governance and policy decisions
163* External representation of MCP
164* Succession planning and community health
165* Ensure restraint and sustainability in protocol evolution
166* Attend Core Maintainer meetings and meetups
167
168**Privileges:**
169
170* Final approval on breaking changes and major spec revisions
171* Voting rights on [SEPs](https://modelcontextprotocol.io/community/sep-guidelines.md)
172* Approval of Maintainers
173* Governance voting rights and expectation of governance participation
174* Administrative rights to all MCP GitHub repositories
175* Listed in `MAINTAINERS.md` as Core Maintainer
176
177**Inactivity:** Core Maintainers with no participation in governance or technical decisions for 6 months may be moved to emeritus status following review by Lead Maintainers. Given the visibility of this role, Core Maintainers should proactively communicate reduced availability.
178
179***
180
18167## Lead Maintainer
18268
183Lead Maintainers hold ultimate authority over MCP's direction and governance. This is a lifetime appointment reserved for project founders. There is no advancement path to this role. It is only assumed through succession (see [Succession](#succession)).
69Lead Maintainer is the founding role, held for life, with no advancement path into it. A Lead Maintainer holds every Core Maintainer duty and privilege plus the powers listed in [Governance](https://modelcontextprotocol.io/community/governance.md#roles) (veto, appointment and removal of Core Maintainers, acting alone).
18470
185**Responsibilities:**
186
187* All Core Maintainer responsibilities
188* Appoint and remove Core Maintainers
189* Final authority on contested governance decisions
190* Project-wide strategic direction
191
192**Privileges:**
193
194* Can act alone where Core Maintainers require multiple approvals
195* Veto authority over any decision
196* Appoints successor
197
19871### Succession
19972
200If a Lead Maintainer leaves the role for any reason, succession begins upon their written notice. If they cannot give notice, the remaining Lead Maintainers or Core Maintainers may determine that the Lead Maintainer is unable to continue serving.
73If a Lead Maintainer leaves the role for any reason, succession begins on their written notice or, if they cannot give notice, when the remaining Lead Maintainers or the Core Maintainers determine that the Lead Maintainer is unable to continue serving.
20174
202If one or more Lead Maintainers remain, they appoint a successor. If more than one remains, they decide by majority vote. The remaining Lead Maintainers continue to govern until a successor is appointed.
75While one or more Lead Maintainers remain, they appoint the successor, by majority vote if more than one remains, and continue to govern until the successor is appointed. If no Lead Maintainers remain, the Core Maintainers appoint a successor by majority vote within 30 days, and the project operates by two-thirds vote of Core Maintainers until a new Lead Maintainer is appointed.
20376
204If no Lead Maintainers remain, the Core Maintainers appoint a successor by majority vote within 30 days. Until a new Lead Maintainer is appointed, the project operates by two-thirds vote of Core Maintainers.
205
206***
207
20877## Community Moderator
20978
210Community Moderators help keep the MCP community healthy, safe, and welcoming. This role focuses on moderation and Code of Conduct enforcement rather than technical contribution.
79**Requirements.** Member status. Composure and good judgment in community interactions. Working knowledge of the [Code of Conduct](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/CODE_OF_CONDUCT.md). Discretion and fairness in sensitive situations.
21180
212**Requirements:**
81**Sponsorship and approval.** Sponsored and approved by one Core Maintainer or Lead Maintainer. Core Maintainers may remove a moderator for failure to uphold moderation standards or for Code of Conduct violations. A moderator may step down at any time.
21382
214* Member status minimum
215* Demonstrated good judgment and composure in community interactions
216* Understanding of the MCP Code of Conduct and community guidelines
217* Ability to handle sensitive situations with discretion and fairness
83**Duties.**
21884
219**Sponsorship:**
85* Watch community channels, including Discord and GitHub Discussions, for Code of Conduct violations.
86* Triage and respond to Code of Conduct reports, and escalate serious or complex incidents to Core Maintainers.
87* Coordinate with other moderators so that enforcement is consistent.
88* Record moderation actions and keep incident details confidential.
89* Recuse from any incident you are party to. Those incidents go directly to Core Maintainers.
22090
221* Sponsored by a Core Maintainer or Lead Maintainer
91**Privileges.** Moderation rights and tools on Discord and GitHub Discussions, and access to private moderator channels. May warn, mute or temporarily ban users for Code of Conduct violations. Listed in [`MAINTAINERS.md`](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md#community-moderators).
22292
223**Responsibilities:**
93**Minimum time.** None beyond Member status.
22494
225* Monitor community channels (Discord, GitHub Discussions, etc.) for Code of Conduct adherence
226* Handle Code of Conduct incident reports, including initial triage and response
227* Escalate serious or complex incidents to Core Maintainers
228* Help maintain a welcoming and inclusive environment
229* Coordinate with other moderators to ensure consistent enforcement
230* Document moderation actions and maintain confidentiality of incident details
231* Recuse from any incident involving them personally; such incidents go directly to Core Maintainers
95Community Moderator is a parallel track that may be held alongside any other role and is not a prerequisite for technical advancement. Moderation work counts toward every role.
23296
233**Privileges:**
97## Leading a working or interest group
23498
235* Moderation rights on community platforms (Discord, GitHub Discussions)
236* Access to moderation tools and private moderation channels
237* Authority to issue warnings, mute, or temporarily ban users for Code of Conduct violations
238* Listed in the community moderator roster
99WG Lead and IG Facilitator require Member status, not Maintainer status, and the work counts toward advancement to Maintainer. Their requirements, sponsorship and duties are defined in [Working Groups and Interest Groups](https://modelcontextprotocol.io/community/working-interest-groups.md#leadership).
239100
240**Relationship to Contributor Ladder:** Community Moderator is a parallel track, not a prerequisite for technical advancement. Moderator experience counts toward any role, especially where community judgment matters. Moderators may hold other roles at the same time (Member, Maintainer, etc.).
101## Advancement process
241102
242**Removal:** Core Maintainers may remove Community Moderators for failure to uphold moderation standards or for Code of Conduct violations. Moderators may step down voluntarily at any time.
103You may nominate yourself or be nominated by a sponsor. Self-nominees still need the sponsors listed below.
243104
244***
1051. The nominee or a sponsor opens an issue in the [specification repository](https://github.com/modelcontextprotocol/modelcontextprotocol) using the nomination template, with links to the contributions that meet the role's requirements.
1062. Sponsors confirm their support in the thread.
1073. A 7-day community comment period runs.
1084. The approving body decides and records the outcome in the thread.
1095. Access is provisioned through the [access repository](https://github.com/modelcontextprotocol/access) and the new role-holder completes onboarding.
245110
246## Working Group and Interest Group Leadership
111| Role | Sponsors | Approved by |
112| - | - | - |
113| Member | 2 Members or Maintainers from different organizations, or 1 Core or Lead Maintainer | No objection from existing Members within 7 days |
114| Maintainer | 1 Maintainer or Core Maintainer | Core Maintainers |
115| Core Maintainer | Nominated by a majority of Core Maintainers | Lead Maintainers, who may instead appoint directly |
116| Community Moderator | 1 Core or Lead Maintainer | The sponsoring Core or Lead Maintainer |
247117
248Working Group (WG) Leads and Interest Group (IG) Facilitators are a form of community leadership that does not require Maintainer status. WG and IG leadership centers on facilitation and coordination rather than merge authority.
118## Escalation
249119
250The full governance rules for WGs and IGs are defined in [SEP-2149: MCP Group Governance and Charter Template](https://modelcontextprotocol.io/seps/2149-working-group-charter-template.md). These include participation tiers, decision-making process, meeting requirements, and lifecycle.
120Decisions are made at the lowest level that owns the matter and are recorded in writing. Maintainers, WG Leads and IG Facilitators handle day-to-day decisions within their scope. Core Maintainers act on escalation, on cross-cutting questions, and where a process requires them, such as specification changes and Maintainer approval. Lead Maintainers act only on contested governance decisions or when Core Maintainers cannot reach a decision. Escalate only when you are blocked, when the decision has project-wide effect, or when a process on these pages requires it.
251121
252**Requirements:**
253
254* Member status minimum
255* Demonstrated sustained engagement with the group's scope
256* Good facilitation and communication skills
257* Ability to represent multiple perspectives fairly
258* Group and its leadership sponsored by at least two Core Maintainers or one Lead Maintainer
259
260**Relationship to Contributor Ladder:**
261
262* WG Lead and IG Facilitator experience is valuable for advancement to Maintainer
263* Leads and Facilitators without Maintainer status work with Maintainers for merge decisions
264* Leads and Facilitators have authority over group operations but not spec approval
265* WG Leads and Maintainers may sponsor SEPs
266* WG Leads may triage SEPs in their scope area. This includes closing SEPs that do not fit the roadmap. Closures require documented rationale, and authors may appeal to Core Maintainers.
267
268***
269
270## Advancement Process
271
272### Self-Nomination vs. Recognition
273
274Contributors may either:
275
2761. **Self-nominate** when they believe they meet the requirements
2772. **Be nominated** by a sponsor who has observed their contributions
278
279Both paths are equally valid. Self-nomination is encouraged. It shows initiative and self-awareness of one's contribution scope.
280
281### Process Steps
282
2831. **Nomination.** The nominee or sponsor opens an issue using the nomination template. It must include links to contributions that demonstrate the requirements, plus sponsor confirmations.
2842. **Community Review.** A 7-day period follows for community input.
2853. **Decision.** The approving authority reviews and decides.
2864. **Onboarding.** The new role-holder receives appropriate access and onboarding.
287
288| Advancement To | Approved By |
289| - | - |
290| Member | 2 existing Members+ from different organizations, **or** 1 Core/Lead Maintainer |
291| Maintainer | 1 Maintainer or Core Maintainer sponsor + Core Maintainer approval |
292| Core Maintainer | Lead Maintainers |
293| Community Moderator | 1 Core Maintainer or Lead Maintainer |
294
295Nominees who self-nominate must still secure the required sponsorship. Sponsors confirm support in the nomination issue.
296
297***
298
299## Decision-Making and Escalation
300
301### Delegation as Default
302
303MCP operates on a principle of delegation. Decisions should be made at the lowest appropriate level. This lets the project move quickly while preserving Core Maintainer bandwidth for cross-cutting concerns.
304
305* **Maintainers, WG Leads, and IG Facilitators** handle day-to-day decisions within scope.
306* **Core Maintainers** intervene on escalation, cross-cutting issues, or when required by process (spec changes, Maintainer approval).
307* **Lead Maintainers** intervene only on contested governance decisions or when Core Maintainers cannot reach consensus.
308
309When in doubt, make the decision at your level and document it. Escalate only when blocked, when the decision has project-wide implications, or when process explicitly requires it.
310
311The detailed escalation procedure for Working Group and Interest Group disputes is defined in [SEP-2149 §1.5](https://modelcontextprotocol.io/seps/2149-working-group-charter-template.md). It includes the designation of a Core Maintainer without shared organizational affiliation to resolve the issue.
312
313### Escalation Matrix
314
315| Issue Type | First Escalation | Second Escalation | Timeline |
122| Issue type | First escalation | Second escalation | Response time |
316123| - | - | - | - |
317| Technical disagreement in PR | Maintainer in scope | Core Maintainer | 5 business days |
318| Technical disagreement in WG | WG Lead | Core Maintainer | 5 business days |
319| Technical disagreement in IG | IG Facilitator | Core Maintainer | 5 business days |
320| Disagreement with WG Lead / IG Facilitator | Core Maintainer | Lead Maintainer | 7 business days |
321| Disagreement with Maintainer decision | Core Maintainer | Lead Maintainer | 7 business days |
322| Core Maintainer disagreement | Lead Maintainer | N/A | 10 business days |
124| Technical disagreement in a pull request | Maintainer in scope | Core Maintainer | 5 business days |
125| Technical disagreement in a working group | WG Lead | Core Maintainer | 5 business days |
126| Technical disagreement in an interest group | IG Facilitator | Core Maintainer | 5 business days |
127| Disagreement with a WG Lead or IG Facilitator | Core Maintainer | Lead Maintainer | 7 business days |
128| Disagreement with a Maintainer decision | Core Maintainer | Lead Maintainer | 7 business days |
129| Disagreement among Core Maintainers | Lead Maintainer | None | 10 business days |
323130| Code of Conduct violation | Community Moderator | Core Maintainer | Immediate |
324131| Security issue | Core Maintainer | Lead Maintainer | Immediate |
325132
326**Escalation process:**
133A vulnerability is reported through a private advisory first (see [Reporting a vulnerability](https://modelcontextprotocol.io/community/policies.md#reporting-a-vulnerability)). The security row is the maintainer-internal escalation once a report exists.
327134
3281. Document the decision, the options considered, and the points of disagreement
3292. Present to the escalation authority with a clear ask
3303. The escalation authority either (a) provides binding guidance, (b) requests more information, or (c) escalates further if needed
135To escalate:
331136
332***
1371. Document the decision, the options considered and the points of disagreement.
1382. Present it to the escalation authority with a clear ask.
1393. The escalation authority gives binding guidance, asks for more information, or escalates further.
333140
334## Contribution Pathways
141Disputes inside a working or interest group follow [Working Groups and Interest Groups](https://modelcontextprotocol.io/community/working-interest-groups.md#escalation), which lists the disputes that go straight to Core Maintainers and requires that the Core Maintainer designated to resolve a group dispute share no organizational affiliation with the parties.
335142
336MCP values diverse contributions. All of these pathways can lead to advancement.
143## Inactivity, stepping down and removal
337144
338**Code Contributions.** SDK development (TypeScript, Python, etc.), testing infrastructure, tooling and developer experience.
145### Inactivity
339146
340**Specification Work.** Drafting or refining spec text, [SEP](https://modelcontextprotocol.io/community/sep-guidelines.md) authorship or co-authorship, protocol design participation, compatibility analysis.
147Members with no contributions for 3 months may be moved to emeritus status. Returning Members go through a simplified re-familiarization. Maintainers with no contributions for 6 months may be moved to emeritus status after Core Maintainer review, and the move revokes their merge rights. Returning Maintainers repeat the security and governance onboarding. Lead Maintainers review a Core Maintainer after 6 months without participation in governance or technical decisions and may move them to emeritus status. Core Maintainers should say early when their availability drops.
341148
342**Documentation.** User guides and tutorials, API documentation, architecture documentation, keeping content current.
149### Stepping down
343150
344**Community Building.** Onboarding new contributors, working group facilitation, community support (Discord, GitHub discussions), event organization or representation.
151You may step down from any role for any reason. Tell the WG Lead, IG Facilitator, Maintainer or Core Maintainer you work with, hand over open work, and move to emeritus status.
345152
346**Quality and Security.** Bug triage and reproduction, security review and analysis, test coverage improvement, release validation.
153### Emeritus status
347154
348***
155Emeritus role-holders keep their recognition in [`MAINTAINERS.md`](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md) and release notes and hold no duties or privileges.
349156
350## Stepping Down and Emeritus Status
157### Removal
351158
352Contributors may step down from roles for any reason. This is normal and healthy.
353
354**Process:**
355
3561. Notify relevant leadership (WG Lead, IG Facilitator, Maintainer, or Core Maintainer as appropriate)
3572. Help transition any ongoing work
3583. Move to emeritus status
359
360**Emeritus status:**
361
362* Recognized for past contributions
363* May return to active status with abbreviated re-onboarding
364* No ongoing responsibilities or privileges
365
366**Involuntary Removal.** Roles may be revoked for code of conduct violations or sustained non-participation. Removal follows appropriate review processes.
367
368***
369
370## Recognition and Visibility
371
372The community recognizes contributors through:
373
374* **Contributor lists** such as `MAINTAINERS.md`
375* **GitHub teams** for appropriate access
376* **Public acknowledgment** in release notes
377* **Speaking opportunities** at community events
378* **Badges** (if implemented) on community platforms
159A role may be revoked for Code of Conduct violations or sustained non-participation, following appropriate review.
379160
No line in this hunk matches that.