# Skills and MCP

> A read-only view of what your agent CLI already has installed.

Both panes are read-only reflections of the agent CLI's own configuration.
devpit keeps no second copy of either: the CLI already owns those catalogues,
and two sources of truth diverge on the first `claude mcp add`.

## Skills

**Resources → Skills** in the sidebar, or **Settings → Skills**. The header
says **Installed** and how many, there is a search box, and picking one shows
its own `SKILL.md` beside the list. The footer names the directory it all came
from, and **Refresh** reads again — a skill arrives by installing a plugin,
which happens in a terminal beside this window.

With none: *"No skills installed."* — *"Skills arrive with the plugins you
install for the agent CLI."*

<!-- Screenshot — the Skills pane with a skill's document open. -->

### Why a step cannot ask for one

Skills are not part of a [step's](/docs/steps) recipe. The CLI offers a turn
all of them or none, so a step asks for one in its prompt — `/tdd` — the way
you would in a session. A step that tries to declare skills is refused when it
is saved, and the refusal says what does work instead.

## MCP

**Resources → MCPs**. Servers are grouped by scope, because the scope is the
answer to "why is this one here": **This project** travels with the repository,
**Every project** follows you into every project you open. Each row gives the
server's name and how it is reached, with anything that looks like a secret —
a token in a URL, a header, an environment value, a secret-named flag —
masked.

There is no connection dot here, deliberately: this pane reads configuration
files, and claiming a server is connected without having connected to it is the
kind of thing it exists to catch.

Whether the servers answer is in the status strip instead, as **MCP** with how
many answer out of how many there are. Its popover lists them as **Active** and
**Inactive** — connected, failed, or needing sign-in, with the reason — and
**Refresh** asks them again. It checks on its own every ten minutes. A server
installed in a folder your shell adds to `PATH` is found, even when devpit was
opened from the desktop's menu.

The footer button copies the command to manage them — **Manage with `claude
mcp`**, which flips to **Copied `claude mcp`** — because that is where adding
and removing happens, and it changes here.

When there is nothing to show, the pane says why and adds *"Nothing is wrong
with devpit; the CLI has none configured yet."*

## Which installation

One CLI can have more than one configuration directory — a
[profile](/docs/profiles) that sets `CLAUDE_CONFIG_DIR` runs against its own
skills and its own servers. Where there is more than one, both panes show a
picker of them, with one marked **default**. With a single installation it
draws nothing at all: a picker with one choice is a label pretending to be a
control.
