You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As required by the Code of Conduct, the description, docs, and comments (words meant for humans) are written by a human, not by an LLM.
Overview
Should we add support for the MCP Skills extension? The extension was accepted in SEP-2640. Clients should be able to browse skills on external MCP servers and fetch files through the gateway as they need them.
What I'd Like To See
Let clients discover Skills support, browse a server's catalog and look up a skill directly by URI.
Pass through the server's pagination and metadata so clients can browse without downloading everything and verify files as they fetch them.
Piggyback on existing MCP authentication until there's a use case for something more.
Let users browse skills and inspect their metadata and files in the MCP Playground, with requests visible to operators alongside other MCP traffic.
Scope
This would be a read-only passthrough with no aggregation. Each server keeps its own catalog and files, and agentgateway forwards requests to the server the client selects.
Related Work
In #3094 and #2254, maintainers suggested keeping registry work in other projects.
This project uses the Rust MCP SDK, which also has Skills support in progress. We may be able to reuse that work.
This seems reasonable to me. I don't think we have to limit to non-aggregation long term though ok with a short term approach of single server only support.
Activity
howardjohn commentedon Sep 21, 2026
This seems reasonable to me. I don't think we have to limit to non-aggregation long term though ok with a short term approach of single server only support.