Skip to main content
SkillCreator includes an MCP (Model Context Protocol) server that lets AI agents query your skill library directly. Instead of reading static files, agents can discover, inspect, and use skills dynamically.

What MCP enables

With the MCP server running, an AI agent can:
  • List skills. Browse your entire skill library.
  • Read skills. Load skill content on demand.
  • Check health. View eval scores and quality metrics.
  • Search. Find skills by keyword or tag.
  • Inspect runs. View skill execution history.

How it works

The MCP server is a stdio-based server that proxies all tool calls to the desktop app’s local RPC endpoint. It runs as a subprocess of the desktop app.

Auto-registration

On first launch, SkillCreator automatically registers its MCP server with detected agent runtimes:
RuntimeConfig file
Claude Code~/.claude.json
Cursor~/.cursor/mcp.json
Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.json
Gemini CLI~/.gemini/settings.json
Auto-registration only adds the server entry if the config file exists. It does not overwrite existing configurations.
Auto-registration also writes tool approval permissions to ~/.claude/settings.json for Claude Code.

Headless mode

The MCP server can run independently of the desktop app:
skillcreator --skillcreator-mcp
This starts a headless MCP server that connects to the local runtime. Useful for CI environments or when you want MCP without the GUI.
Last modified on March 19, 2026