From 92592736684f8d17950cb4022e17ab862e463b62 Mon Sep 17 00:00:00 2001 From: tiennm99 Date: Sun, 11 Oct 2026 02:33:02 +0700 Subject: [PATCH] docs(skills): use the single miti-coolify MCP for both servers miti-sg's Coolify now manages miti-jp too, so the skills search one MCP server instead of two. Drop the stale gitea-mirror watch-path exception; the new miti-jp app has its watch path set. --- .claude/skills/debug-service/SKILL.md | 6 +++--- .claude/skills/migrate-service/SKILL.md | 4 ++-- CLAUDE.md | 1 - 3 files changed, 5 insertions(+), 6 deletions(-) diff --git a/.claude/skills/debug-service/SKILL.md b/.claude/skills/debug-service/SKILL.md index 6099459..3d927ab 100644 --- a/.claude/skills/debug-service/SKILL.md +++ b/.claude/skills/debug-service/SKILL.md @@ -35,10 +35,10 @@ Run `git log --oneline -10 -- /`; a recent change is the first suspect. ## 3. Collect runtime evidence -Coolify has two MCP servers, `miti-jp` and `miti-sg`; the service may live on -either. +One Coolify MCP, `miti-coolify`, manages both servers, `miti-sg` and +`miti-jp`; the service may live on either. -1. `search_resources` with the service name on both servers. +1. `search_resources` with the service name. 2. For a failed deploy: `list_deployments`, then `get_deployment` with `include_log_summary=true`. 3. `get_logs` only when the resource is running; otherwise follow the diff --git a/.claude/skills/migrate-service/SKILL.md b/.claude/skills/migrate-service/SKILL.md index a654c13..5da9145 100644 --- a/.claude/skills/migrate-service/SKILL.md +++ b/.claude/skills/migrate-service/SKILL.md @@ -24,8 +24,8 @@ old resource stays intact until the user deletes it; it is the rollback. ## 1. Identify both resources Read `/compose.yml` and `/README.md`. Then -`search_resources` with the service name on every Coolify MCP server -(`miti-jp`, `miti-sg`). The old one is usually a Service (`get_service`, +`search_resources` with the service name through the Coolify MCP +(`miti-coolify`, which manages both servers `miti-sg` and `miti-jp`). The old one is usually a Service (`get_service`, `list_service_applications`, `list_service_databases`); the new one is an Application whose `git_repository` is this repo and `base_directory` is `/`. If the new app does not exist, the user creates it first — diff --git a/CLAUDE.md b/CLAUDE.md index a7a968b..2b4a649 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -55,7 +55,6 @@ After creating one, check `watch_paths` with the Coolify MCP `get_application`; - `traffmonetizer`, on both `miti-sg` and `miti-jp`, leaves it unset on purpose to be restarted on every push. -- `gitea-mirror` on `miti-jp` is not a real setup; skip it. ## Service directories hold deploy files only