chore(glama): declare maintainer so the catalog entry can be claimed

[FROWNINGdev]

glama.ai lists our MCP server, but the page still shows a Claim button — the entry is unowned. That means catalog metadata cannot be corrected and build-failure notifications have no verified recipient.

Their schema (https://glama.ai/mcp/schemas/server.json, draft-07) requires exactly one field: maintainers, a list of GitHub usernames permitted to maintain the server.

This sits alongside the manifests other catalogs already read — smithery.yaml for Smithery, cli/server.json for the MCP Registry.

Why now

Glama sent a build-failure notice. Everything reproducible on our side is healthy:

• docker build . from the repo root succeeds; django-orm-lens 1.12.0 installs from PyPI.
• The resulting image answers the MCP initialize handshake over stdio, protocol 2024-11-05.
• stdout carries JSON-RPC only — the readiness banner correctly goes to stderr.
• The published ghcr.io/frowningdev/django-orm-lens:latest behaves identically.

So this PR claims the listing; it is not itself the build fix. The build log lives behind the Glama account and is needed before anything else can be diagnosed.

Summary by CodeRabbit

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

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 7b79e737-7f40-4f1d-a95b-fb8a4cb09f5c

📥 Commits

Reviewing files that changed from the base of the PR and between 0b474b9 and c820659.

📒 Files selected for processing (1)

• glama.json

---

📝 Walkthrough

Walkthrough

The pull request adds glama.json with the Glama MCP server schema URL and FROWNINGdev as maintainer.

Changes

Glama MCP metadata

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

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

Merge Risk: ⚪ Minimal · up to c8206

This is a localized catalog metadata change that declares a maintainer for the Glama listing; no actionable merge-blocking risk remains beyond normal checks and review.

🚥 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 describes the main change: declaring a Glama maintainer so the catalog entry can be claimed.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/glama-maintainers

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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