Skip to main content
Glama

skills-mcp

MCP server that serves agent skills (SKILL.md bundles, the format used by Claude Code plugin skill repos like cloudflare/skills) to any MCP client — including clients that can't install plugins, such as claude.ai / Claude Desktop connectors or an aggregator like MetaMCP.

Skills are exposed two ways:

  • Tools — list_skills, read_skill, read_skill_file for tool-oriented clients. The server's MCP instructions list every skill so models know when to load one.

  • Resources — skill://<name>/SKILL.md (plus each bundled file) for resource-aware clients.

Configuration

Env var

Meaning

SKILLS_SOURCES

Comma-separated skill sources (required). Each entry is owner/repo, owner/repo#ref, or an absolute local path.

SKILLS_CACHE_DIR

Cache directory for GitHub tarballs (default: OS tmpdir).

GitHub sources are fetched as tarballs on startup (no git needed) and fall back to the cached copy if the fetch fails.

Related MCP server: Agent Skills MCP

Usage

SKILLS_SOURCES=cloudflare/skills,raymatos/my-skills npx -y skills-mcp-server

Any directory containing a SKILL.md (searched up to 6 levels deep) is a skill; YAML frontmatter name: and description: are used when present.

License

MIT

Available Tools

3 tools
list_skillsList SkillsA
Read-onlyIdempotent

List all available agent skills with name, description, source, and bundled files. Call read_skill to load one.

Inputs: no named parameters.

read_skillRead SkillA
Read-onlyIdempotent

Read a skill's SKILL.md instructions. Use the returned guidance for the current task; it may reference supporting files readable via read_skill_file.

Inputs: name (required).

read_skill_fileRead Skill FileA
Read-onlyIdempotent

Read a supporting file bundled with a skill (paths are listed by list_skills and referenced from SKILL.md).

Inputs: name (required), path (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping role: listing skills, reading the main skill instructions, and reading supporting files. There is no ambiguity about which tool to use for a given step.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: list_skills, read_skill, read_skill_file. The verb and noun are clear and predictable.

    Tool Count5/5

    Three tools is perfectly scoped for a skills management server. Each tool is necessary and there are no redundant or extraneous tools.

    Completeness5/5

    The tool surface covers the full workflow for accessing skills: discovery, reading the primary instructions, and accessing bundled files. No obvious gaps for the stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers