Docs / MCP

The Skyboy MCP server

Expose the whole skyboy.in catalog as callable tools so any MCP-compatible agent can search, preview, bundle, and install skills without leaving the conversation. One server implementation, two transports, picked by flag: stdio for desktop agents, http for the web app and remote agents.

Tools it exposes

search_catalog(query, category?)

Fuzzy search the catalog, ranked

get_skill(slug)

Full SKILL.md + skill.json metadata in one call

get_plugin(slug)

Nested skills, hooks, and agents manifest

list_categories()

The dynamic category tree, never hardcoded

prepare_context_zip(slugs[])

The exact skyboy zip bundle: _CONTEXT_SUMMARY.md + skills/

install_skill(slug, target_dir?)

Local/stdio only. Writes to your filesystem.

One transport flag, one implementation

The stdio transport is what Claude Desktop, Cursor, and Windsurf spawn. The http transport serves the same tools over JSON-RPC POST on a local port, and gives prepare_context_zip a signed download URL instead of a file path. install_skill exists only on stdio: writing to a filesystem needs local trust.

skyboy mcp --transport stdio   # desktop agents (default)
skyboy mcp --transport http    # http://127.0.0.1:8765, read-only + signed zip downloads

Claude Desktop

Add to claude_desktop_config.json (Settings, Developer, Edit Config), then restart Claude Desktop.

{
  "mcpServers": {
    "skyboy": {
      "command": "skyboy",
      "args": [
        "mcp",
        "--transport",
        "stdio"
      ]
    }
  }
}

Cursor

Add to ~/.cursor/mcp.json (or the project-level .cursor/mcp.json), or use Cursor Settings, MCP, Add server.

{
  "mcpServers": {
    "skyboy": {
      "command": "skyboy",
      "args": [
        "mcp",
        "--transport",
        "stdio"
      ]
    }
  }
}

Local http transport

Run skyboy mcp --transport http, then point a URL-based client at it. Bundles come back as signed download links valid for 15 minutes.

{
  "mcpServers": {
    "skyboy": {
      "type": "http",
      "url": "http://127.0.0.1:8765"
    }
  }
}

Hosted remote, zero install

The deployed endpoint at https://mcp.skyboy.in serves the read-only surface. No local process, nothing to manage.

{
  "mcpServers": {
    "skyboy": {
      "type": "http",
      "url": "https://mcp.skyboy.in"
    }
  }
}

prepare_context_zip is skyboy zip

The tool calls the same bundle logic the CLI uses. The archive always has a generated _CONTEXT_SUMMARY.md at its root: a short brief the receiving model reads first, telling it what is in the bundle, how to apply each skill, and the boundaries (nothing executes; surface declared permissions). Plugins are indexed into the summary, never vendored into the archive.

Use it from the CLI too: skyboy add <slug> installs a skill directly. See the MCP agent guide for a walkthrough.