Back to blog

How to install skills and MCP servers in Claude Code, from an empty folder

Start from an empty folder and install a skill and an MCP server for Claude Code: search, inspect before installing, where the config files go, and how to check and remove them. Every command was actually run.

SOSourceWeftNov 21, 20265 min read

Last updated: 2026-11-21

What you will finish with

Claude Code with one installed skill and one configured MCP server, and a clear idea of which folders hold their files and how to check and remove them later.

This tutorial covers the install step only. We do not cover installing Claude Code itself; follow Anthropic's own documentation for that and come back.

Every command below was run on 2026-11-20 with the published CLI 0.3.0 in a fresh empty folder. You need Node.js and a terminal. You do not need a SourceWeft account.

Skills and MCP servers in one minute

  • A skill is a folder with a SKILL.md file that tells Claude how to do a kind of task. It may also ship scripts, which run on your machine.
  • An MCP server is a service that lets Claude call outside tools, such as searching Notion. A config entry connects it to Claude Code.

MCP servers vs agent skills covers how to choose. This page is only about installing.

Step 1: Search for a skill

npx @sourceweft/cli skills search "frontend design" --limit 5

Each row is an install name and a short description; a scripts marker appears when the skill ships scripts. Part of what we got:

@anthropics/frontend-design-skills                       Guidance for distinctive, intentional visual design when building new…
@vercel-labs/frontend-design-open-agents                 Create distinctive, production-grade frontend interfaces with high de…

The install name, such as @anthropics/frontend-design-skills, is what the other commands take.

Step 2: Inspect before installing

npx @sourceweft/cli skills info @anthropics/frontend-design-skills
Version:    34040c9c5685
License:    Complete terms in LICENSE.txt
Source:     https://github.com/anthropics/skills/tree/34040c9c568585f6929bedeaad110ad08f079624/skills/frontend-design
Trust:      Featured — a featured publisher, not reviewed by a SourceWeft admin (files are still hash-checked)
Files:      2

Read three things: Source (repository and exact commit), License, and whether a Scripts: yes line appears (it means the skill includes executable files). How to check an agent skill before you install it explains the scan flags.

Step 3: Install it for Claude Code

npx @sourceweft/cli skills install @anthropics/frontend-design-skills --scope project --yes
Installed @anthropics/frontend-design-skills → …/.claude/skills/frontend-design (claude-code)

Two options you will use often:

  • --scope project installs into .claude/skills/ in the current project. Without it the default is user, which installs into ~/.claude/skills/ for every project.
  • --yes skips the confirmation. Without it the CLI prints the details and asks. In a non-interactive shell it stops with Error: Confirmation required. Re-run with --yes to proceed without asking. and writes nothing. Add --yes only after you have read the Step 2 output.

The files we found:

.claude/skills/frontend-design/SKILL.md
.claude/skills/frontend-design/LICENSE.txt
.claude/skills/frontend-design/.sourceweft.json

The first two are the skill; .sourceweft.json is the CLI's record (source, version, per-file hashes). The CLI installs for Claude Code by default. Use --agent for other tools; npx @sourceweft/cli skills agents lists them and their folders.

If Claude Code was already open, start a new session before using the skill.

Step 4: Check it

npx @sourceweft/cli skills list
npx @sourceweft/cli skills doctor
@anthropics/frontend-design-skills  34040c9c5685  claude-code/project    …/.claude/skills/frontend-design
OK — 1 installed skill(s), no problems found.

list shows the scope (project or user). doctor compares the files on disk with the record; run it again later to see whether anyone edited the skill.

Step 5: Configure an MCP server

An MCP config is a piece of JSON. Each server in the SourceWeft catalog has an identifier, such as com.notion/mcp. First print the config without writing anything:

npx @sourceweft/cli mcp install com.notion/mcp --client claude-code
{
  "mcpServers": {
    "notion": {
      "type": "http",
      "url": "https://mcp.notion.com/mcp"
    }
  }
}
This server signs in with OAuth: the config holds no key, and your client opens the server's sign-in the first time it connects (in Claude Code, run /mcp).

The last line means this server signs in with OAuth, the config holds no key, and you sign in the first time by running /mcp in Claude Code.

When it looks right, add --write and the CLI merges it into .mcp.json in the current folder (--client cursor writes .cursor/mcp.json instead):

npx @sourceweft/cli mcp install com.notion/mcp --client claude-code --write
Created "notion" in …/.mcp.json

We also checked:

  • Adding a second server reports "Added" and leaves the existing notion entry as it was.
  • Running the same command again reports "notion" is already in …/.mcp.json; nothing changed.
  • For servers that need an API key, the CLI's help says to pass --key-env NAME, the name of an environment variable; the config refers to the name and never contains the key. Passing --key-env for a server that takes no key, or signs in with OAuth, is an error rather than silently ignored.

.mcp.json in the project root is Claude Code's project-level MCP config. If you commit it, check that it holds only URLs and environment-variable names, never a key.

Step 6: Update and remove

npx @sourceweft/cli skills update --dry-run
npx @sourceweft/cli skills remove gh-anthropics-skills-frontend-design --scope project --yes

--dry-run shows what an update would do without doing it. remove takes the name update prints (here gh-anthropics-skills-frontend-design), not the install name; the folder name frontend-design gives not installed by sourceweft here. Afterwards list prints No skills installed by sourceweft. For an MCP server, edit .mcp.json and delete its entry.

FAQ

Where do Claude Code skills go? .claude/skills/<name>/ for one project, ~/.claude/skills/<name>/ for all projects. Each skill folder needs a SKILL.md.

Where is the Claude Code MCP config? At project level it is .mcp.json in the project root. mcp install … --write merges into it for you.

Do I need a SourceWeft account? No. The commands here were run signed out.

The skill is installed but nothing happens. Check with skills list and skills doctor that the files are under .claude/skills/, then start a new Claude Code session.

How do I know whether a skill is fine to install? Read skills info before installing: source, license and scan flags. This article goes through them. The CLI's file verification has its own walkthrough: Install an agent skill with the SourceWeft CLI.

What this does not do

  • It does not review the skill or the MCP server for you. Files matching the record does not mean the content suits you.
  • It does not install Claude Code itself, and it does not complete an MCP server's OAuth sign-in; that happens in Claude Code.

More ways to find skills: Where to find agent skills and how to install one.

Shareable URL

Keep reading

Related essays

All posts

What are Claude skills, and how do you find and install them?

A plain explanation of Claude skills (agent skills): what a skill folder contains, where to find skills, and two ways to install one, with a command or by hand. Includes what to check before installing.

Read next

MCP servers vs agent skills: what's the difference?

An MCP server connects an agent to a system. A skill teaches an agent how to do a task. A side-by-side comparison, with examples and a rule for choosing.

Read next

What is an agent skills directory? Browse 26,423 skills by category

What an agent skills directory is, what a good listing should show before you install, and how to browse 26,423 skills across 15 categories with search, a CLI and per-skill install guides. Numbers read on 21 November 2026.

Read next