SEP Updates #2
Merged
LucaButBoring merged 37 commits intoLucaButBoring:feat/tasks-stabilizationfrom Apr 18, 2026
Merged
Conversation
Guides SEP authors through interview → research → gate → draft → PR.
Checks existing spec coverage via mcp-docs, prior art via
/search-mcp-github, overlapping SEPs, and design-principle fit before
filling the eight-section TEMPLATE.md. Writes seps/SEP-DRAFT-{slug}.md
and offers (with checkpoint) to open a draft PR that backfills the
SEP number.
:house: Remote-Dev: homespace
SEP-2133 (Final) established Extensions Track for extension SEPs, and SEP-1865 already uses it. TEMPLATE.md and sep-guidelines.mdx still list only three types — the skill now notes that discrepancy inline so the agent doesn't get confused when reading the template. :house: Remote-Dev: homespace
🏠 Remote-Dev: homespace
Co-authored-by: David Soria Parra <167242713+dsp-ant@users.noreply.github.com>
- Use 0000-{slug}.md placeholder per sep-guidelines.mdx line 81 (was SEP-DRAFT-)
- Phase 6: add npm run generate:seps + git add docs/seps/ so render-seps.yml CI passes
- Q5: sponsor grants draft status (was inverted); add 6-month dormant window
- Q3: distinguish prototype-for-acceptance vs ref-impl-for-Final (two gates)
- Q1: add Extensions Track follow-up (Working Group + Extension Maintainers per SEP-2133)
- Q6: new security implications question (required TEMPLATE.md section)
- Phase 4: enumerate required vs optional sections; preamble notes for Status/Sponsor/PR fields
- Phase 6: use sponsor username in --reviewer; acknowledge SEP-1850 amend convention
- Specification Enhancement Proposal (canonical term)
:house: Remote-Dev: homespace
BLOCKER (introduced in 5a5e20f, now fixed): - Removed false claim that render-seps.ts skips ^0000- files. The skip on line 50 is dead code (outer ^(\d+)- regex matches 0000- first), so check:seps fails on the first push. Switched Phase 6 to the SEP-1850 amend flow so CI only sees the final renamed state. MAJOR: - Phase 2 step 4: added roadmap alignment check alongside design principles (sep-guidelines.mdx line 77) - Phase 3 Gate: replaced 'err toward proceeding' with the guidelines' actual advice to ask in Discord when unsure (sep-guidelines.mdx line 34) - Q5: now captures Author name/email/username for the Author(s) preamble field MINOR: - Dormant transition: 'Core Maintainers may close' (discretionary per SEP-1850) - Optional sections: added Acknowledgments - Preamble notes: added Created (YYYY-MM-DD) and Author(s) fields - Q5: noted gh pr create --reviewer expects bare handle without @ - Intro: added dissenting-opinions author duty (sep-guidelines.mdx line 10) - Phase 3: 'bug fix or typo correction' to match source bullet :house: Remote-Dev: homespace
All three findings were in explanatory prose, not commands or output: - Preamble notes: added Type field (was the only one of 6 unmentioned). Carries forward Q1's Extensions Track warning to write-time. - Phase 6 trailer: removed false CI rationale. CI does run on the 0000- push (pull_request trigger fires on gh pr create, before the amend). The actual reason for the amend per SEP-1850 is clean single-commit history, not CI evasion. Said that instead. - Phase 6 closing: replaced 'not yet ready for sponsor review' with 'next step is finding a sponsor'. The original framing told authors to wait when sep-guidelines.mdx steps 4-6 say sponsor outreach is the immediate next action. The 6-month clock starts at PR open. :house: Remote-Dev: homespace
🏠 Remote-Dev: homespace
Final swarm (6 assessors, 3-vote adversarial verification) passed SHIP with 2 minor polish items, now addressed: - Line 127: removed 'so CI only ever sees the final state'. Round 3 fixed line 149's rationale but left this earlier sentence attributing a CI motivation to SEP-1850. SEP-1850 line 45 says only 'amend the commit to rename the file' — nothing about CI. Post-modelcontextprotocol#2543, CI passes on the 0000- push anyway. - Lines 15, 27: 'Working Group' → 'Working Group or Interest Group' for prior-discussion venues. sep-guidelines.mdx accepts both. Line 24 (Extensions Track ownership) unchanged — SEP-2133 specifically says Working Group there. :house: Remote-Dev: homespace
…gitarald/update-vscode-client docs: update VS Code client entry with current MCP capabilities
…#2568) * docs(community): add Skills Over MCP IG charter (SEP-2149) Add the Skills Over MCP Interest Group charter per SEP-2149 requirements. All existing WGs and IGs must publish a conforming charter by ~May 18, 2026. - New file: docs/community/skills-over-mcp/charter.mdx - Updated docs/docs.json with new "Interest Group Charters" nav group This is the first Interest Group charter submitted. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix: apply prettier formatting to charter Align table columns to match prettier output; no semantic changes. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* Convert proposal from Google Doc to markdown doc in seps folder * Fix markdownlint and cspell issues * Add literal examples * Add rationale for location of custom header metadata * Define value encoding rules * Add section on Edge Cases & Conformance Tests * Clarify requirement on clients to support custom headers * Define JSON RPC error code for header mismatch errors * Add clear error handling for missing custom headers * Added tradeoffs on passing metadata in headers vs path * Added section on options for header number/size limits * Address PR review comments * Apply suggestion from @mikekistler * Collapse Mcp-Tool-Name, Mcp-Resource, Mcp-Prompt-Name into Mcp-Name * Specify Base64 encoding is of UTF-8 representation * Add rationale for encoding approach with alternatives evaluation * Drop caching as advantage of path-based routing * Clarify client behavior for setting standard and custom headers * Allow intermediaries to reject invalid requests without JSON-RPC error response * Add security guidance for trusting header values * Add rationale for scoping x-mcp-header to tools only * Remove limit on header value size * Rename sep file to match PR number * Fix render-seps check * Fix format check * First draft of spec updates for SEP modelcontextprotocol#2243 * Add changelog entry for SEP 2243 * Clarify that Mcp-Method header is required for notifications and add notification example * Address PR review comments. Co-authored-by: Mike Kistler <mikekistler@microsoft.com> * Apply suggestion from @mikekistler * Fix Render SEPs and Prettier PR checks
…tocol#2581) PR modelcontextprotocol#2364 moved `docs/community/seps/` to `docs/seps/`, but the corresponding patterns in `.gitattributes` were not updated to match. Fix the paths so GitHub continues to collapse these generated files in diffs. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…textprotocol#2243 (modelcontextprotocol#2584) The Note under "Tool Names" explaining that uniqueness is per-server, that aggregating clients SHOULD prefix to disambiguate, and that serverInfo.name is not a reliable disambiguation key, was accidentally overwritten when modelcontextprotocol#2243 inserted the x-mcp-header section. This restores the Note verbatim from 828bd47 in its original position. :house: Remote-Dev: homespace
…lients (modelcontextprotocol#2576) * docs(clients): expand mcpc entry with comprehensive feature coverage Update the mcpc client listing to reflect its full capabilities including async tasks, DCR, OAuth 2.1 with PKCE, cross-session discovery, MCP proxy sandboxing, interactive shell, schema validation, and x402 payments. https://claude.ai/code/session_01Y6Ksa3V6XWtwLXDFVGn3Cz * docs(clients): reframe mcpc entry around code-mode-in-the-shell thesis Adjust mcpc description based on Jan Curn's MCP Dev Summit NYC talk. Lead with the core value proposition: agents only need Bash() to access MCP, progressive tool discovery avoids context bloat, and shell scripts are more token-efficient than naive tool calling. Reorder features to highlight code mode and discovery first, add "no LLM required" detail. https://claude.ai/code/session_01Y6Ksa3V6XWtwLXDFVGn3Cz * docs(clients): sharpen mcpc entry with CLI-vs-MCP complementarity angle Reframe opening around the "MCP haters are only half right" thesis: CLI and MCP are complementary, not competing. Call out the naive MCP anti-pattern (dumping tools into context), highlight self-documenting --help discovery, and clarify the division of concerns (MCP for remote, shell for local). Add "production-ready" to the lightweight bullet. https://claude.ai/code/session_01Y6Ksa3V6XWtwLXDFVGn3Cz * docs(clients): tone down mcpc opening to match file conventions Replace editorial/marketing language with factual description matching the style of other entries. Lead with what mcpc does (maps MCP to CLI commands, single Bash() call) rather than making arguments about the ecosystem. Soften bullet claims to be descriptive rather than comparative. https://claude.ai/code/session_01Y6Ksa3V6XWtwLXDFVGn3Cz * docs(clients): note mcpc as most spec-compatible MCP CLI client https://claude.ai/code/session_01Y6Ksa3V6XWtwLXDFVGn3Cz * Better copy * Added info about CIMD support to mcpc * Better copy --------- Co-authored-by: Claude <noreply@anthropic.com>
…ntextprotocol#2586) * docs(community): convert Skills Over MCP from Interest Group to Working Group Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * style: run prettier on charter and docs.json Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add .mintlify/skills/ directory with a symlink to the search-mcp-github skill so Mintlify auto-serves it at /.well-known/agent-skills/index.json, making it discoverable by any agent that implements the agentskills.io spec. Also add license: Apache-2.0 to the skill frontmatter. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Move SEP-worthiness gate to Phase 1 so trivial requests are redirected before the six-question interview and research run - Add repo-clone prerequisite check (seps/TEMPLATE.md must exist) - Phase 3.1: hedge mcp-docs server with '(if available)' + grep fallback - Phase 6: branch from origin/main explicitly, note branch-reuse and fork paths, add 'npm run format:docs' before amend, narrow the SEP-1850 attribution to the rename/amend step only - README: reorder description to match new phase order, add prerequisite :house: Remote-Dev: homespace
- Phase 4: replace 12-name Required/Optional enumeration with a structural pointer to TEMPLATE.md's '---' rule (last residual of the 'read from TEMPLATE.md, don't repeat' review note) - Phase 4 PR bullet: state-agnostic wording; fix the stale repo URL in seps/TEMPLATE.md itself rather than documenting around it - Prerequisite: add 'git fetch origin' so research phases see current SEPs/schema/MAINTAINERS.md - Phase 6 closing: condition 'find a sponsor' on Q5 == None - README: mention format:docs alongside generate:seps :house: Remote-Dev: homespace
🏠 Remote-Dev: homespace
Previously read as ambiguous between a single Core Maintainer approval and a Core Maintainer vote. Charter PR approval requires only a single Core Maintainer, who should notify all Core Maintainers.
…l/davidsp/sep2149-clarify-core-maintainer-approval SEP-2149: clarify single Core Maintainer approval for WG charter
Most SEP authors are not maintainers and work from a fork, per
CONTRIBUTING.md. The skill previously assumed origin pointed at the
canonical repo and only mentioned forking as a Phase 6 fallback that
never fired for fork users (they can push to their own origin).
- Prerequisite: detect remote topology up front. If origin is a fork,
ensure an upstream remote exists and use that as {canonical}. Tell
users without a clone to 'gh repo fork --clone' rather than clone
upstream directly.
- Phase 6: branch from {canonical}/main (not origin/main, which may be
a stale fork main); keep origin as the push target. Pass --repo and
--base to gh pr create so it targets upstream regardless of
gh-resolved state, with 'gh repo set-default' as the recovery.
- README: '(or your fork of it)' in the prerequisite line.
:house: Remote-Dev: homespace
…l/feature/add-official-mcp-skills-to-well-known-list
…l/den/draft-sep-skill (chore): Add /draft-sep skill to simplify how SEPs are written
…skill (modelcontextprotocol#2597) The file-level symlink from modelcontextprotocol#2589 (SKILL.md -> SKILL.md) wasn't picked up by Mintlify's .well-known/agent-skills/ auto-scan — the live index only listed the auto-generated `mcp` skill. Replace it with a per-skill directory symlink so the search-mcp-github folder is exposed as a whole, matching the subdirectory layout Mintlify serves (/agent-skills/<name>/skill.md).
LucaButBoring
merged commit e6c43ed
into
LucaButBoring:feat/tasks-stabilization
5 of 6 checks passed
9 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change title to de-emphasize stabilization, we may still choose to leave this in experimental.
Update SEP Motivation and structure to highlight changes are for 2 reasons, new SEPs & Feedback
Added a section to say this does not move Tasks out of Experimental
Updated Cancellation behavior, this should not return an error can just silently be ignored to implement co-operative cancellation pattern.
Merged in upstream modelcontextprotocol hence so many changes. The only ones I actually made are to the SEP itself. seps/2557-adapt-tasks-for-stateless-and-sessionless-protocol.md