widescreen-research: Command for Claude Code

/mcp-server-implementation-game

Implement and validate a new MCP server end-to-end with instrumentation, registry integration, and a first-class dogfooding workflow that exercises every exposed capability through the agent.

Usage

/mcp-server-implementation-game $ARGUMENTS [ship_deadline] [risk_level] [transport] [registry_visibility]

Arguments

• $ARGUMENTS (required): High-information server specification (PRD/RFC/URL/brief); see Variables
• ship_deadline (optional): ISO 8601 deadline (default: 1 week from now)
• risk_level (optional): "low" | "medium" | "high" (default: "medium")
• transport (optional): "stdio" | "shttp" (default: "stdio")
• registry_visibility (optional): "local" | "team" | "public" (default: "local")

Variables

• SPEC_DOCUMENT: $ARGUMENTS (prewritten specification document)
  • Must include: tool/resource schemas, prompts/models (if any), auth/secret handling, error taxonomy, retries/timeouts, perf goals, observability, rollout
• SERVER_ID: derived from spec first line, slugged
• TRANSPORT: stdio/shttp per argument
• REGISTRY: where to register (local/team/public)

Algorithm

Phase 0: Initialize Server Game Space

mkdir -p .mcp-server-game/{state,artifacts,checks,logs}

cat > .mcp-server-game/state.json << EOF
{
  "server_id": "$SERVER_ID",
  "transport": "$TRANSPORT",
  "registry_visibility": "$REGISTRY",
  "deadline": "$SHIP_DEADLINE",
  "risk_level": "$RISK_LEVEL",
  "phase": 0,
  "budgets": { "error_budget": 0.02, "p95_latency_ms": 250 },
  "instrumentation": { "metrics": true, "events": true, "traces": true },
  "connectivity": { "configured": false, "verified": false },
  "dogfood": { "planned": false, "executed": false, "results_path": null }
}
EOF

# Persist raw spec
cat > .mcp-server-game/spec.raw.txt << 'EOF'
$ARGUMENTS
EOF

Phase 1: Readiness Gate (Spec-Provided Contracts)

cat > .mcp-server-game/checks/readiness.json << 'EOF'
{
  "contracts": [
    "Spec provides tool schemas (names, params, result types)",
    "Spec provides resource schemas (uris, mime types, metadata)",
    "Spec provides error taxonomy + retry/timeout strategy",
    "Spec documents auth/secret handling",
    "Transport selected (stdio/shttp) with bootstrap",
    "Observability plan (metrics/events/traces) present in spec"
  ],
  "registry": [
    "Server metadata prepared for registry",
    "Visibility chosen (local/team/public)"
  ]
}
EOF

echo "✅ Readiness checklist created"