name: mcp-registration
mcp.json, .claude/mcp.json, or user config), when tools do not appear in the client, or when a task requires end-to-end MCP smoke testing (listTools and callTool). Trigger on requests like "MCP登録", "mcp.json設定", "MCPサーバ追加", and "MCP動作検証".Use this skill to add MCP server registrations safely and verify they actually work. Always finish with executable verification, not config edits alone.
Check these in order and use the one the user requested:
mcp.json.claude/mcp.json~/Library/Application Support/Code/User/mcp.jsonPreserve the existing top-level schema:
mcpServers, add under mcpServers.servers, add under servers.mcpServers for project-local files unless the user specifies another format.Use this shape:
{
"mcpServers": {
"server-name": {
"command": "npx",
"args": ["tsx", "mcp/server.ts"],
"cwd": "/absolute/path/to/project",
"env": {
"KEY": "<token>"
}
}
}
}
Rules:
cwd absolute.<token> in repo-managed configs.mcpServers vs servers).Run:
...Server running on stdio.Prefer MCP SDK client verification over manual assumptions:
StdioClientTransport.listTools and verify expected tool names.success: true.For DB-backed servers without production credentials, use local test env when possible (e.g., file: SQLite/libSQL URL).
Report:
<token>).mcp.json を探すために ~/ を再帰検索するとmacOSの権限エラーが大量に出る。プロジェクトルート、.claude/、VSCode設定ディレクトリなどターゲットパスを先に確認するmcp.json に追加しただけで完了とすると、スキーマ不一致やランタイムエラーが本番で初めて発覚する。必ず tools/list + tools/call まで通す<token> プレースホルダか source .env.local 方式を使うreferences/mcp-registration-checklist.md: execution checklist and decision rules.references/competitor-ui-viewer-notes-2026-02.md: practical tips captured from a real implementation.