Skip to main content

Group Type

Working Group

Mission Statement

The Skills Over MCP Working Group defines how “agent skills” — rich, structured instructions for agent workflows — are discovered, distributed, and consumed through MCP. Native skills support in host applications demonstrates strong demand, and the group emerged from discussion on SEP-2076 — Agent Skills as a First-Class MCP Primitive, which raised open questions about whether existing MCP primitives suffice or what conventions to standardize. The WG produces specification extensions, reference implementations, and coordination artifacts because solutions touch the protocol spec, registry schema, SDK implementations, and client behavior.

Scope

In Scope

  • Specification Work: SEPs defining how skills are represented, discovered, and consumed within MCP — including the Skills Extension (Extensions Track) and related protocol changes
  • Reference Implementations: SDK components and reference servers demonstrating skill discovery and consumption patterns
  • Cross-Cutting Concerns: Coordination with Registry WG (skills discovery/distribution, registry schema changes), Agents WG (skill activation, server metadata consumption), Primitive Grouping WG (progressive disclosure patterns), and external projects including the Agent Skills spec (content format and well-known URI discovery), FastMCP, and PydanticAI
  • Documentation: Specification sections and guidance covering skill authoring, discovery, and consumption

Out of Scope

  • Registry schema decisions: Schema ownership belongs to the Registry WG; this WG contributes requirements but does not own the schema
  • Client implementation mandates: We can document patterns but not require specific client behavior
  • Plugin/bundle packaging: Installable bundles (skills + servers + subagents + configuration as a single artifact) — surfaced by use cases but belongs to a broader packaging effort
  • Agents WG — How agents consume server metadata, skill activation
  • Registry WG — Skills discovery/distribution, registry schema changes
  • Primitive Grouping WG — Progressive disclosure patterns

Leadership

RoleNameOrganizationGitHubTerm
LeadOla HungerfordNordstrom / MCP Maintainer@olaservoInitial
LeadPeter AlexanderAnthropic / Core Maintainer@pja-antInitial

Authority & Decision Rights

Decision TypeAuthority Level
Meeting logistics & schedulingWG Leads (autonomous)
Proposal prioritization within WGWG Leads (autonomous)
SEP triage & closure (in scope)WG Leads (autonomous, with documented rationale)
Technical design within scopeWG consensus
Spec changes (additive)WG consensus → Core Maintainer approval
Spec changes (breaking/fundamental)WG consensus → Core Maintainer approval + wider review
Scope expansionCore Maintainer approval required
WG Member approvalWG Member sponsors

Membership

NameOrganizationGitHubDiscordLevel
Ola HungerfordNordstrom / MCP Maintainer@olaservoLead
Peter AlexanderAnthropic / Core Maintainer@pja-antLead
Yu YiGoogle@erainParticipant
Sunish ShethDatabricks@sunishsheth2009Participant
Keith A GrovesHyix@keithagrovesParticipant
Peder Holdgaard PedersenSaxo Bank / MCP Maintainer@pederhpParticipant
Sam MorrowGitHub@SamMorrowDrumsParticipant
Jacob MacDonaldGoogle@jakemac53Participant
Jonathan HefnerIndependent / MCP Maintainer@jonathanhefnerParticipant
Luca ChangAWS / MCP Maintainer@LucaButBoringParticipant
Bob DickinsonTeamSpark.ai / MCP Maintainer@BobDickinsonParticipant
Radoslav DimitrovStacklok / MCP Maintainer@rdimitrovParticipant
Juan Antonio OsorioStacklok@JAORMXParticipant
Kaxil NaikAstronomer / Apache Airflow PMC@kaxilParticipant
Cliff HallFuturescale@cliffhallParticipant

Operations

MeetingFrequencyDurationPurpose
Working SessionWeekly (Tuesdays)60 minutesTechnical discussion, pattern evaluation, proposal review; open to all participants
Default start time is 9:00 AM Pacific. Sessions may occasionally be scheduled earlier to better accommodate non-US time zones. Meetings are published at meet.modelcontextprotocol.io. Agendas are posted in advance per MCP meeting policy. Meeting notes are published to Meeting Notes — Skills Over MCP WG. Discord: #skills-over-mcp-wg

Resources

Deliverables & Success Metrics

Active Work Items

Full live tracking is on the Skills Over MCP WG project board. Headline workstreams:
ItemStatusTarget DateChampion
Skills Extension SEP (draft, Extensions Track)In Review@pja-ant
Skills Extension reference implementationIn Review@olaservo
Agent Skills spec coordinationIn Progress@jonathanhefner, @pja-ant
Registry skills.json proposalIn Progress@JAORMX

Success Criteria

  • Short-term: Documented consensus on requirements and evaluation of existing approaches
  • Medium-term: Clear recommendation (convention vs. protocol extension vs. both) — the draft Skills Extension SEP represents the WG’s current direction: a formal extension using existing Resources primitives
  • Long-term: Interoperable skill distribution across MCP servers and clients

Changelog

DateChange
2026-04-16Converted from Interest Group to Working Group
2026-04-14Initial charter (formalized from experimental-ext-skills repo README, which served as the de facto charter before the charter process was established via SEP-2149)
2026-02-01IG formed; experimental repo created