Add server.json and the mcp-name marker for the official MCP registry

[arpanghoshal]

Prepares ctrlrun mcp-operator for listing in the official MCP registry at registry.modelcontextprotocol.io. It does not publish anything; it makes the next release publishable.

What this adds

• server.json at the repo root, against the 2025-12-11 schema, naming the server io.github.ctrlrun/ctrlrun-mcp-operator. The package is the PyPI ctrlrun distribution, the positional argument is mcp-operator, and the transport is streamable-http at the loopback default http://127.0.0.1:8901/mcp, which is what SPEC-mcp-operator §2.1 already fixes.
• One HTML comment at the end of README.md carrying mcp-name: io.github.ctrlrun/ctrlrun-mcp-operator.

Why the README line is load-bearing

The registry verifies namespace ownership for PyPI packages by looking for an mcp-name: token in the package's long description, which is this README. I checked the live 0.12.1 description: 26,223 characters, no marker. So a publish attempted today fails ownership verification.

The ordering is therefore: merge this, cut a release so PyPI carries a description with the marker, then publish. Publishing before a marked release is on PyPI cannot succeed.

Two things to decide

1. Version fields. server.json says 0.12.1 in both places, matching the current release. They must name whichever release first carries the marker, so if the next tag is 0.13.0 both fields move with it.
2. Namespace. io.github.ctrlrun/* authenticates through GitHub and needs nothing else. The alternative is dev.ctrlrun/mcp-operator, which authenticates by a DNS TXT record on a domain already on Cloudflare and reads as the project rather than as a GitHub account. Changing it later means republishing under a new name, so it is cheaper to decide now.

Checks

Full suite: 4136 passed, 374 skipped. tests/test_readme_assets.py passes unchanged, including the header copy pins, since the marker sits below the last section and is a comment rather than prose.

Summary by CodeRabbit

• Documentation
  • Added MCP metadata identifying the CTRLRun Operator package.
  • Added server metadata describing its identity, documentation, repository, version, package configuration, and streamable HTTP endpoint.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 19d850c3-d542-41f8-b3c4-e8b408aa6cc9

📥 Commits

Reviewing files that changed from the base of the PR and between d0c5661 and 02b4e53.

📒 Files selected for processing (2)

• README.md
• server.json

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull request adds MCP package metadata to README.md and a server.json manifest for CTRLRun Operator version 0.12.1.

Changes

MCP metadata

Layer / File(s)	Summary
MCP package and server metadata README.md, server.json	README.md identifies the package as io.github.ctrlrun/ctrlrun-mcp-operator. server.json defines package version 0.12.1, PyPI installation settings, loopback streamable HTTP transport, and the mcp-operator argument.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 02b4e

No concrete metadata or launch-contract defect remains; the PR is ready for normal merge checks.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the two primary changes: adding server.json and the mcp-name marker for the official MCP registry.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch add-mcp-registry

---

_{Comment @coderabbitai help to get the list of available commands.}