← September 2026
News 2026-09-18

MCP Protocol News - September 18, 2026

The Model Context Protocol ecosystem this week was dominated by the Skills extension: the specification repository merged SEP-2640, then added support tracking, backward-compatibility requirements…

MCP Protocol News - September 18, 2026

MCP Protocol News - September 18, 2026

Week of: September 18, 2026


Overview

The Model Context Protocol ecosystem this week was dominated by the Skills extension: the specification repository merged SEP-2640, then added support tracking, backward-compatibility requirements, and revised links as the extension moved into a published state, alongside naming Sambhav Kothari as working group lead. On the tooling side, the GitHub MCP Server shipped v1.12.2 with new issue-comment and reaction-management tools.

Stories

1. SEP-2640 Skills Extension merged into the MCP specification

Source: MCP Specification Link: https://github.com/modelcontextprotocol/modelcontextprotocol/commit/1eb5bbe8ac933bdb595fedc687b8ed545e440491

The MCP specification repository merged pull request #2640, "SEP-2640: Skills Extension," landing the Skills extension in the spec codebase.

This is the foundational ecosystem move of the week: an extension that defines how skills are represented over MCP gives builders a standardized target for packaging agent capabilities rather than bespoke conventions. Teams designing agent tooling should track the extension's wording and capability requirements as they stabilize.

Impact Analysis: The Skills extension now has a landed specification change, making it the reference point for skill packaging in MCP-based agents.

2. Skills extension overview and support tracking added to docs

Source: MCP Specification Link: https://github.com/modelcontextprotocol/modelcontextprotocol/commit/2997f33bf6e4aab3db48d755fc877c8feab32c71

Pull request #3353 was merged, adding a Skills extension overview and support tracking to the MCP documentation.

Support tracking is the practical signal for builders deciding when to invest in the extension, since it indicates which implementations are expected to back it. An explicit overview also lowers the cost of understanding the extension's scope.

Impact Analysis: Documented support tracking gives developers a concrete way to gauge implementation readiness for Skills.

3. Sambhav Kothari named Skills Over MCP working group lead

Source: MCP Specification Link: https://github.com/modelcontextprotocol/modelcontextprotocol/commit/f9c73a3ad892a36672754293bbfd8570928a526d

A docs commit added Sambhav Kothari as the Skills Over MCP working group lead (merged via PR #3360).

Formalizing working group leadership signals that Skills work is moving from proposal to sustained maintenance, which matters for anyone depending on the extension's direction. It also gives the ecosystem a clear point of coordination for follow-on changes.

Impact Analysis: Clear working group ownership suggests the Skills extension will see continued, coordinated iteration rather than one-off landings.

4. Skills SEP links repaired after ext-skills archive move

Source: MCP Specification Link: https://github.com/modelcontextprotocol/modelcontextprotocol/commit/f56f204f6290f6531b14d5734eb3e0a10f0eb201

Commit f56f204, tagged as PR #3366, repaired Skills SEP links following the move of the ext-skills archive.

Broken proposal links are a small but real friction point for builders trying to trace the rationale behind the extension's design decisions. The fix keeps the specification's reference trail usable as the repository reorganizes around the extension.

Impact Analysis: Reference links for the Skills proposal remain traceable after the repository restructuring.

5. Docs updated to reflect published Skills extension status and track work in extension issues

Source: MCP Specification Link: https://github.com/modelcontextprotocol/modelcontextprotocol/commit/24efd6e7cbd7a074e6b3b781eb370891df40afad

A merge of PR #3372 folded in documentation changes reflecting the published Skills extension status, alongside related commits that track Skills work in extension issues.

Marking the extension as published is the milestone that tells implementers the specification is a stable integration target rather than a draft. Routing ongoing work into extension issues also establishes where future changes will be discussed.

Impact Analysis: The Skills extension is now documented as published, shifting it from proposal tracking to implementation support.

6. GitHub MCP Server 1.12.2 adds issue comment and reaction management tools

Source: GitHub MCP Server Link: https://github.com/github/github-mcp-server/releases/tag/v1.12.2

GitHub MCP Server released v1.12.2, adding an update_issue_comment tool and adding remove_issue_reaction, remove_issue_comment_reaction, and remove_pull_request_review_comment_reaction tools to the granular issues and pull requests toolsets.

The additions round out write-side coverage for GitHub workflows exposed over MCP, letting agents edit and clean up comments and reactions rather than only creating them. For builders automating triage or moderation flows, that reduces the need to fall back on direct API calls.

Impact Analysis: More complete write tooling in the GitHub MCP Server makes comment and reaction lifecycle management feasible for MCP-driven agents.

Source Links

More from News