Create a maintainer onboarding document

[tadasant]

We have a bunch of things that need to happen anytime we add a maintainer:

• @modelcontextprotocol.io account
• Permissions to access infra
• GitHub permissions, Discord permissions
• Maybe more

Would be good to document and track so it's not just in our heads.

[mukteshkrmishra]

+1 to this. ^^.

[rdimitrov]

We should also cover the offboarding process so removing access is also consistent 👍

[allenfeng8]

I am new to MCP, and would love to work on this.

[domdomegg]

While it's more work initially, what might give us more transparency + audit logging + peer approval is provisioning access to a lot of this stuff automatically with infrastructure-as-code.

I think we'd want to do this as a separate MCP project, not specific to registry.

E.g. with Pulumi you can create and manage:

• GitHub teams
• Google Workspace users and groups
• Discord role assignments

We could then have something where people update one YAML file, and then that reflects across all the systems + docs. And it's clear who was approved when, and why, and by who. Offboarding is equivalently simple, simply remove someone from the file.

Appreciate this is a bigger project, and perhaps the V1 of this issue is just documenting the current process, not improving it just yet!

[domdomegg]

I've put together https://github.com/modelcontextprotocol/access for the above, that does GitHub + Google Workspace. Want to get some feedback on it before we actually roll it out to manage all the groups, so just created some test groups for now.

[rdimitrov]

+1 👍 We've been using terraform to achieve the same thing and I can agree it has been quite nice but also convenient 👍