update-taptap-mcp
Use when users ask to update, refresh, or upgrade the local TapTap Maker MCP package.
makecindy · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add makecindy/cindy-official-plugins --skill update-taptap-mcp技能说明
name: update-taptap-mcp description: Use when users ask to update, refresh, or upgrade the local TapTap Maker MCP package.
TapTap Maker MCP Upgrade Workflow
Use the CLI upgrade entry instead of hand-writing npm cache or client-config scripts. Maker local
development is published by @taptap/maker; do not update the legacy main Open API package for
Maker workflows.
Scope
This workflow upgrades only the current machine and the current Maker project directory.
- Do not scan unrelated Maker projects.
- Do not batch-upgrade multiple projects.
- Do not delete old config backup files. Historical
.bak.*files have no reliable ownership marker and must be left untouched. - The MCP status surface only checks the package policy and reports
required_upgrade,update_available,current,unavailable, orskipped. It never runstaptap-maker upgradeby itself.
Required Steps
- Read
maker://status; if resources are unavailable, fall back tomaker_status_lite. Usemaker_status_lite({ detail: true })only when package or connection diagnostics are explicitly needed. If theMaker MCP package updatesection reportsrequired_upgrade, explain the version reason to the user first. Do not run any upgrade command before that explanation and approval step. - Identify the current Maker project directory. Use
--target-dironly when the directory is confirmed to be a Maker project, which means it or one of its parents contains.maker-mcp/config.json. This argument only selects the project whose managedAGENTS.mdpolicy is updated; it never writes that directory into user-level MCP config. - If the AI client has exactly one attached workspace and that workspace is the Maker project, use
that workspace as
<PROJECT_DIR>. If there are multiple workspaces, or the current directory is not clearly a Maker project, ask the user for the Maker project directory before using--target-dir. - Read the exact target package version from the status result (
latestorlatest_beta, matching the user's current release channel). After the user approves the upgrade, run that exact package version for the confirmed project:
npx -y -p @taptap/maker@<TARGET_VERSION> taptap-maker upgrade --target-dir <PROJECT_DIR>
If the user only wants one client, pass --ide codex, --ide cursor, or --ide claude.
If the user only wants to refresh the machine-level MCP command and no Maker project directory is
confirmed, explain that this refresh will not update project AGENTS.md, then run
npx -y -p @taptap/maker@<TARGET_VERSION> taptap-maker upgrade without --target-dir only after the
user agrees.
- Tell the user that the current MCP session remains available and continues using the existing
version and proxy tools. The updated package and
AGENTS.mdtake effect on the next MCP start or user-requested reconnect; do not require a new conversation. - After the next restart/reconnect, verify by reading
maker://status; if resources are unavailable, callmaker_status_lite.
Status-Driven Upgrade Notes
- Trigger timing is limited to the startup asynchronous check and the 12-hour TTL lazy check from
maker://status/maker_status_lite. - Business tools do not trigger version checks.
- The remote policy fields are
schema_version,latest,latest_beta,minimum_supported,blacklist, andmessage. required_upgrademeans the local AI must explain the reason, ask the user for approval, and only then run the appropriate upgrade command.- After any upgrade, the current session remains usable. Restart or reconnect only when the user wants
the new package loaded, then verify with
maker://statusormaker_status_lite.
Expected Effects
taptap-maker upgrade performs current-directory upgrade work:
- Materializes the exact package version as a stable self runtime and refreshes AI client MCP config to use its absolute Node and bundle paths.
--launcher npxis an explicit compatibility mode; it pins the exact package version and uses a dedicated writable npm cache instead of becoming the upgrade default.- User-level MCP config never contains a project
cwd; unchanged entries are not rewritten. --target-dironly selects the project whose managedAGENTS.mdpolicy is updated.- Updates the current project's TapTap Maker managed
AGENTS.mdpolicy block when the directory is bound to a Maker project. - Keeps user-written
AGENTS.mdcontent outside the managed block. - Writes only
<config>.taptap-maker.bak.latestwhen a client config actually changes. - Does not create timestamp config backups and does not delete old backups.
If Upgrade Appears Not To Take Effect
If maker://status still shows an old package, an unexpected project context, or missing Maker
proxy tools after restart/reconnect, first inspect MCP Roots and the tool call's target_dir. Also
check whether a legacy project-level MCP config is overriding user/global config.
Common project-level files include:
.mcp.json.codex/config.toml.codex/mcp.json.cursor/mcp.json.vscode/mcp.jsoncodex.toml
Do not migrate, delete, or edit these project-level files automatically. Explain the finding and ask the user whether they want to move Maker MCP configuration to user/global scope.
Old Project Handling
When a user upgrades MCP and later opens an old Maker project:
- Read
maker://statusfirst. - If the
AGENTS.mdsection reportsmissing_file,missing_block, oroutdated, run:
npx -y -p @taptap/maker@<TARGET_VERSION> taptap-maker agents update --target-dir <PROJECT_DIR>
- Tell the user the current session remains usable. The updated
AGENTS.mdinstructions load on the next MCP start or user-requested reconnect; do not require a new conversation.
Status reads are intentionally read-only. Do not modify AGENTS.md from maker://status or
maker_status_lite; us