Manage MCP servers

Manage MCP servers across coding agents

Agents Pack CLI 0.2.0 can configure the same remote MCP server for Claude Code, Codex, and Cursor in one operation. The configuration is user- or machine-level: it applies across projects, does not write project files, and does not require agents-pack init.

The first release supports remote HTTP endpoints, including Streamable HTTP. It does not support local stdio servers or deprecated remote SSE configuration.

Ask your coding agent

Core pack 0.28.0 and newer includes the required ap-add-mcp skill. Ask:

Use ap-add-mcp to add the remote MCP server named docs at
https://example.com/mcp to Claude Code, Codex, and Cursor.
Preview the change before applying it, then verify every provider.

The skill checks agents-pack mcp --help first. If the installed executable is older than CLI 0.2.0, it stops and asks you to upgrade the CLI instead of editing provider files directly.

Add a server directly

Preview first, then apply the same plan:

agents-pack mcp add docs \
  --url https://example.com/mcp \
  --dry-run

agents-pack mcp add docs \
  --url https://example.com/mcp \
  --yes

All three providers are selected by default. To target only some of them:

agents-pack mcp add docs \
  --url https://example.com/mcp \
  --agents claude,codex \
  --yes

Every selected provider CLI must be installed and available on PATH. Agents Pack validates all targets before it writes any configuration.

Use HTTPS for non-local endpoints. Do not put credentials in the URL.

Authenticate each provider separately

Adding configuration does not authenticate the MCP server. Agents Pack does not copy tokens or OAuth state between providers and does not report a clean configuration as an authenticated connection.

When the server requires OAuth, authenticate each selected provider:

codex mcp login docs
claude mcp login docs
agent mcp login docs

Cursor can also complete authentication through its MCP settings. Provider login behavior changes independently, so follow the current Codex MCP documentation, Claude Code MCP documentation, or Cursor MCP documentation if a provider presents a different flow.

Inspect status

Status is always read-only:

agents-pack mcp status
agents-pack mcp status docs

It reports each provider as:

State	Meaning
`clean`	The provider matches the configuration Agents Pack recorded.
`missing`	A managed provider entry is absent.
`drifted`	A managed provider entry changed outside Agents Pack.
`unmanaged`	The name exists, but Agents Pack does not own it.
`malformed`	Provider configuration cannot be read safely.
`unavailable`	The required provider CLI is not available.

Agents Pack stores the server URL, original provider targets, and creation time in ~/.agents-pack/mcp-lock.json. It never stores authentication secrets there.

Remove a managed server

Preview removal, apply it, then verify:

agents-pack mcp remove docs --dry-run
agents-pack mcp remove docs --yes
agents-pack mcp status docs

Removal targets the provider set recorded when the server was added. Agents Pack refuses to adopt or remove an unmanaged entry, and it stops on drift instead of overwriting a provider change.

Add and remove snapshot affected configuration and record an operation journal. If a provider command fails, Agents Pack rolls the operation back. A later mutation can recover an interrupted transaction.