MCP Manager Skill

Manage MCP servers for openclacky. The user's MCP configuration lives at ~/.clacky/mcp.json (the same format Claude Desktop and Cursor use). You never ask the user to edit it by hand, you do it for them through the local clacky HTTP API.

---

Command Parsing

User says	Subcommand
add mcp, install mcp, connect <something>, "I want clacky to read my files / access github / query my db / search the web"	add
mcp list, mcp status, "what mcps do I have"	list
mcp probe <name>, "what tools does <name> have"	probe
mcp remove <name>, mcp delete <name>	remove
mcp reconfigure <name>, mcp fix <name>	reconfigure

If the intent is unclear, default to add, it's the most common ask.

---

Server Coordinates

All API calls go to the local clacky server. The host and port are exposed via environment variables:

HOST="${CLACKY_SERVER_HOST:-127.0.0.1}"
PORT="${CLACKY_SERVER_PORT:-7070}"
BASE="http://${HOST}:${PORT}"

All write operations require requests to come from 127.0.0.1 or ::1. They will, because we're running locally.

---

API Cheat Sheet

Action	Call
List configured servers	curl -s ${BASE}/api/mcp
Add a server	curl -s -X POST ${BASE}/api/mcp -H 'Content-Type: application/json' -d '{...}'
Update a server	curl -s -X PUT ${BASE}/api/mcp/<name> -H 'Content-Type: application/json' -d '{...}'
Remove a server	curl -s -X DELETE ${BASE}/api/mcp/<name>
Probe tools	curl -s -X POST ${BASE}/api/mcp/<name>/probe

Request body for create/update, stdio (local process, default):

{
  "name": "filesystem",
  "command": "npx",
  "args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/me/Documents"],
  "env": { "API_KEY": "xxx" },
  "description": "Read/write files in ~/Documents"
}

Request body for create/update, http (remote server, streamable-http):