mcp-config-ops

スター9

フォーク3

更新日2026年3月6日 14:02

Use when installing or repairing Claude Desktop or Claude Code MCP config, checking status, backing up config files, or fixing config drift in openrouter-mcp

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

physics91

physics91/openrouter-mcp

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Mcp Config Ops

Overview

Use this skill when a task touches MCP client configuration rather than core model behavior. It standardizes status checks, backup discipline, installer flows, and config-drift troubleshooting for the repository's Node-to-Python bootstrap path.

Repository Touchpoints

bin/openrouter-mcp.js
src/openrouter_mcp/cli/mcp_manager.py
src/openrouter_mcp/cli/commands.py
src/openrouter_mcp/server.py
docs/CLAUDE_DESKTOP_GUIDE.md
docs/CLAUDE_CODE_GUIDE.md
docs/INSTALLATION.md

Standard Workflow

Inspect the current state:
```
node bin/openrouter-mcp.js status
```
Identify the target client:
- Claude Desktop
- Claude Code
- both
Back up any config file before mutation.

Apply one installer or repair action at a time:

node bin/openrouter-mcp.js install-claude
node bin/openrouter-mcp.js install-claude-code

Re-run status and inspect the written config path.
If documentation changed, verify that package names and command examples still match the actual CLI path.

Backup And Restore Rules

Never overwrite a user config file without first capturing a backup path.
If the installer already creates backups, record where they are.
If an install or migration goes wrong, restore the backup before trying a second fix path.

Consistency Checks

Check command examples against the actual package scope:

rg -n "@physics91/openrouter-mcp|openrouter-mcp" README.md docs

Watch for drift between install docs and actual CLI behavior.
Treat Node/Python bootstrap issues as part of config operations when they block installation or status checks.

Recovery Pattern

If config drift or install failure is reported:

Capture the failing path and command.
Compare generated config with the documented expected shape.
Restore backup if the generated output is clearly wrong.
Re-run a single installer path.
Finish by running status again.

Done Definition

The target integration was inspected or updated intentionally.
Backup or restore handling was explicit.
The final status output was reviewed.
Any package-name or doc-command mismatch was surfaced.

このリポジトリの他の Skills

同じリポジトリ

deploy

physics91/openrouter-mcp

Use when publishing or releasing openrouter-mcp to npm, or preparing a version for distribution with metadata and release checks

2026-03-069

resilience-policy

physics91/openrouter-mcp

Use when changing concurrency limits, quota rules, circuit breakers, cleanup behavior, or other high-risk resilience policies in the collective-intelligence paths

2026-03-069

security-ops

physics91/openrouter-mcp

Use when handling API key setup, credential rotation or deletion, security-audit runs, shared-environment risk checks, or security-document hygiene in openrouter-mcp

2026-03-069

test

physics91/openrouter-mcp

Use when running tests, reproducing the repository's assurance gate locally, checking failures, or verifying coverage for openrouter-mcp

2026-03-069

build

physics91/openrouter-mcp

Use when checking code quality, running linting, formatting code, or verifying static analysis gates before PR or publish.

2026-03-039

git-worktree

physics91/openrouter-mcp

Use when the user asks to continue with additional tasks while keeping current work in progress, or needs parallel branch development, hotfix interruption handling, and review sandboxes without extra clones. Use when tasks involve `git worktree add/list/remove/prune/lock/repair`, resolving branch-in-use conflicts across worktrees, configuring per-worktree settings (`git config --worktree`, `extensions.worktreeConfig`), or writing scripts that must resolve worktree paths safely with `git rev-parse`.

2026-03-039

Mcp Config Ops

Overview

Repository Touchpoints

bin/openrouter-mcp.js

src/openrouter_mcp/cli/mcp_manager.py

src/openrouter_mcp/cli/commands.py

src/openrouter_mcp/server.py

docs/CLAUDE_DESKTOP_GUIDE.md

docs/CLAUDE_CODE_GUIDE.md

docs/INSTALLATION.md

Standard Workflow

Inspect the current state:

node bin/openrouter-mcp.js status

Identify the target client:

Claude Desktop
Claude Code
both

Back up any config file before mutation.

Apply one installer or repair action at a time:

node bin/openrouter-mcp.js install-claude
node bin/openrouter-mcp.js install-claude-code

Re-run status and inspect the written config path.

If documentation changed, verify that package names and command examples still match the actual CLI path.

Backup And Restore Rules

Never overwrite a user config file without first capturing a backup path.

If the installer already creates backups, record where they are.

If an install or migration goes wrong, restore the backup before trying a second fix path.

Consistency Checks

Check command examples against the actual package scope:

rg -n "@physics91/openrouter-mcp|openrouter-mcp" README.md docs

Watch for drift between install docs and actual CLI behavior.

Treat Node/Python bootstrap issues as part of config operations when they block installation or status checks.

Recovery Pattern

If config drift or install failure is reported:

Capture the failing path and command.

Compare generated config with the documented expected shape.

Restore backup if the generated output is clearly wrong.

Re-run a single installer path.

Finish by running status again.

Done Definition

The target integration was inspected or updated intentionally.

Backup or restore handling was explicit.

The final status output was reviewed.

Any package-name or doc-command mismatch was surfaced.

name	mcp-config-ops
description	Use when installing or repairing Claude Desktop or Claude Code MCP config, checking status, backing up config files, or fixing config drift in openrouter-mcp