Onboarding request: mcp‑graphql‑enhanced — reliable GraphQL introspection for GitHub GraphQL API

[letoribo]

Hello maintainers,

I would like to request onboarding of my MCP server io.github.letoribo/mcp-graphql-enhanced into the GitHub MCP Registry.

🔍 Comparative testing

• Apollo MCP Server v1.17.0 (also tested v1.8.1‑amd64): configuration remains complex, introspection repeatedly hangs (4+ minutes) on both Query and Repository types at depth 1, with no output.
• blurrah/mcp‑graphql: baseline GraphQL MCP implementation, but lacks scoped introspection and adaptive fallback.
• mcp‑graphql‑enhanced: scoped introspection (typeNames + typeDepth) succeeds instantly. For example, Repository at typeDepth: 1 returns the full SDL promptly, bounded and synchronous, without timeout.

Server / Test Case	Manifest / Topology Check	Full Introspection (GitHub schema)	Scoped Introspection (Repository, depth=1)
Apollo MCP Server v1.17.0 (also v1.8.1)	❌ N/A (no cheap option)	❌ hangs >4 min, no output	❌ hangs >4 min, no output
blurrah/mcp‑graphql	❌ N/A (no cheap option)	❌ failed — exceeded 1MB transport	❌ not possible — no params
mcp‑graphql‑enhanced	✅ succeeded — bounded manifest	N/A (predictably too large, not attempted)	✅ succeeded — complete usable SDL

🔗 Shared Chat Logs

• Apollo MCP comparison: claude.ai/share/8fae1b8a-6f03-4cdb-9eac-cff53e741ade
• blurrah/mcp‑graphql comparison: claude.ai/share/5b845f72-809a-42ee-8083-361314126069
• mcp‑graphql‑enhanced successful introspection: attached shared chat logs

💡 Why it matters

• Bounded introspection: avoids hangs by scoping requests.
• Adaptive fallback: if a request is too heavy, the server automatically switches to lighter arguments instead of stalling.
• Reliability: synchronous responses even on large schemas (e.g. GitHub GraphQL API).

📦 Release info

• Latest release: v4.13.3 — Official MCP Registry Support
• Repo: github.com/letoribo/mcp-graphql-enhanced
• License: MIT

I believe this server fills a critical gap for developers and enterprises working with GitHub GraphQL APIs, and I’d be grateful if it could be onboarded into the GitHub MCP Registry.

Thank you!
— @letoribo

[letoribo]

Happy to provide additional diagnostic logs or live test outputs if needed.
Open to feedback and ready to adjust the server for Registry requirements.
Thanks for reviewing!