MCP | hugsy

Hugsy includes a native Swift MCP server. It runs locally over stdio, with the same offline registry as the CLI. All tools and resources are read-only.

Connect a host

Install the CLI, then add this configuration to your MCP host. Use an absolute executable path if the host does not inherit your shell’s PATH.

MCP configuration

{
  "mcpServers": {
    "hugsy": {
      "command": "hugsy",
      "args": ["mcp"]
    }
  }
}

Print the same configuration with hugsy mcp-config. Run the server directly with:

Terminal

hugsy mcp

Tools

Read-only MCP tools
Tool	Input	Result
`search_components`	Optional `query`	Component summaries, categories, and animation techniques.
`get_component`	`name`	Full Swift source, usage, accessibility notes, and checksum.
`plan_install`	`names`, up to six	Source files and safe CLI commands. No filesystem access.

Resources and prompts

Read hugsy://registry for the complete registry or hugsy://components/<name> for an individual Swift source file. The integrate_component prompt accepts a component name and returns a source-aware integration checklist.

A deliberate boundary

The MCP process does not read your project, write files, or execute shell commands. Your tools inspect the source, explain the integration, and use the CLI with your approval. Start with --dry-run --json, and never replace customized files without permission.

The static website also provides llms.txt, complete component notes, and the JSON registry. GitHub Pages does not host an MCP process.