MCP tools reference

All tools are invoked via JSON-RPC tools/call. Under MCP 2026-07-28 each request carries an _meta envelope and mirrors method/name into the Mcp-Method and Mcp-Name headers — see Connect your agent for a complete request:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "<tool_name>",
    "arguments": { },
    "_meta": { "io.modelcontextprotocol/protocolVersion": "2026-07-28" }
  }
}

The tools/list result carries the 2026-07-28 cache fields (ttlMs: 300000, cacheScope: "public") — the tool set is static and identical for every caller, authenticated or not.

registry_search

Search the public registry by name, description, tags, category, or agent compatibility.

Field	Type	Description
query	string	Search term (optional)
limit	number	Max results, default 10, max 20
category	string	Filter by category
tag	string	Filter by tag
agent	string	cursor, claude, vscode, or mcp
sort	string	relevance, quality, impact, trending, stars, installs, activations, recent, name

Example

{
  "name": "registry_search",
  "arguments": {
    "query": "performance",
    "limit": 5,
    "sort": "quality"
  }
}

registry_get_skill

Full metadata for a skill including eval uplift, install command, and manifest.

Field	Type	Required
org	string	yes — organization slug, e.g. skillist
repo	string	yes — skill repo name

The server also accepts legacy slug as an alias for repo.

Example

{
  "name": "registry_get_skill",
  "arguments": {
    "org": "skillist",
    "repo": "registry-mcp"
  }
}

registry_facets

List available filter facets: categories, tags, and compatible agents. No parameters.

{
  "name": "registry_facets",
  "arguments": {}
}

registry_install_help

Returns CLI install commands, SKILL.md URL, and skill page URL for a skill.

Field	Type	Required
org	string	yes
repo	string	yes

Example response fields

• cliInstall — global CLI setup (npm install -g @skillist/cli)
• installCommand — skillist install org/repo
• runCommand — sandbox run hint when applicable
• skillMdUrl — https://skillist.io/{org}/{repo}/SKILL.md
• registryUrl — https://skillist.io/{org}/{repo}

Authenticated project tools

The following tools require an authenticated MCP session (Better Auth OAuth token on the Authorization: Bearer header). Calling them without a session returns a tool result with isError: true whose text explains how to authenticate; the transport also sets the WWW-Authenticate header pointing at the OAuth resource metadata. The four registry tools above remain public.

my_projects

List the projects the authenticated user can access across every organization they belong to. No parameters. Returns only readable projects: every project in orgs the user owns, plus shared projects and projects the user is a member of in their other orgs. Each entry: orgId, orgSlug, projectId, slug, name, description, visibility, itemCount.

{
  "name": "my_projects",
  "arguments": {}
}

project_skills

List the curated items in a project, grouped by folder path and resolved for agent use. Requires read access to the project: org owner, a member of the project, or a project marked shared. Callers without access get a “Not found or no access” tool error.

Field	Type	Description
projectId	string	Project id (preferred)
orgSlug	string	Organization slug (use with projectSlug)
projectSlug	string	Project slug (use with orgSlug)

Skill items return {org}/{repo}, visibility, and install/run commands; external items return externalUrl and externalName.

add_skill_to_project

Add a skill or external reference to a project. Requires write access to the project: org owner, a project editor/admin, or an org editor (or higher) when the project is marked shared. Provide exactly one of skillId or externalUrl. Duplicates return the existing item id with duplicate: true.

Field	Type	Required
projectId	string	yes
skillId	string	one of skillId / externalUrl
externalUrl	string	one of skillId / externalUrl
externalName	string	optional display name for external items
path	string	optional folder path

Agent workflow

1. registry_facets — when the user needs browse filters
2. registry_search — find candidates
3. registry_get_skill — inspect eval scores and metadata
4. registry_install_help — return install commands and delivery URLs to the user

Prefer skills with higher eval uplift and quality scores when multiple matches exist.