Skill MCP Server

Skill MCP server exists for a simple reason — assistants are far more useful when they can act on Skill directly instead of describing what you should do. Search the skill-builder registry and auto-install skills for Claude Code, Cursor, and Codex.

What you get

Publish and install AI skill prompts from the command line — or author them in the web editor with help from an AI drafting assistant.

Setting it up

@dmzagent/skill-builder on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need one environment variable: SKILL_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by com.dmzagent; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the skill mcp server does with a few real requests.