Add glama.json naming the listing maintainer

[arpanghoshal]

Lets the Glama listing for this server be claimed.

ctrlrun-mcp-operator is already listed on glama.ai, marked Official, categorised Security and Developer Tools, and rated B for maintenance. Nobody has claimed it, so the profile, the Docker build spec and the analytics are all read-only to us.

Glama offers two claim routes. Signing in as the account that owns the repository does not apply: CTRLRun is an Organization, not a user. The other route is this file, a glama.json at the repository root listing GitHub usernames under maintainers, recognised on their next sync.

Why it is worth claiming

The Docker build spec is the part that matters. Glama only indexes servers for search once a container build passes their safety and quality checks, and the build spec can only be configured by a maintainer. Claiming is also what allows the listing's name and description to be edited, so the directory says what we would say rather than what a crawler inferred.

Not a dependency of anything currently open

The score badge is keyed on the repository, CTRLRun/ctrlrun, not on the listing name, so it already renders and is already carried in the awesome-mcp-servers entry. Claiming does not change that URL, and renaming the listing later would not break it either.

Checks

Full suite: 4137 passed, 374 skipped. The file is inert at runtime; it is read by Glama, never by this package.

Summary by CodeRabbit

• New Features
  • Added Glama MCP server metadata and schema information.
  • Identified the project maintainer in the published metadata.

[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: 8e9e1573-728b-4e55-9604-daddbe091a83

📥 Commits

Reviewing files that changed from the base of the PR and between 80405d6 and 32894a2.

📒 Files selected for processing (1)

• glama.json

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

---

📝 Walkthrough

Walkthrough

The pull request adds glama.json with Glama MCP server metadata. The file specifies the schema URL and arpanghoshal as the maintainer.

Changes

Glama MCP Metadata

Layer / File(s)	Summary
Glama metadata registration glama.json	Adds the Glama MCP server schema URL and arpanghoshal as the maintainer.

Priority: ⬇️ Low

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

Change: Other

Merge Risk: ⚪ Minimal · up to 32894

The change only adds Glama metadata and is ready to merge.

🚥 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 main change: adding glama.json to identify the Glama listing maintainer.
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-glama-maintainers

---

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