Skip to content

Commit 4c99abf

Browse files
authored
Merge pull request modelcontextprotocol#2358 from modelcontextprotocol/den/sep-guidance
Add guidance to discuss SEPs with working groups before submission
2 parents 4462230 + 12d7bf7 commit 4c99abf

1 file changed

Lines changed: 10 additions & 1 deletion

File tree

docs/community/sep-guidelines.mdx

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ The SEP process is reserved for changes that are substantial enough to require b
3131
- Adding examples to existing features
3232
- Minor schema fixes that don't change behavior
3333

34-
Not sure? Ask in [Discord](https://discord.gg/6CSzBmMkjX) before starting significant work.
34+
Not sure? Ask in [Discord](/community/communication#discord) before starting significant work.
3535

3636
## SEP Types
3737

@@ -69,6 +69,15 @@ flowchart TD
6969

7070
### Step-by-Step Process
7171

72+
<Note>
73+
To improve your chances of a SEP being accepted:
74+
75+
- **Discuss your idea with the relevant [working or interest group](/community/working-interest-groups) in [Discord](/community/communication#discord) first.** This is the single best way to refine your proposal and build early support.
76+
- **If no relevant group exists, start a conversation in [GitHub Discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions) or the `#general` channel in [Discord](/community/communication#discord).** If there is enough interest, it may be worth [creating a new IG or WG](/community/working-interest-groups#creating-an-interest-group) — the effort involved in finding sponsors and facilitators is a good signal of whether the idea has sufficient traction, and is still preferable to a cold submission.
77+
- **Check alignment with [Core Maintainer](/community/governance#roles) priorities and [design principles](/community/design-principles).** Priorities are generally reflected in the [project roadmap](/development/roadmap). Proposals outside current priorities or that conflict with design principles are more likely to face delays or additional friction in the review process.
78+
79+
</Note>
80+
7281
1. **Draft your SEP** as a markdown file named `0000-your-feature-title.md`, using `0000` as a placeholder. Follow the [SEP format](#sep-format) below.
7382

7483
2. **Create a pull request** adding your SEP file to the `seps/` directory in the [specification repository](https://github.com/modelcontextprotocol/modelcontextprotocol).

0 commit comments

Comments
 (0)