support-support-mcp-registry-steward

Inventories MCP servers and tools across Claude and Codex runtimes and maintains auditable registration records.

2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/30eggis/walwal-harness --skill support-support-mcp-registry-steward-30eggis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: support-support-mcp-registry-steward
Source: https://github.com/30eggis/walwal-harness/tree/main/HR-Resource/support-support-mcp-registry-steward
Command: npx skills add https://github.com/30eggis/walwal-harness --skill support-support-mcp-registry-steward-30eggis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams using Claude and Codex often lack a clear picture of which MCP servers and tools are actually available in each runtime, leading to invented capabilities, unsafe registrations, and lost configuration decisions. ## Core Features & Use Cases - Runtime Capability Inventory: Discovers MCP servers, tools, and connector mechanisms actually exposed in the active Claude or Codex runtime, recording server names, commands, args, and required environment variables. - Registration Risk Review: Documents purpose, credentials, read/write risk, validation commands, and rollback procedures for every proposed MCP registration. - Auditable Maintenance Records: Writes a structured worker report under .harness/documents/{mission}/coo/workers/ with inventory, risk review, and maintenance plan sections. - Use Case: Before a mission that needs Playwright MCP, run this Skill to verify whether the project already references it, confirm setup instructions exist, and record whether it is Claude-only or also available to Codex. ## Quick Start Ask the agent to inventory all MCP servers and tools available in the current Claude and Codex runtimes and write the capability record for this mission.

Frequently Asked Questions about support-support-mcp-registry-steward

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I inventory available MCP servers in Claude and Codex?▼

Use only the discovery mechanisms exposed in the active runtime, such as MCP tool namespaces in Claude sessions or connector/tool search in Codex. Record each server name, command, args, and required environment variables, and mark tools as read-only or write-capable.

Are MCP tools configured for Claude also available in Codex?▼

No. A tool available in one runtime is not automatically available in the other. Claude MCP configuration under `.claude` does not apply to Codex, so a Claude MCP must be marked Claude-only until Codex registration is confirmed.

What should be documented before registering a new MCP server?▼

Document the purpose and mission fit, target runtime (Claude, Codex, or both), required credentials and environment variables, read/write risk and blast radius, a validation command or smoke test, and a rollback or disable procedure.

Can this Skill edit global Claude or Codex MCP configuration?▼

No. It never edits global Claude, Codex, or user-level MCP configuration without explicit Owner approval. It prefers project-local documentation and registration instructions over hidden global state.

What happens when no MCP discovery mechanism is available?▼

The Skill records `None` with the exact reason instead of guessing. It never invents MCP servers, tools, connector names, credentials, or config paths, and every claim must include exact evidence paths or tool names.