Skip to main content

Group Type

Interest Group

Mission Statement

The Skills Over MCP Interest Group explores how “agent skills” — rich, structured instructions for agent workflows — can be discovered and consumed through MCP. Native skills support in host applications demonstrates strong demand, and the IG 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. Cross-cutting collaboration is needed because solutions touch the protocol spec, registry schema, SDK implementations, and client behavior.

Scope

In Scope

  • Requirements gathering: Documenting use cases, constraints, and gaps in current MCP primitives for skill distribution
  • Pattern exploration: Testing and evaluating approaches (skills as tools, resources, registry metadata, protocol primitives) and discovery mechanisms (runtime via MCP, domain-level via well-known URIs, ecosystem-level via registry)
  • Coordination: Bridging discussions across Registry WG, Agents WG, and external projects including the Agent Skills spec (content format and well-known URI discovery), FastMCP, and PydanticAI
  • Proof of concepts: Maintaining a shared repo of reference implementations and experimental findings

Out of Scope

  • Approving spec changes: This IG does not have authority to approve protocol changes; recommendations flow through the SEP process
  • Registry schema decisions: Schema ownership belongs to the Registry WG; this IG 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

Membership

NameOrganizationGitHubLevel
Ola HungerfordNordstrom / MCP Maintainer@olaservoFacilitator
Peter AlexanderAnthropic / Core Maintainer@pja-antFacilitator
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
Office HoursWeekly (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 IG. Discord: #skills-over-mcp-ig

Resources

Deliverables & Success Metrics

Active Work Items

Full live tracking is on the Skills Over MCP IG project board. Headline workstreams:
ItemStatusChampion
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 IG’s current direction: a formal extension using existing Resources primitives
  • Long-term: Interoperable skill distribution across MCP servers and clients

Changelog

DateChange
2026-04-14Initial charter