Skip to content

Commit 7d372f2

Browse files
CaitieM20CaitieM20
authored
Merge pull request modelcontextprotocol#2587 from tadasant/registry-wg-charter
docs(community): add Registry WG charter
2 parents 6abdad6 + cb6c24f commit 7d372f2

2 files changed

Lines changed: 110 additions & 0 deletions

File tree

‎docs/community/registry/charter.mdx‎

Lines changed: 109 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,109 @@
1+
---
2+
title: Registry Charter
3+
description: Charter for the MCP Registry Working Group.
4+
---
5+
6+
## Group Type
7+
8+
**Working Group**
9+
10+
## Mission Statement
11+
12+
The Registry Working Group exists to build and maintain the official MCP Registry — an open catalog and API for publicly available MCP servers — so that clients, sub-registries, and end users can discover, evaluate, and install servers with confidence. The WG owns the registry service, the `server.json` schema, the registry API specification, and the sub-registry ecosystem that further distributes server metadata.
13+
14+
## Scope
15+
16+
### In Scope
17+
18+
- **Registry Service**: Operation, reliability, and evolution of the hosted registry at `registry.modelcontextprotocol.io`, including uptime, monitoring, and incident response.
19+
- **Registry API Specification**: The OpenAPI spec defining how any registry (official or private) exposes server metadata.
20+
- **`server.json` Schema**: The standardized format for describing MCP server identity, packages, runtime configuration, and capabilities — coordinated with the Server Card WG to keep Server Card a coherent subset.
21+
- **Client SDKs**: Generated or hand-maintained client libraries that make it easy for clients and sub-registries to integrate with the registry API.
22+
- **Publishing & Trust**: Authentication flows (GitHub OAuth, GitHub OIDC, DNS/HTTP verification), namespace ownership, moderation tooling, and community-driven flagging.
23+
- **Adoption & Outreach**: Documentation, onboarding guides, and outreach to drive catalog coverage.
24+
- **Issue Triage & Automation**: Labeling system, triage, and contributor workflow for the registry repo.
25+
26+
### Out of Scope
27+
28+
- Any runtime-related MCP protocol specification aspects (owned by Core Maintainers and other WGs).
29+
- Server Card format and discovery mechanism (owned by the Server Card WG; this WG coordinates on `server.json` alignment).
30+
- Ranking/choosing between MCP server implementations on behalf of MCP clients or end-users.
31+
- Hosting, distributing, or executing MCP server code or binaries — the registry is a metadata catalog, not a package registry.
32+
- Any commitment to delivering an enterprise-ready or reusable registry implementation. The codebase supports this instance only and is not intended for external deployments.
33+
34+
### Related Groups
35+
36+
- **Server Card WG** — `server.json` and Server Card must stay aligned; the registry will expose Server Cards + local package-related metadata for published entries. Tight coordination required to avoid schema divergence.
37+
38+
## Leadership
39+
40+
| Role | Name | Organization | GitHub | Term |
41+
| ---- | ------------------ | ------------ | ------------------------------------------ | ------- |
42+
| Lead | Tadas Antanavicius | PulseMCP | [@tadasant](https://github.com/tadasant) | Initial |
43+
| Lead | Radoslav Dimitrov | Stacklok | [@rdimitrov](https://github.com/rdimitrov) | Initial |
44+
45+
## Authority & Decision Rights
46+
47+
| Decision Type | Authority Level |
48+
| ----------------------------------- | ------------------------------------------------------ |
49+
| Meeting logistics & scheduling | WG Leads (autonomous) |
50+
| Proposal prioritization within WG | WG Leads (autonomous) |
51+
| SEP triage & closure (in scope) | WG Leads (autonomous, with documented rationale) |
52+
| Technical design within scope | WG consensus |
53+
| Spec changes (additive) | WG consensus → Core Maintainer approval |
54+
| Spec changes (breaking/fundamental) | WG consensus → Core Maintainer approval + wider review |
55+
| Scope expansion | Core Maintainer approval required |
56+
| WG Member approval | WG Member sponsors |
57+
58+
## Membership
59+
60+
| Name | Organization | GitHub | Discord | Level | Maintainer? |
61+
| ------------------ | ------------ | ------------------------------------------------ | ---------- | --------- | ----------- |
62+
| Tadas Antanavicius | PulseMCP | [@tadasant](https://github.com/tadasant) | tadasant\_ | Lead | Yes |
63+
| Radoslav Dimitrov | Stacklok | [@rdimitrov](https://github.com/rdimitrov) | dimitrovr | Lead | Yes |
64+
| Bob Dickinson | TeamSpark | [@BobDickinson](https://github.com/BobDickinson) | rddthree | WG Member | Yes |
65+
| Preeti Dewani | Ravenmail | [@pree-dew](https://github.com/pree-dew) | pree_dew | WG Member | No |
66+
67+
## Emeritus Membership
68+
69+
| Name | Organization | GitHub | Discord | Level | Maintainer? |
70+
| ------------ | ------------ | ------------------------------------------ | --------- | --------- | ----------- |
71+
| Adam Jones | Anthropic | [@domdomegg](https://github.com/domdomegg) | domdomegg | WG Member | Yes |
72+
| Toby Padilla | GitHub | [@toby](https://github.com/toby) | | WG Member | Yes |
73+
74+
## Operations
75+
76+
| Meeting | Frequency | Duration | Purpose |
77+
| --------------- | --------- | -------- | ------------------------------------------------- |
78+
| Working Session | Weekly | 30 min | Technical discussion, triage, and proposal review |
79+
80+
Discord: `#registry-dev`
81+
82+
## Deliverables & Success Metrics
83+
84+
### Active Work Items
85+
86+
| Item | Status | Target Date | Champion |
87+
| --------------------------------------------------------------------- | ----------- | ----------- | ---------------------------------------- |
88+
| Server Card / `server.json` alignment | In Progress | Q2 2026 | [@tadasant](https://github.com/tadasant) |
89+
| Uptime & monitoring automation | Planned | Q2 2026 | TBD |
90+
| Issue triage automation & labeling system | Planned | Q2 2026 | TBD |
91+
| Adoption outreach to popular server maintainers | Ideating | Q3 2026 | TBD |
92+
| Cataloging specification support by clients and sub-registry products | Ideating | Q3 2026 | TBD |
93+
| Client SDK generation / publication | Ideating | Q3 2026 | TBD |
94+
| Registry API v1 GA | Ideating | TBD | TBD |
95+
96+
### Success Criteria
97+
98+
- Registry uptime ≥ 99.9% with automated monitoring and alerting.
99+
- `server.json` schema and Server Card format aligned with no unintentional divergence.
100+
- Majority of popular, publicly available MCP servers published to the registry.
101+
- At least one client SDK (generated or maintained) available for registry consumers.
102+
- Registry API v1 specification finalized and stable.
103+
- Active sub-registry ecosystem consuming the official registry API.
104+
105+
## Changelog
106+
107+
| Date | Change |
108+
| ---------- | --------------- |
109+
| 2026-04-08 | Initial charter |

‎docs/docs.json‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -495,6 +495,7 @@
495495
"community/file-uploads/charter",
496496
"community/inspector-v2/charter",
497497
"community/interceptors/charter",
498+
"community/registry/charter",
498499
"community/sdk/charter",
499500
"community/server-card/charter",
500501
"community/skills-over-mcp/charter",

0 commit comments

Comments
 (0)