home / mcp / skillhub mcp server

Skillhub MCP Server

Exposes Claude-style skills as MCP tools for cross-client reuse and flexible packaging.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "214140846-skillhub-mcp": {
      "command": "uvx",
      "args": [
        "skillhub-mcp@latest"
      ]
    }
  }
}

Skillhub MCP turns Claude-style skills into MCP tools, enabling any MCP client to call the same skills. It serves as an MCP server that exposes skills, resources, and packaging formats for flexible reuse across editors and agents while supporting multiple transports and resource fetching.

How to use

You run the Skillhub MCP server locally and connect your MCP clients to it. Clients can discover and invoke skills, fetch associated resources, and operate with different transports such as stdio, HTTP, or SSE. Use the built-in resource fetch feature when a client does not have native resource support. Start the server with a standard MCP command, then configure your MCP client to point at the server so you can call skills just like you would with any other MCP endpoint.

How to install

Prerequisites: you need a recent Node.js and npm installed on your system to run the provided runtime commands.

1) Install the runtime tooling and start the server using the recommended launcher.

# Install and run the Skillhub MCP server via UVX (recommended)
{
  "skillhub-mcp": {
    "command": "uvx",
    "args": ["skillhub-mcp@latest"]
  }
}

Additional configuration and usage notes

You can customize the root directory where skills are discovered. The default root is a hidden folder in your home directory, but you can point to an alternate path by providing it as an argument when starting the server.

Safety and compatibility notes

Skills may contain scripts and resources. Skillhub MCP does not execute scripts itself; clients decide how to run resources. Run untrusted content inside sandboxes or containers whenever possible.

CLI reference and transports

You can choose between multiple transports, with stdio as the default. HTTP and SSE transports are also supported for remote or streaming connections.

When configuring your environment, you will often see run-time examples that pass the package name and a version tag to a launcher. Use the exact command and arguments shown here.

Examples: attaching the server to editors

Cursor, Claude Code, and Codex can connect to Skillhub MCP servers. Use the following patterns to configure each client to locate and start the server.

Cursor configuration (examples shown in the editor’s MCP settings):

```
{
  "mcpServers": {
    "skillhub-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": ["skillhub-mcp@latest", "/path/to/skills"]
    }
  }
}
```

This connects Cursor to the Skillhub MCP server running with your skills root. Replace "/path/to/skills" with the actual path where you store skills.

Skills layout and packaging

Skills can be a directory containing SKILL.md or a zip/.skill archive. Nested directories and archives are supported so you can organize skills flexibly.

All files in a skill root become downloadable resources for clients. The client decides how to use or run resources.

Available tools

fetch_resource

Fetch downloadable resources for MCP clients that lack native resource support, enabling clients to read scripts, datasets, and examples shipped with skills.