CLACOROO
EN IT
Download

MCP servers

A Model Context Protocol (MCP) server gives Claude Code a structured channel to talk to an external tool — a database, a docs index, an API, a vector store, anything that speaks MCP. The MCP servers section in CLACOROO shows every server registered with Claude Code, their live status, lets you add new ones through a clear form, and lets you remove or re-authenticate the ones you have.

Mutations run the official claude mcp ... commands under the hood.

Overview

The MCP servers section, with cards showing server name, transport (http/sse/stdio), status (Connected/Needs Auth/Error/Warning) and action buttons.

Each MCP server is a card (or row in Compact view). The card carries:

  • Name of the server
  • Source badge — claude.ai (built-in) · plugin · user-added
  • Transport — http, sse, stdio
  • Status — Connected · Needs Auth · Warning · Error · Disabled
  • Description — what the server provides (when declared)
  • Enable/disable toggle (servers you added only) + action buttons depending on source and status: Tools, Remove, Re-authenticate, Clear auth cache, Open settings.json

Above the cards: a topbar with + MCP to register a new server, filters, sort, search and Cards / Compact view switch.

What it shows

Status badges

Status reflects what claude mcp list reports:

StatusMeaning
ConnectedThe server is reachable and responding correctly
Needs AuthThe server is reachable but requires you to authenticate (OAuth or similar)
WarningThe server responded but with non-critical issues
ErrorThe server is unreachable or returning errors
DisabledThe server is registered but currently disabled

The Dashboard’s MCP connected KPI counts Connected servers against the total.

Source badges

  • claude.ai · global — built-in to Claude Code, you didn’t add it
  • plugin: <name> — registered by a plugin you installed
  • user-added — you added it yourself via the + MCP form

Only user-added servers can be removed from this UI. Plugin-provided servers come and go with their plugin; built-in servers are managed by Claude Code.

Transports

  • http — request/response over HTTPS
  • sse — server-sent events (streaming HTTP)
  • stdio — local subprocess CLACOROO talks to over stdin/stdout

The transport determines which fields the + MCP form will ask for (URL for http/sse, command + args for stdio).

Add MCP form

The Add MCP server form, with name, transport radios (http/sse/stdio), URL/command field, args list, environment variables and HTTP headers.

The form is split by section:

  • Name — a short identifier (letters, digits, hyphens, dots)
  • Transport — three radio cards; pick one
  • URL (for http/sse) — full HTTPS endpoint; required
  • Command + args (for stdio) — the executable and its arguments; the form lets you add args one at a time
  • Environment variables — KEY=VALUE pairs; useful for tokens
  • HTTP headers (for http/sse) — Header: value pairs; useful for Authorization: Bearer ...
  • Scope — global or current project

Submit runs claude mcp add --transport <t> [-s <scope>] [-e KEY=VAL] [-H HEADER:VAL] <name> <target> [-- args]. The new server appears immediately and starts probing for its first status.

Common tasks

How to add an MCP server

  1. Click + MCP in the topbar
  2. Fill in the Name and pick a Transport
  3. Provide the URL (http/sse) or Command + args (stdio)
  4. Add env vars or headers if the server needs auth via token
  5. Pick scope (global usually)
  6. Click Add — CLACOROO runs the official claude mcp add command
  7. The new card appears with status Connecting… then settles to one of the real statuses

How to authenticate a “Needs Auth” server

  1. On the card, click Authenticate
  2. CLACOROO opens the built-in terminal with claude mcp authenticate <name> prepared
  3. Follow the prompts in the terminal (often an OAuth flow that opens your browser)
  4. Once done, click Refresh on the card; the status flips to Connected

How to remove an MCP server

  1. Click Remove on the card (visible only on user-added servers)
  2. Confirm in the dialog (it shows the exact claude mcp remove command that will run)
  3. The card disappears; the Dashboard’s MCP KPI updates

How to clear an MCP auth cache

If a server is stuck in Needs Auth but you know it’s authenticated server-side:

  1. Click Clear auth cache on the card
  2. Click Refresh to re-probe
  3. The server should flip to Connected without re-authenticating

How to enable/disable an MCP server (toggle)

Servers you added have an enable/disable toggle on the card (same style as plugins). It’s handy to save tokens: every connected server adds its tools to Claude’s context — keep on only the ones you need.

  1. Disable by switching the toggle off → confirm in the dialog → CLACOROO removes the server from Claude Code (claude mcp remove) but saves the configuration, so you don’t have to re-enter it
  2. Re-enable by switching the toggle back on → the server is re-added with the saved config, in one click

Built-in (claude.ai) and plugin-provided servers don’t have the toggle: the former are managed on claude.ai, the latter are enabled/disabled together with the owning plugin (Plugins section).

Tips & shortcuts

  • The status dot color is the fastest scan: green = good, yellow = needs auth, red = error, gray = disabled
  • Hover the status to see when it was last checked, and the raw response if Claude Code recorded one
  • A server with error is not retried automatically every render — click Refresh to re-probe
  • stdio servers can be slow to first connect (the subprocess has to start) — give them a few seconds before declaring an error
  • Use search to find a server by name or by part of its URL — useful when you have many

Edge cases & errors

  • The server stays at “Connecting…” forever. Either the transport is wrong (you picked http but the server only speaks stdio) or the endpoint is unreachable. Click the status to see Claude Code’s last error.
  • “Add MCP” fails with a regex error. The name field allows only letters, digits, hyphens, dots — no spaces or special characters. Rename and retry.
  • Headers don’t seem to be sent. Make sure each header is in the form Header-Name: value (one per line). The form validates this; the toast tells you which line is off.
  • Removing or disabling a built-in or plugin server isn’t possible. The Remove button and toggle are hidden by design for those sources. For a plugin server, disable/remove the owning plugin from the Plugins section.
  • Multiple servers with the same name. Two scopes (global and project) defined the same name. Open claude_desktop_config.json or the project’s MCP config to disambiguate.
  • Hooks — the other “extension point” Claude Code exposes
  • Plugin manager — plugins can ship MCP servers; managing them there also affects this section
  • Claude Config — the global claude_desktop_config.json editor
  • Dashboard — the MCP connected KPI summarises this section