--- title: SEPs Are Moving to Pull Requests | daily.dev description: Model Context Protocol's Specification Enhancement Proposals (SEPs) are moving from GitHub Issues to pull requests against the seps/ directory, effective... canonical: https://daily.dev/posts/seps-are-moving-to-pull-requests-gfatw9xlz twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: SEPs Are Moving to Pull Requests | daily.dev og:description: Model Context Protocol's Specification Enhancement Proposals (SEPs) are moving from GitHub Issues to pull requests against the seps/ directory, effective... og:url: https://daily.dev/posts/seps-are-moving-to-pull-requests-gfatw9xlz og:image: https://api.daily.dev/og/posts/GfatW9XlZ.png og:image:alt: SEPs Are Moving to Pull Requests og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # SEPs Are Moving to Pull Requests **[Model Context Protocol](https://daily.dev/sources/modelcontextprotocol-blog)** · 4 min read · 0 upvotes · 0 comments ## Summary Model Context Protocol's Specification Enhancement Proposals (SEPs) are moving from GitHub Issues to pull requests against the seps/ directory, effective immediately. The change addresses scattered discussions and lack of version history, drawing inspiration from Python's PEP process. Under the new workflow, contributors draft a markdown file, open a PR, rename the file using the PR number, find a maintainer sponsor, and iterate directly in the PR. Sponsors now own updating the SEP's Status field in the file itself, while PR labels remain for filtering. Existing issue-based SEPs can continue but migration to the new process is encouraged. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I submit a new SEP (Specification Enhancement Proposal) for the Model Context Protocol now? New SEPs must be submitted as pull requests to the seps/ directory instead of GitHub issues, effective November 28, 2025. Draft a markdown file named 0000-your-feature.md using the SEP template, open a PR, then rename the file using the PR number (e.g., PR #1850 becomes 1850-your-feature.md), find a maintainer sponsor, and iterate on feedback in the PR. _daily.dev helps contributors track evolving governance workflows like MCP's SEP process as they roll out._ ### What happens to SEPs that were already submitted as GitHub issues before the new process? Existing issue-based SEPs can continue under the old workflow, but migration to the new PR-based process is strongly encouraged for better version control and centralized discussion. To migrate, create a markdown file from the template, submit it as a PR to the seps/ directory, rename it using the new PR number, and close the original issue with a link to the new PR. _Following migration guides like this helps teams navigate process changes without losing contributor momentum._ ### Who is responsible for updating a SEP's status field under MCP's new PR-based proposal process? Sponsors are now responsible for updating the SEP status, both by applying labels to the pull request and by ensuring the Status field is updated within the SEP markdown file itself. This keeps the canonical proposal state versioned alongside the content, while PR labels support filtering. Transitions still follow Draft, In-Review, Accepted, then Final. _Developers navigating open-source governance changes can follow updates like this one on daily.dev._ ## Similar posts on daily.dev - [Welcome to the Eternal September of open source. Here’s what we plan to do for maintainers.](https://daily.dev/posts/welcome-to-the-eternal-september-of-open-source-here-s-what-we-plan-to-do-for-maintainers--gakiupiut) · GitHub Blog · 0 upvotes · 0 comments - [Open Source’s ‘Eternal September’, GitHub Keeps Maintainers Covered for All Seasons](https://daily.dev/posts/open-source-s-eternal-september-github-keeps-maintainers-covered-for-all-seasons-gitxcoui5) · DevOps.com · 0 upvotes · 0 comments - [Improved pull request “Files changed” – February 5 updates](https://daily.dev/posts/improved-pull-request-files-changed-february-5-updates-xx00git1g) · GitHub Changelog · 1 upvotes · 0 comments --- Tags: [#open-source](https://daily.dev/tags/open-source), [#github](https://daily.dev/tags/github), [#mcp](https://daily.dev/tags/mcp) [View this post on daily.dev](https://daily.dev/posts/seps-are-moving-to-pull-requests-gfatw9xlz) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"SEPs Are Moving to Pull Requests","url":"https://daily.dev/posts/seps-are-moving-to-pull-requests-gfatw9xlz","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/seps-are-moving-to-pull-requests-gfatw9xlz"},"datePublished":"2026-08-23T12:16:54.311Z","dateModified":"2026-08-23T12:17:56.766Z","description":"Model Context Protocol's Specification Enhancement Proposals (SEPs) are moving from GitHub Issues to pull requests against the seps/ directory, effective...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ccad778d24e1fca3aa1c66575a7bfbf3?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ccad778d24e1fca3aa1c66575a7bfbf3?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Model Context Protocol","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Model Context Protocol","logo":"https://media.daily.dev/image/upload/s--ORAgfri4--/f_auto,q_auto/v1787487408/logos/modelcontextprotocol-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/modelcontextprotocol-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/seps-are-moving-to-pull-requests-gfatw9xlz","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"open-source,github,mcp","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Model Context Protocol","item":"https://daily.dev/sources/modelcontextprotocol-blog"},{"@type":"ListItem","position":3,"name":"SEPs Are Moving to Pull Requests"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/seps-are-moving-to-pull-requests-gfatw9xlz#faq","mainEntity":[{"@type":"Question","name":"How do I submit a new SEP (Specification Enhancement Proposal) for the Model Context Protocol now?","acceptedAnswer":{"@type":"Answer","text":"New SEPs must be submitted as pull requests to the seps/ directory instead of GitHub issues, effective November 28, 2025. Draft a markdown file named 0000-your-feature.md using the SEP template, open a PR, then rename the file using the PR number (e.g., PR #1850 becomes 1850-your-feature.md), find a maintainer sponsor, and iterate on feedback in the PR. daily.dev helps contributors track evolving governance workflows like MCP's SEP process as they roll out."}},{"@type":"Question","name":"What happens to SEPs that were already submitted as GitHub issues before the new process?","acceptedAnswer":{"@type":"Answer","text":"Existing issue-based SEPs can continue under the old workflow, but migration to the new PR-based process is strongly encouraged for better version control and centralized discussion. To migrate, create a markdown file from the template, submit it as a PR to the seps/ directory, rename it using the new PR number, and close the original issue with a link to the new PR. Following migration guides like this helps teams navigate process changes without losing contributor momentum."}},{"@type":"Question","name":"Who is responsible for updating a SEP's status field under MCP's new PR-based proposal process?","acceptedAnswer":{"@type":"Answer","text":"Sponsors are now responsible for updating the SEP status, both by applying labels to the pull request and by ensuring the Status field is updated within the SEP markdown file itself. This keeps the canonical proposal state versioned alongside the content, while PR labels support filtering. Transitions still follow Draft, In-Review, Accepted, then Final. Developers navigating open-source governance changes can follow updates like this one on daily.dev."}}]} ```