Help users discover, install, configure, and manage MCP servers. Supports OpenClaw, Claude Desktop, Claude Code, and Cursor.
Core Principles
ClawHub First — Always check for a ClawHub plugin bundle before raw server install. Bundles include skills and workflows on top of the MCP connection.
Never Store Secrets — Auth values are always env var references (${VAR_NAME}), never raw tokens. Never ask the user to paste their actual token in chat.
Verify Before Acting — Confirm server choice and auth readiness before installing.
Guide Completely — Don't just install. Walk through auth setup and verification.
Intent Routing
Classify the user's request into one of these intents, then follow the corresponding workflow.
DISCOVER — "What MCP servers are available for X?"
If clawHubMatch is present, mention the bundle first: "There's a [bundle name] plugin on ClawHub with [N] skills — want that instead?"
Present results as a numbered list with name, description, and auth requirements.
If any result has "source": "npm" or "source": "smithery", add a note: "This server is from [npm/Smithery] and hasn't been verified by our team. It should work but proceed with caution."
Offer to install any result.
If user asks "what else should I install?" or "recommend more servers":
text
Step 2 — ClawHub bundle offer:
If clawHubMatch is present, offer the bundle:
I found a [bundle displayName] plugin on ClawHub that includes the MCP connection plus [skillCount] additional skills. Would you like the full bundle, or just the raw MCP connection?
If user wants the bundle, guide them to install via ClawHub (clawhub install <bundleId>). Then record the install and stop.
Step 3 — Confirm server:
If multiple results, present a numbered list and ask user to pick. If one result, confirm: "I'll set up [displayName] — sound good?"
Step 3.5 — Compatibility check (if non-default client):
If the user specified a client or you detected a non-OpenClaw client, check compatibility:
The --client flag is optional. If omitted, the script auto-detects the client (OpenClaw, Claude Desktop, Claude Code, or Cursor). The output includes mergeTarget (the config file path) and client (the detected client name).
Step 5 — Auth guidance (if server has requiredEnv):
Follow the Auth Guidance Pattern below. Wait for user to confirm they have their token ready before proceeding.
This script checks prerequisites and returns the install command — it does NOT run it.
If prerequisitesMet is false, show the prerequisites.suggestion and help the user install the prerequisite first.
If prerequisitesMet is true, run the installCommand.command directly using the Bash tool. For example, if the output says "command": "npx -y @github/mcp-server --help", run that command to verify the package resolves.
If installCommand.command is null (HTTP servers), skip — no install needed.
If the install command fails, try the installCommand.fallbackCommand if present, or consult {baseDir}/references/troubleshooting.md.
Step 7 — Write config:
Present the configEntry from step 4 and explain it needs to be added to the config file at mergeTarget (the path returned by build_config.py). If the config file exists, merge the new server entry into the existing mcpServers object. If it doesn't exist, create it:
If status is "healthy", include the tool count in the summary. If "unhealthy" or "error", troubleshoot before declaring success — consult {baseDir}/references/troubleshooting.md.
Step 9 — Summary:
Tell the user what was installed, what tools are now available (from health check if run), and remind them to restart their client to pick up the new server.
BULK INSTALL — "Install the dev toolkit" / "Set up servers for data work"
If user mentions a specific bundle, resolve it. If they describe a use case, match to the closest bundle:
If unconfigured has entries: "I found [count] MCP server packages on your system that aren't configured yet: [list them]. Want me to set up any of them?"
If alreadyConfigured has entries: mention them as already active.
If nothing detected: "No known MCP server packages found. Want me to search for servers to install?"
For each server the user wants to configure, follow the INSTALL workflow starting at Step 4 (Build config) — the package is already installed.
RECOMMEND — "Set up MCP for this project" / "What servers should I use?"
If the user specifies a project type: python3 {baseDir}/scripts/recommend_servers.py --template "<type>"
Available templates: python-web, node-fullstack, data-science, mobile, devops, static-site.
If detected is true:
Present the detected template: "This looks like a [displayName] project (matched [files/patterns])."
List recommended servers first, then optional servers.
Mark any that are already configured.
Offer to install the recommended set (routes to BULK INSTALL logic).
If detected is false:
List available templates and ask the user to pick one.
Or suggest running DISCOVER for a broader search.
CONFIGURE — "Set the API key for X" / "Connect X to my database"
Identify the server from the user's request.
Run build_config.py --server-id "<id>" with any custom env/args the user provides:
text
If managers are found, offer the option: "I detected [manager name] on your system. Want to store this token there instead of in your shell profile? It's more secure."
If yes, generate the store command:
text
Config generation fails: Show a manual config example from {baseDir}/references/transport-patterns.md and walk through it.
Server starts but tools don't appear: Run python3 {baseDir}/scripts/health_check.py --server-id "<id>" to diagnose. Consult {baseDir}/references/troubleshooting.md.
Health check times out: The server may need env vars, a database connection, or more time. Try increasing the timeout with --timeout 30.
Config not found for a client: Check the mergeTarget path from build_config.py. See {baseDir}/references/troubleshooting.md for client-specific config paths.
Categories
Available category filters for discovery: developer-tools, database, communication, productivity, cloud-infra, ai-ml, data, cms-content, finance, observability, search, auth, storage, version-control, browser.