Skip to content

Commit 543ecea

Browse files
authored
Merge pull request modelcontextprotocol#1608 from olaservo/add-meeting-info
docs: Add Meeting Calendar information for Interest and Working Groups
2 parents e40f499 + a6bdbdd commit 543ecea

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

docs/community/working-interest-groups.mdx

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,12 @@ These groups exist to:
2222

2323
## Mechanisms
2424

25+
## Meeting Calendar
26+
27+
All Interest Group and Working Group meetings are published on the public MCP community calendar at [meet.modelcontextprotocol.io](https://meet.modelcontextprotocol.io/).
28+
29+
Facilitators are responsible for posting their meeting schedules to this calendar in advance to ensure discoverability and enable broader community participation.
30+
2531
### Interest Groups (IGs)
2632

2733
**Goal:** Facilitate discussion and knowledge-sharing among MCP contributors who share interests in a specific MCP sub-topic or context. The primary focus is on identifying and gathering problems that may be worth addressing through SEPs or other community artifacts, while encouraging open exploration of protocol issues and opportunities.
@@ -30,6 +36,8 @@ These groups exist to:
3036

3137
- Regular conversations in the Interest Group Discord channel
3238
- **AND/OR** a recurring live meeting regularly attended by Interest Group members
39+
- Meeting dates and times published in advance on the [MCP community calendar](https://meet.modelcontextprotocol.io/) when applicable, and tagged with their primary topic and interest group Discord channel name (e.g. `auth-ig`)
40+
- Notes publicly shared after meetings, as a GitHub issue ([example](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1629)) and/or public Google Doc
3341

3442
**Examples**:
3543

@@ -68,6 +76,8 @@ Participation in an Interest Group (IG) is not required to start a Working Group
6876

6977
- Meaningful progress towards at least one SEP or spec-related implementation **OR** hold maintenance responsibilities for a project (e.g., Inspector, Registry, SDKs)
7078
- Facilitators are responsible for keeping track of progress and communicating status when appropriate
79+
- Meeting dates and times published in advance on the [MCP community calendar](https://meet.modelcontextprotocol.io/) when applicable, and tagged with their primary topic and working group Discord channel name (e.g. `agents-wg`)
80+
- Notes publicly shared after meetings, as a GitHub issue ([example](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1629)) and/or public Google Doc
7181

7282
**Examples**:
7383

0 commit comments

Comments
 (0)