agentsclimarketplace

Mcp operations

Skill hoangsonww/Claude-Code-Agent-Monitor/.claude/skills/mcp-operations

Operate and maintain the local MCP server for this project. Use when creating MCP host config, troubleshooting tool connectivity, modifying tool domains, or adjusting safety policy flags.From its SKILL.md

Install
npx -y skills add hoangsonww/Claude-Code-Agent-Monitor --skill mcp-operations

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.2 KB, as published. Nobody here has run it

MCP Operations

Use this skill whenever work touches mcp/ behavior or MCP host integration.

Core workflow

  • Confirm dashboard API is running (/api/health).
  • Confirm MCP server build status.
  • Validate env flags for mutation/destructive modes.
  • Verify host configuration path and command.

Safe operations policy

  • Default to read-only mode (MCP_DASHBOARD_ALLOW_MUTATIONS=false).
  • Enable mutations only for explicit admin tasks.
  • Enable destructive mode only transiently and require explicit confirmation token.

Required verification for code changes

  • npm run mcp:typecheck
  • npm run test:mcp
  • npm run mcp:build

Catalog invariant

  • Add tools only through mcp/src/tools/domains/ and registerAllTools.
  • Protocol transports and REPL must use the same declarations and schemas.
  • Update .agents/skills/mcp-maintainer/references/tool-domain-map.md when a domain changes.

References

  • Host config examples: references/host-config.md
  • Operations runbook: references/runbook.md

What ships with it: 2 files

945 B alongside SKILL.md

references/

Gives 0 of the 12 instructions most mcp tooling skills give

Counted across 780 of the 1,136 authors here whose files we hold, read 2026-09-06

  • Use Zod for input validationin 34 of 780, across 21 files
  • Use stdio for local clientsin 27 of 780, across 10 files
  • Restart Claude Code after configurationin 26 of 780, across 23 files
  • Verify MCP server connection before using toolsin 23 of 780, across 17 files
  • Define input schemas for every toolin 20 of 780, across 11 files
  • Use Streamable HTTP for remote clientsin 18 of 780, across 8 files
  • Pin SDK version in package.jsonin 17 of 780, across 6 files
  • Keep server logic independent of transportin 16 of 780, across 6 files
  • Verify SDK methods against official documentationin 15 of 780, across 5 files
  • Format evaluation results as an XML filein 15 of 780, across 12 files
  • Test servers using the MCP Inspectorin 15 of 780, across 14 files
  • Create ten complex and independent evaluation questionsin 14 of 780, across 11 files

Said here and by no other author read

  • Confirm dashboard API health
  • Validate environment flags
  • Verify host configuration path
  • Enable mutations only for admin tasks
  • Enable destructive mode only transiently
  • Update tool domain map on changes

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 613,373. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.