Skip to content

Commit 6d954fe

Browse files
LucaButBoringLucaButBoring
authored
Merge branch 'main' into feat/ext-tasks
2 parents d963ad0 + 8bf5b7d commit 6d954fe

3 files changed

Lines changed: 92 additions & 1 deletion

File tree

‎docs/community/sdk/charter.mdx‎

Lines changed: 90 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,90 @@
1+
---
2+
title: SDK Working Group Charter
3+
description: Charter for the MCP SDK Working Group.
4+
---
5+
6+
## Group Type
7+
8+
**Working Group**
9+
10+
## Mission Statement
11+
12+
The SDK Working Group exists to keep the official MCP SDKs consistent, conformant, and current with the specification. It coordinates implementation of new protocol versions across languages, governs the [SDK Tiering System](/community/sdk-tiers), and establishes shared design patterns where sensible, so that developers get a coherent experience across SDKs while each remains idiomatic to its language.
13+
14+
## Scope
15+
16+
### In Scope
17+
18+
- **SDK Tiering**: Operating the [SDK Tiering System](/community/sdk-tiers), including reviewing tier advancement requests, applying relegation criteria, and maintaining the published tier assignments.
19+
- **Official SDK Roster**: Evaluating proposals to add new official SDKs or retire existing ones.
20+
- **Release Coordination**: Aligning Tier-1 SDK release plans with specification version dates so that protocol features land in SDKs on the timelines their tier requires.
21+
- **Cross-SDK Design Guidance**: Recommending common patterns for SDK API surface, versioning, deprecation, error handling, and extension packaging, so that SDKs remain recognisably similar across languages while staying idiomatic.
22+
- **Conformance Integration**: Working with the Conformance Testing project to ensure each official SDK runs the conformance suite and publishes results.
23+
- **Maintainer Coordination**: Providing a forum for per-language SDK maintainers to share implementation experience and surface specification ambiguities back to Core Maintainers.
24+
25+
### Out of Scope
26+
27+
- **Per-SDK day-to-day maintenance**: Issue triage, PR review, and releases for an individual SDK remain the responsibility of that SDK's maintainers as listed in [MAINTAINERS.md](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md).
28+
- **Specification authorship**: Protocol changes are proposed through the [SEP process](/community/sep-guidelines) and owned by the relevant working group or Core Maintainers. The SDK WG implements accepted SEPs; it does not own spec sections.
29+
- **Conformance test authoring**: The conformance test suite itself is owned by the [Conformance Testing](https://github.com/modelcontextprotocol/conformance) project.
30+
- **Third-party and community SDKs**: SDKs outside the [modelcontextprotocol](https://github.com/modelcontextprotocol) organization are not governed by this group.
31+
32+
### Related Groups
33+
34+
- **Transports WG**: Transport implementations are a substantial part of every SDK. The SDK WG coordinates with the Transports WG on rollout sequencing when transport SEPs land.
35+
- **Conformance Testing**: Tier assignments depend on conformance scores. The SDK WG consumes conformance results and feeds back gaps in test coverage.
36+
- **All specification-producing WGs**: The SDK WG is a downstream consumer of accepted SEPs and coordinates reference-implementation timing with the originating group.
37+
38+
## Leadership
39+
40+
| Role | Name | Organization | GitHub | Term |
41+
| ---- | ---------------- | ------------ | ------------------------------------------------------ | ------- |
42+
| Lead | Felix Weinberger | Anthropic | [@felixweinberger](https://github.com/felixweinberger) | Ongoing |
43+
44+
## Authority & Decision Rights
45+
46+
| Decision Type | Authority Level |
47+
| ---------------------------------------- | ---------------------------------------------- |
48+
| Meeting logistics & scheduling | WG Leads (autonomous) |
49+
| Proposal prioritization within WG | WG Leads (autonomous) |
50+
| SDK tier advancement or relegation | WG consensus |
51+
| Cross-SDK design guidance | WG consensus (advisory to per-SDK maintainers) |
52+
| Per-SDK releases, versioning, API design | That SDK's maintainers (autonomous) |
53+
| Adding or retiring an official SDK | WG consensus → Core Maintainer approval |
54+
| Changes to the tiering criteria | WG consensus → Core Maintainer approval |
55+
| Scope expansion | Core Maintainer approval required |
56+
| WG Member approval | WG Member sponsors |
57+
58+
## Membership
59+
60+
WG Members are the maintainers of each official SDK as recorded in [MAINTAINERS.md](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md) and the corresponding roles in [modelcontextprotocol/access](https://github.com/modelcontextprotocol/access). Maintainers of any official SDK are WG Members by default.
61+
62+
## Operations
63+
64+
| Meeting | Frequency | Duration | Purpose |
65+
| --------------- | --------- | -------- | ---------------------------------------------------- |
66+
| Working Session | Biweekly | 45 min | Release coordination, tier reviews, cross-SDK design |
67+
68+
Communication happens in the `#general-sdk-dev` Discord channel and the SDK Working Group category in [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions).
69+
70+
## Deliverables & Success Metrics
71+
72+
### Active Work Items
73+
74+
| Item | Status | Target Date | Champion |
75+
| --------------------------------------------------- | ----------- | ----------- | ------------------- |
76+
| 2026-06-30 spec support across Tier-1 SDKs | Planning | 2026 Q3 | Per-SDK maintainers |
77+
| Cross-SDK guidance for stateless transport adoption | In progress | 2026 Q2 | WG Leads |
78+
| Quarterly tier review | Recurring | Quarterly | WG Leads |
79+
80+
### Success Criteria
81+
82+
- All official SDKs have a published tier and a passing conformance run on their default branch.
83+
- Tier-1 SDKs ship support for each released specification version within the timeline their tier requires.
84+
- Tier advancement and relegation decisions are recorded with rationale in GitHub Discussions.
85+
86+
## Changelog
87+
88+
| Date | Change |
89+
| ---------- | --------------- |
90+
| 2026-04-28 | Initial charter |

‎docs/docs.json‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -471,6 +471,7 @@
471471
"community/file-uploads/charter",
472472
"community/inspector-v2/charter",
473473
"community/interceptors/charter",
474+
"community/sdk/charter",
474475
"community/server-card/charter",
475476
"community/skills-over-mcp/charter",
476477
"community/triggers-events/charter"

‎docs/registry/about.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ The MCP Registry provides:
1616
- A REST API for MCP clients and aggregators to discover available servers
1717
- Standardized installation and configuration information
1818

19-
Server metadata is stored in a standardized [`server.json` format](https://github.com/modelcontextprotocol/registry/blob/main/docs/reference/server-json/server.schema.json), which contains:
19+
Server metadata is stored in a standardized [`server.json` format](https://github.com/modelcontextprotocol/registry/blob/main/docs/reference/server-json/draft/server.schema.json), which contains:
2020

2121
- The server's unique name (e.g., `io.github.user/server-name`)
2222
- Where to locate the server (e.g., npm package name, remote server URL)

0 commit comments

Comments
 (0)