Add Latchkey MCP server to Official CI/CD and GitOps MCP Servers

[that-developer-kaveh]

Adds the Latchkey MCP server to Official CI/CD and GitOps MCP Servers (data/repos.yaml + README row), type: hosted-mcp-server like the GitLab and Atlassian entries, and runs sync_readme_counts.py.

• Use case: GitHub Actions failure triage for coding agents — failure bundles (root cause, failing file, scrubbed logs) for runs the self-healing runner could not fix, run status, log tails, workflow dispatch, one-off commands on fresh ephemeral runners.
• Action level: write-capable (dispatch_workflow, run_job); no built-in human-approval gate, so human_approval: false and no approval label. Safety model: per-workspace API keys with jobs:read / jobs:run scopes and a per-key switch for running jobs; secret-scrubbed logs; the server never edits repository code (durable fixes arrive as PRs for human review).
• Evidence: partial — every self-heal intervention is recorded, jobs appear as their own cost line; no full trajectory replay.
• Commercial-only, hosted; no OSS form of the server (disclosed). Descriptor: https://latchkey.dev/.well-known/mcp/manifest.json.

Disclosure: I'm a co-founder of Latchkey.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TXkS5Njggof4RSVoT4vFpu

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud