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.
https://api.skillist.io/mcp — streamable HTTP with optional OAuth.
Transport
| Feature | Value |
|---|---|
| Protocol | MCP 2026-07-28 (stateless, per-request metadata) |
| Transport | Streamable HTTP — every message is its own POST |
| Sessions | None — each request is self-contained; Mcp-Session-Id is ignored |
| Required headers | MCP-Protocol-Version, Mcp-Method (and Mcp-Name on tools/call) |
| Legacy clients | 2025-era initialize handshakes are served statelessly from the same tools |
Every request carries its protocol version and client info in params._meta
(io.modelcontextprotocol/* keys), mirrored into the headers above. Clients on
older revisions that open with initialize keep working — the handshake is
answered per request, with no session state. server/discover reports supported
versions and capabilities.
Server info
Section titled “Server info”curl https://api.skillist.io/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 |
| my_projects | Projects you can access across orgs (session required) |
| project_skills | Curated items in a project (read access, session required) |
| add_skill_to_project | Add a skill/link to a project (write access, session required) |
The first four tools are public. my_projects, project_skills, and
add_skill_to_project require an authenticated MCP session — see
OAuth authentication.
See Tools reference for parameters and examples.
Public reads, scoped writes
Section titled “Public reads, scoped writes”The four registry_* tools are public, read-only registry access. The project
tools are gated by an authenticated MCP session and per-project access derived
from project visibility (private/shared) and membership: my_projects
returns only readable projects, project_skills needs read access (org owner, a
project member, or a shared project), and add_skill_to_project needs write
access (org owner, a project editor/admin, or an org editor+ on a shared
project). Publish, edit, and sandbox run still 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.io/{org}/{repo}paths returned by install help