Skip to main content
Glama
@skills-hub-ai/mcp

@skills-hub-ai/mcp

README.md
# @skills-hub-ai/mcp

MCP server for [skills-hub.ai](https://skills-hub.ai) — serve your installed skills as prompts in Claude Code, Cursor, or any MCP-compatible tool.

## Setup

### Claude Code

```bash
claude mcp add skills-hub -- npx @skills-hub-ai/mcp
```

### Cursor

Add to your Cursor MCP settings (`~/.cursor/mcp.json`):

```json
{
  "mcpServers": {
    "skills-hub": {
      "command": "npx",
      "args": ["@skills-hub-ai/mcp"]
    }
  }
}
```

### Manual (any MCP client)

```json
{
  "command": "npx",
  "args": ["@skills-hub-ai/mcp"]
}
```

## How It Works

The server scans these directories for installed skills:

| Tool        | Directory           |
| ----------- | ------------------- |
| Claude Code | `~/.claude/skills/` |
| Cursor      | `~/.cursor/skills/` |

Each skill directory should contain a `SKILL.md` file (installed via `skills-hub install <slug>`).

Skills are exposed as **MCP prompts** — your AI tool can list and invoke them. The server caches discovered skills for 30 seconds.

## Installing Skills

Use the [CLI](https://www.npmjs.com/package/@skills-hub-ai/cli) to install skills:

```bash
npx @skills-hub-ai/cli search "code review"
npx @skills-hub-ai/cli install <skill-name>
```

## Links

- [Browse skills](https://skills-hub.ai/browse)
- [CLI](https://www.npmjs.com/package/@skills-hub-ai/cli)
- [Getting Started](https://skills-hub.ai/docs/getting-started)
- [GitHub](https://github.com/tinh2/skills-hub-mcp)

TDQS

A3.7/5.0

Scored across 4 tools

Disambiguation5/5

Each tool maps to a distinct resource+action pair: catalog search, catalog detail lookup, local inventory listing, and installation. There is no plausible confusion between remote catalog reads and local-state operations.

Naming Consistency5/5

All four tools use consistent snake_case verb_noun naming (search_skills, get_skill_detail, list_installed_skills, install_skill). The verb choice (search/get/list/install) accurately signals the action in each case.

Tool Count4/5

Four tools is small but appropriate for a focused catalog-plus-installer client; each tool earns its place with no filler. It leans slightly thin, since a couple of lifecycle operations are absent.

Completeness4/5

The core flow (search → inspect → install, plus listing what is installed) is fully covered with no dead ends. Minor gaps remain: no uninstall/remove tool, no update/upgrade for installed skills, and no way to read an installed skill's local instructions.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues