Roles at a glance
Timelines 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.
Contributor
A 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 and join the channels listed in Communication. Pull requests on the specification repository are opened by Members. Other repositories set their own rules in their contributing guides.Member
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. Sponsorship and approval. Sponsored by two Members or Maintainers from different organizations, or by one Core Maintainer or Lead Maintainer. Approved by no-objection. Duties. Respond to issues and pull requests assigned to you. Help onboard new contributors when you can. Follow the Code of Conduct. Privileges. GitHub organization membership with triage rights. Can be assigned issues and pull requests and use review commands such as/lgtm. Can open pull requests on the specification repository, as set out in Contributing. Eligible to serve as WG Lead or IG Facilitator. The member lists in the access repository are the roster. No separate list is published.
Minimum time. 2-3 months of active participation.
Maintainer
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, the design principles and how the area is used in practice. Completed security and governance onboarding. Sponsorship and approval. Sponsored by one Maintainer or Core Maintainer. Approved by Core Maintainers. Duties.- Own the operational health of the area, including test stability, documentation currency, the release process and milestone planning.
- Review escalated decisions within the timelines under Escalation, and make sure proposals that reach Core Maintainers are refined and account for ecosystem-wide impact.
- Mentor Members and sponsor future Maintainers.
- 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.
MAINTAINERS.md.
Minimum time. 6 months as Member.
Core Maintainer
Requirements. Six or more months as a Maintainer or in equivalent standing. Demonstrated judgment on project-wide decisions. Trusted across organizations. 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). 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. Represent the project externally, plan succession, and watch community health. Attend the Core Maintainer meeting every two weeks and Steering Group meetups. Privileges. Vote on SEPs and governance matters. Approve Maintainers, breaking changes and major specification revisions. Administrative rights on all MCP repositories. Listed inMAINTAINERS.md.
Minimum time. By invitation after sustained Maintainer contribution.
The 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.
Lead Maintainer
Lead 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 (veto, appointment and removal of Core Maintainers, acting alone).Succession
If 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. While 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.Community Moderator
Requirements. Member status. Composure and good judgment in community interactions. Working knowledge of the Code of Conduct. Discretion and fairness in sensitive situations. 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. Duties.- Watch community channels, including Discord and GitHub Discussions, for Code of Conduct violations.
- Triage and respond to Code of Conduct reports, and escalate serious or complex incidents to Core Maintainers.
- Coordinate with other moderators so that enforcement is consistent.
- Record moderation actions and keep incident details confidential.
- Recuse from any incident you are party to. Those incidents go directly to Core Maintainers.
MAINTAINERS.md.
Minimum time. None beyond Member status.
Community 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.
Leading a working or interest group
WG 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.Advancement process
You may nominate yourself or be nominated by a sponsor. Self-nominees still need the sponsors listed below.- The nominee or a sponsor opens an issue in the specification repository using the nomination template, with links to the contributions that meet the role’s requirements.
- Sponsors confirm their support in the thread.
- A 7-day community comment period runs.
- The approving body decides and records the outcome in the thread.
- Access is provisioned through the access repository and the new role-holder completes onboarding.
Escalation
Decisions 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.
A vulnerability is reported through a private advisory first (see Reporting a vulnerability). The security row is the maintainer-internal escalation once a report exists.
Maintainers who learn of an actively exploited vulnerability or a severe incident must follow the EU Cyber Resilience Act (CRA) escalation rule. They must notify a Core Maintainer or Lead Maintainer immediately in
#security-disclosures on Discord while they fix the problem, and that Core Maintainer or Lead Maintainer works with the Linux Foundation CRA steward.
To escalate:
- Document the decision, the options considered and the points of disagreement.
- Present it to the escalation authority with a clear ask.
- The escalation authority gives binding guidance, asks for more information, or escalates further.
Inactivity, stepping down and removal
Inactivity
Members 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.Stepping down
You 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.Emeritus status
Emeritus role-holders keep their recognition inMAINTAINERS.md and release notes and hold no duties or privileges.