> ## Documentation Index
> Fetch the complete documentation index at: https://modelcontextprotocol.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Group Charter Template

> The charter template for MCP working groups and interest groups, and how to submit a charter.

This page gives the charter template that every working group and interest group must follow and explains how to submit a charter. The template was adopted by [SEP-2149](https://modelcontextprotocol.io/seps/2149.md), a Specification Enhancement Proposal (SEP), and is changed, together with the rules in [Working Groups and Interest Groups](https://modelcontextprotocol.io/community/working-interest-groups.md), by a Process SEP. Each charter lives at `docs/community/working-groups/<name>.mdx` or `docs/community/interest-groups/<name>.mdx` in the [modelcontextprotocol repository](https://github.com/modelcontextprotocol/modelcontextprotocol), records only the group's mission, scope, leadership, membership and operations, and does not restate those rules, which apply to every group. Sections marked **(WG only)** are required for working groups and optional for interest groups. To start a group, see [Forming a group](https://modelcontextprotocol.io/community/working-interest-groups.md#forming-a-group).

## Submitting a charter

* The group must already be sponsored under [Forming a group](https://modelcontextprotocol.io/community/working-interest-groups.md#forming-a-group).
* Copy the template below into the charter file and replace the placeholders. Delete the `{/* */}` guidance comments or leave them as written: HTML comments break the MDX build, and `npm run format` corrupts a `{/* */}` comment that spans lines.
* Run `npm run prep`, then push.
* Open a pull request that adds the charter file, a navigation entry under Working Groups or Interest Groups in `docs/docs.json`, and a line under [Current groups](https://modelcontextprotocol.io/community/working-interest-groups.md#current-groups).
* A Core Maintainer will review the pull request, as outlined in the [Amending or retiring a group](https://modelcontextprotocol.io/community/working-interest-groups.md#amending-or-retiring-a-group) requirements.
* Later changes follow [Amending or retiring a group](https://modelcontextprotocol.io/community/working-interest-groups.md#amending-or-retiring-a-group) and add a row to the charter's Changelog.

> [!NOTE]
>
> [Transports](https://modelcontextprotocol.io/community/working-groups/transports.md) and
> [Security](https://modelcontextprotocol.io/community/interest-groups/security.md) are filled-in examples, for a
> working group and an interest group respectively.

## Template

```mdx theme={null}
---
title: <Group Name> Charter
description: Charter for the MCP <Group Name> <Working Group | Interest Group>.
---

## Group Type

{/* Keep one, delete the other. */}

**Working Group** | **Interest Group**

## Mission Statement

{/* Two or three sentences: the problem space, why it needs collaboration across groups, and the deliverables the WG will produce or the discussions the IG will host. */}
{/* Example opening: "The <Group Name> Working Group exists to <deliverable> so that <outcome>." */}

## Scope

### In Scope

{/* WG: Specification Work (spec sections or SEPs the group owns), Reference Implementations (SDK components or reference implementations), Cross-Cutting Concerns (areas needing coordination with other groups), and Documentation responsibilities. */}
{/* IG: topic areas for discussion, and the kinds of output (problem statements, use cases, recommendations). */}

### Out of Scope

{/* Explicit statements of what is not within the group's purview, to prevent mission creep. */}

### Related Groups

{/* Other WGs or IGs with intersecting work and the nature of the overlap. */}

## Leadership

{/* List current Leads (WG) or Facilitators (IG). Requirements and duties are defined at /community/working-interest-groups#leadership. */}

| Role | Name | Organization | GitHub | Term |
| ---- | ---- | ------------ | ------ | ---- |
|      |      |              |        |      |

## Authority & Decision Rights (WG only)

{/* The progression from lazy consensus to vote to escalation is defined at /community/working-interest-groups#making-decisions, not here. */}
{/* The rows below record the level at which this WG takes each kind of decision. They are the usual allocation and are approved with the charter. A change to any row follows /community/working-interest-groups#amending-or-retiring-a-group and gets a Changelog row. */}
{/* IGs do not make binding decisions and omit this section. */}

| Decision Type                       | Authority Level                                        |
| ----------------------------------- | ------------------------------------------------------ |
| Meeting logistics & scheduling      | WG Leads (autonomous)                                  |
| Proposal prioritization within WG   | WG Leads (autonomous)                                  |
| SEP triage & closure (in scope)     | WG Leads (autonomous, with documented rationale)       |
| Technical design within scope       | WG consensus                                           |
| Spec changes (additive)             | WG consensus → Core Maintainer approval                |
| Spec changes (breaking/fundamental) | WG consensus → Core Maintainer approval + wider review |
| Scope expansion                     | Core Maintainer approval required                      |
| WG Member approval                  | WG Member sponsors                                     |

## Membership

{/* List current members and their participation level. Omit this section until the group has members. */}
{/* Participation tiers and membership criteria are defined at /community/working-interest-groups#participation-levels. */}

| Name | Organization | GitHub | Discord | Level |
| ---- | ------------ | ------ | ------- | ----- |
|      |              |        |         |       |

## Operations

{/* List the group's regular meetings. Meeting and channel rules are defined at /community/working-interest-groups#meetings-and-channels. */}
{/* External repositories, proposal documents or meeting notes may be listed below the table. */}

| Meeting         | Frequency | Duration | Purpose                               |
| --------------- | --------- | -------- | ------------------------------------- |
| Working Session |           |          | Technical discussion, proposal review |
| Office Hours    |           |          | Open Q&A for newcomers and observers  |

## Deliverables & Success Metrics (WG only)

{/* IGs may list current discussion topics or planned outputs here instead. */}

### Active Work Items

| Item           | Status                       | Target Date | Champion |
| -------------- | ---------------------------- | ----------- | -------- |
| SEP-XXXX: Name | draft / in-review / accepted |             |          |

### Success Criteria

{/* State measurable outcomes. */}

## Changelog

| Date | Change |
| ---- | ------ |
|      |        |
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.