All comparisons

Last reviewed:

SkillReg and MCP Registries: Skills and MCP Servers Are Two Layers

Facts about third-party tools were checked on October 16, 2026. Each one links to a numbered, dated source at the bottom of the page. Anything we could not check is marked "not verified".

Smithery, Glama and the official MCP Registry often come up next to SkillReg when people search for "where to share agent skills". They answer a different question. MCP registries help you find MCP servers, which give an agent new tools. SkillReg hosts skills, which tell an agent how to do a task. Most teams will end up using both layers.

Skills and MCP servers are different things

A skill is a directory with a SKILL.md file: YAML frontmatter with a name and a description, then instructions the agent follows when the skill applies [3]. It is text that changes how the agent works, for example "how we write release notes" or "how we deploy this service".

An MCP server is a program that exposes tools over the Model Context Protocol. An agent connects to it and calls its tools, for example "create a GitHub issue" [1].

Claude Code itself treats them as separate surfaces: its managed settings list skills and mcp as distinct customization sources that administrators can lock independently [4].

What MCP registries do

MCPfinder alone reports an index of "25,000+ MCP servers" across these three registries [2]. These registries list servers to connect to, not SKILL.md instructions.

The Smithery Skills Registry is a separate product

Smithery also runs the Smithery Skills Registry at smithery.ai/skills. Its CLI documents it in a separate "Skills" section, with smithery skill search, smithery skill add <skill> --agent <name>, votes and reviews [1]. It is a public directory of skills, distinct from Smithery's MCP registry. We compare public skill directories, including this one, in SkillReg vs Public Skill Directories.

Where SkillReg fits

SkillReg is not an MCP server registry. It does not list, host or proxy MCP servers. It is a private registry for your organization's skills: publish versions with skillreg push, install them for Claude, Codex and Cursor with skillreg pull, and get security scanning on every publish on all plans, with audit logs from Team (pricing).

QuestionMCP registries (Smithery MCP, Glama, official MCP Registry)SkillReg
What is listedMCP servers and the tools they expose [1] [2]SKILL.md skills
What the agent getsNew tools it can call [1]Instructions on how to do a task [3]
AudiencePublic discovery of servers [2]Private sharing inside an organization
Claude Code settingMCP configuration surface [4]Skills surface, installed into .claude/skills/

Using both layers

A typical setup uses an MCP server for access and a skill for know-how. For example, connect a GitHub MCP server found in an MCP registry, then publish a triage-issues skill in SkillReg that tells the agent how your team labels and assigns issues with that server's tools. The server stays public and generic; the skill stays private and specific to your team.

Related comparisons

Sources

  1. @smithery/cli 4.11.1 on npm, README, sections "MCP Servers", "Tools", "Skills" and "Publishing". Version published 2026-04-30; checked 2026-10-16.
  2. @mcpfinder/server 1.5.0 on npm, README of MCPfinder, a third-party index of MCP servers. Version published 2026-10-01; checked 2026-10-16.
  3. skills 1.7.2 on npm, README of the skills CLI, sections "What are Agent Skills?" and "Creating Skills". Version published 2026-10-09; checked 2026-10-16.
  4. @anthropic-ai/claude-agent-sdk 0.3.301 on npm, Claude Code settings types in sdk.d.ts (strictPluginOnlyCustomization). Version published 2026-10-15; checked 2026-10-16.

Ready to try SkillReg?

Get started for free. No credit card required.

Get Started Free