Skip to content

Commit 727db65

Browse files
authored
(chore) Create MAINTAINERS.md (modelcontextprotocol#1001)
* Create MAINTAINERS.md * Update MAINTAINERS.md * Update MAINTAINERS.md * Update MAINTAINERS.md * Update based on discussion * Update maintainers file * Update MAINTAINERS.md * Update governance.mdx * Update MAINTAINERS.md
1 parent 1138252 commit 727db65

File tree

3 files changed

+118
-1
lines changed

3 files changed

+118
-1
lines changed

MAINTAINERS.md

Lines changed: 113 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,113 @@
1+
# MCP Maintainers
2+
3+
This document lists current maintainers and working groups in the Model Context Protocol project.
4+
5+
**Last updated:** July 23, 2025
6+
7+
## Lead Maintainers
8+
9+
- [Justin Spahr-Summers](https://github.com/jspahrsummers)
10+
- [David Soria Parra](https://github.com/dsp-ant)
11+
12+
## Core Maintainers
13+
14+
- [Inna Harper](https://github.com/ihrpr)
15+
- [Basil Hosmer](https://github.com/bhosmer-ant)
16+
- [Paul Carleton](https://github.com/pcarleton)
17+
- [Nick Cooper](https://github.com/nicknotfun)
18+
- Nick Aldridge
19+
- Che Liu
20+
- [Den Delimarsky](https://github.com/localden)
21+
22+
## SDK Maintainers
23+
24+
### Java SDK
25+
26+
- [Christian Tzolov](https://github.com/tzolov)
27+
- [Dariusz Jędrzejczyk](https://github.com/chemicL)
28+
29+
### Ruby SDK
30+
31+
- [Topher Bullock](https://github.com/topherbullock)
32+
- [Koichi Ito](https://github.com/koic)
33+
- [Ateş Göral](https://github.com/atesgoral)
34+
35+
### Swift SDK
36+
37+
- [Matt Zmuda](https://github.com/mattt)
38+
- [Carl Peaslee](https://github.com/carlpeaslee)
39+
40+
### Go SDK
41+
42+
- [Rob Findley](https://github.com/findleyr)
43+
44+
### C# SDK
45+
46+
- [Stephan Halter](https://github.com/halter73)
47+
- [Mike Kistler](https://github.com/mikekistler)
48+
49+
### Kotlin SDK
50+
51+
- [Leonid Stashevsky](https://github.com/e5l)
52+
- [Sergey Ignatov](https://github.com/ignatov)
53+
54+
### Python SDK
55+
56+
- [Inna Harper](https://github.com/ihrpr)
57+
- [Jerome Swannack](https://github.com/jerome3o)
58+
- [Samuel Colvin](https://github.com/samuelcolvin)
59+
- [Marcelo Trylesinski](https://github.com/Kludex)
60+
61+
### TypeScript SDK
62+
63+
- [Inna Harper](https://github.com/ihrpr)
64+
- [Felix Weinberger](https://github.com/felixweinberger)
65+
- [Olivier Chafik](https://github.com/ochafik)
66+
67+
### Rust SDK
68+
69+
- [Alex Hancock](https://github.com/alexhancock)
70+
71+
## Project Maintainers
72+
73+
- [Glen Maddern](https://github.com/geelen) (use-mcp)
74+
- [Ola Hungerford](https://github.com/olaservo) (Inspector, Reference Servers)
75+
- [Cliff Hall](https://github.com/cliffhall) (Inspector, Reference Servers)
76+
- [Toby Padilla](https://github.com/toby) (Registry)
77+
- [Tadas Antanavicius](https://github.com/tadasant) (Registry, Reference Servers)
78+
- [Shaun Smith](https://github.com/evalstate) (Reference Servers)
79+
- [Jonathan Hefner](https://github.com/jonathanhefner) (Reference Servers)
80+
81+
## Community Moderators
82+
83+
- [Ola Hungerford](https://github.com/olaservo)
84+
- [Cliff Hall](https://github.com/cliffhall)
85+
- [Shaun Smith](https://github.com/evalstate)
86+
- [Jonathan Hefner](https://github.com/jonathanhefner)
87+
- [Tadas Antanavicius](https://github.com/tadasant)
88+
89+
## Working Groups
90+
91+
### Security Working Group
92+
93+
- [Den Delimarsky](https://github.com/dend)
94+
- [Paul Carleton](https://github.com/pcarleton)
95+
- [Jenn Newton](https://github.com/jenn-newton)
96+
97+
### Authorization Working Group
98+
99+
- [Aaron Parecki](https://github.com/aaronpk)
100+
- [Darin McAdams](https://github.com/D-McAdams)
101+
- [Paul Carleton](https://github.com/pcarleton)
102+
103+
### Client Implementor Working Group
104+
105+
- [Michael Feldstein](https://github.com/msfeldstein)
106+
- [Harald Kirschner](https://github.com/digitarald)
107+
- [Connor Peet](https://github.com/connor4312)
108+
109+
## About This Document
110+
111+
This document is updated by the MCP maintainers and reflects the current
112+
governance structure. For more information about MCP governance, see our
113+
[governance documentation](https://modelcontextprotocol.io/community/governance).

docs/community/governance.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -144,3 +144,7 @@ The MCP project maintains a public Discord server with open chats for interest g
144144
- Nick Aldridge
145145
- Che Liu
146146
- Den Delimarsky
147+
148+
## Current Maintainers and Working Groups
149+
150+
Refer to [the maintainer list](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md).

docs/community/sep-guidelines.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Each SEP must have an **SEP author** -- someone who writes the SEP using the sty
4545
SEPs should be submitted as a GitHub Issue in the [specification repository](https://github.com/modelcontextprotocol/modelcontextprotocol). The standard SEP workflow is:
4646

4747
1. You, the SEP author, create a [well-formatted](#sep-format) GitHub Issue with the `SEP` and `proposal` tags. The SEP number is the same as the Github Issue number, the two can be used interchangably.
48-
2. Find a Core Maintainer or Maintainer to sponsor your proposal. Core Maintainers and Maintainers will regularly go over the list of open proposals to determine which proposals to sponsor.
48+
2. Core Maintainers and Maintainers will regularly go over the list of open proposals to determine which proposals to sponsor. You can tag relevant maintainers from [the maintainer list](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md) in your proposal.
4949
3. Once a sponsor is found, the GitHub Issue is assigned to the sponsor. The sponsor will add the `draft` tag, ensure the SEP number is in the title, and assign a milestone.
5050
4. The sponsor will informally review the proposal and may request changes based on community feedback. When ready for formal review, the sponsor will add the `in-review` tag.
5151
5. After the `in-review` tag is added, the SEP enters formal review by the Core Maintainers team. The SEP may be accepted, rejected, or returned for revision.

0 commit comments

Comments
 (0)