mcpField
S
Skillhub Mcp

Skillhub Mcp

Local
github.com/214140846AI & Agents1Updated 41w ago

About Skillhub Mcp

Skillhub MCP turns Claude-style skills stored as directories or archives into tools and resources for MCP clients. It is for teams reusing skills across agents and supports nested folders, packaged skills, and multiple transports.

Key features

  1. 01Expose skills as MCP tools
  2. 02Discover nested skill directories
  3. 03Support .zip and .skill packages
  4. 04Provide scripts and files as resources
  5. 05Offer stdio, HTTP, and SSE transports

Use cases

  1. 01Reuse a skill across different MCP clients
  2. 02Organize skills in nested folders
  3. 03Load skills packaged as .zip or .skill files
  4. 04Let a client read skill files as resources

MCP support

The MCP server exposes discovered skills as tools and their accompanying files as resources. It supports stdio, HTTP, and SSE transports, with a fetch_resource tool for clients lacking native resource support.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"skillhub": {
"command": "uvx",
"args": [
"skillhub-mcp"
]
}
}
}
Run commanduvx skillhub-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypiskillhub-mcp1.0.5

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Skillhub MCP

Skillhub MCP logo

PyPI version PyPI downloads

Links

mcp-name: io.github.214140846/skillhub-mcp

You already have Claude-style skills (SKILL.md), but in practice you often hit a wall:

  • your client speaks MCP, not Claude Skills
  • your team uses multiple agents (Cursor, Copilot, Codex, etc.), so skills are painful to reuse across tools
  • you want a more flexible way to organize and ship skills (nested folders, zip packaging)

Skillhub MCP bridges that gap: it turns Claude-style skills into MCP tools, so any MCP client can call the same skills.

⚠️ Experimental. Skills may contain scripts/resources. Treat them as untrusted and run with sandboxes/containers when possible.

Is this an MCP server or an MCP client?

This project is an MCP server.

  • Skillhub MCP (this repo): runs as a server process and exposes tools/resources to clients.
  • MCP clients: editors/agents like Cursor, Claude Code, Codex, etc. They start or connect to MCP servers.

What You Get

  • Cross-client reuse: install once, use from any MCP client
  • Flexible packaging: nested directories, .zip and .skill archives
  • Skill resources: expose scripts/datasets/examples as MCP resources (files the client can read)
  • Resource fallback: a fetch_resource tool for clients without native MCP resource support
  • Multiple transports: stdio (default), http, sse

Quick Start

Default skills root: ~/.skillhub-mcp

uvx (recommended)
{
  "skillhub-mcp": {
    "command": "uvx",
    "args": ["skillhub-mcp@latest"]
  }
}

Use a custom skills root:

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

Install in Popular Editors (MCP Clients)

Below are minimal working examples for mainstream “vibe coding” editors.

Cursor

Cursor supports configuring MCP servers via mcp.json. Add the following to your global ~/.cursor/mcp.json or project .cursor/mcp.json, then restart Cursor.

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

Option A: configure via Claude Code CLI (recommended for quick setup):

claude mcp add --transport stdio skillhub-mcp -- uvx skillhub-mcp@latest /path/to/skills

Option B: project-scoped configuration via .mcp.json at your project root. You may need to explicitly allow project MCP servers in .claude/settings.json.

./.mcp.json

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

./.claude/settings.json (approve only this server)

{
  "enabledMcpjsonServers": ["skillhub-mcp"]
}
Codex (OpenAI)

Option A: use the Codex CLI to add a stdio MCP server:

codex mcp add skillhub-mcp -- uvx skillhub-mcp@latest /path/to/skills

Option B: edit ~/.codex/config.toml:

[mcp_servers.skillhub-mcp]
command = "uvx"
args = ["skillhub-mcp@latest", "/path/to/skills"]

Skill Format

Skillhub MCP discovers skills under the root directory (default ~/.skillhub-mcp). Each skill can be:

  • a directory containing SKILL.md
  • a .zip or .skill archive containing SKILL.md (at the archive root or inside a single top-level folder)

All other files become downloadable MCP resources for your agent to read. Note: Skillhub MCP does not execute scripts; the client decides whether/how to run them.

Example layout:

~/.skillhub-mcp/
├── summarize-docs/
│   ├── SKILL.md
│   ├── summarize.py
│   └── prompts/example.txt
├── translate.zip
├── analyzer.skill
└── web-search/
    └── SKILL.md

Archive rules:

translate.zip
├── SKILL.md
└── helpers/
    └── translate.js
data-cleaner.zip
└── data-cleaner/
    ├── SKILL.md
    └── clean.py

Directory Structure: Skillhub MCP vs Claude Code

Claude Code expects a flat skills directory (each immediate subdirectory is one skill). Skillhub MCP is more permissive:

  • nested directories are discovered
  • .zip / .skill packaged skills are supported

If you need Claude Code compatibility, keep the flat layout.

CLI Reference

skillhub-mcp [skills_root] [options]

Flag / OptionDescription
positional skills_rootOptional skills directory (defaults to ~/.skillhub-mcp).
--transport {stdio,http,sse}Transport (default stdio).
--host HOSTBind address for HTTP/SSE transports.
--port PORTPort for HTTP/SSE transports.
--path PATHURL path for HTTP transport.
--list-skillsList discovered skills and exit.
--verboseEmit debug logging.
--logMirror verbose logs to /tmp/skillhub-mcp.log.

Safety Notes

  • Skills are not "just prompts": they can include scripts and arbitrary files.
  • Skillhub MCP does not run scripts, but your client might. Prefer running in a sandbox/container.

Language

  • English: README.md
  • 中文: README.zh-CN.md

About the Author

I focus on AI SaaS going global, covering the full journey from idea validation and vibe coding to product development, infrastructure, SEO, backlinks, and growth experiments.

Everything shared here comes from real projects, real traffic, and real revenue attempts.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.