modelcontextprotocol / modelcontextprotocol/ext-skills
Post-v1: query/filter on skills/list for large catalogs
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 655
- Forks
- 58
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 9
Description
We are building an MCP server that will contain a massive amount of skills. Exposing them all in a skill://index.json is not practical and will leads to context bloat and poor skill selection.
From our server end, we have a mechanism to surface relevant skills based on a query string / passed in context. Today, we can workaround and surface that mechanism through a "discover_skills" tool and returning a list of resource URIs. But relying on a tool being called to discover skills is unideal
Could there be a more idiomatic way to do this in the Skills over MCP extension spec? Perhaps a skills/discover? Or a resources/discover if we are going Skills are just Resources route
This is similar to the "query" parameter proposed for tools in SEP-1821. https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1821
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the Skills over MCP extension specification and the referenced SEP-1821 discussion. Compare the current skill://index.json and discover_skills approaches, then document a decided discovery mechanism and its expected query or context behavior as the completed outcome.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100