Registry MCP
The Skillist Registry MCP server lets agents search, browse, and install skills without leaving the chat. It runs on the same API worker as the REST registry.
Endpoint
https://api.skillist.dev/mcp — streamable HTTP with optional OAuth.
Transport
| Feature | Value |
|---|---|
| Protocol | MCP 2024-11-05 |
| Transport | Streamable HTTP |
| Stateless JSON | POST with Accept: application/json |
| SSE sessions | POST/GET with Accept: text/event-stream and Mcp-Session-Id |
| Session teardown | DELETE with Mcp-Session-Id |
initialize returns an Mcp-Session-Id header for stateful clients. Plain JSON-RPC POST remains supported for simple clients.
Server info
Section titled “Server info”curl https://api.skillist.dev/mcpReturns transport metadata, tool names, and OAuth discovery URLs.
Tools
| Tool | Purpose |
|---|---|
| registry_search | Search by query, category, tag, agent, sort |
| registry_get_skill | Full metadata for org/repo including eval uplift |
| registry_facets | Categories, tags, and compatible agents |
| registry_install_help | CLI install commands and SKILL.md URL |
See Tools reference for parameters and examples.
Read-only by design
Section titled “Read-only by design”Registry MCP is read-only. Publish, edit, and sandbox run require the CLI with an authenticated API key.
Next steps
Section titled “Next steps”- Connect your agent — Cursor, Claude, VS Code
- OAuth authentication — sign in from OAuth-capable MCP clients
- Delivery URLs — apex
skillist.dev/{org}/{repo}paths returned by install help