Gluecron
Server Details
AI-native git hosting — repos, PRs, issues, CI gates, and AI code review over MCP (60 tools).
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 131 tools
Several tools do the same thing with no stated distinction: merjax_read_file vs merjax_repo_read_file, merjax_explain_repo vs merjax_repo_explain_codebase, merjax_search_repos vs merjax_repo_search, and merjax_generate_commit_message which is explicitly 'the same engine' as merjax_generate_pr_description. Beyond those duplicates, PR-state tools overlap heavily (merjax_get_pr, merjax_get_pr_checks, merjax_pr_status_summary, merjax_list_pr_conflicts, merjax_get_diff all return overlapping conflict/CI blocks), so an agent will routinely misselect.
All names share the merjax_ prefix and snake_case, which is good, but the verb/noun ordering is mixed (read_file / repo_read_file, list_prs / repo_list_issues, explain_repo / repo_explain_codebase) and noun-only names like whoami, handover, repo_health and repo_rating break the pattern. Legible, but the duplicated orderings make the convention unpredictable rather than rule-driven.
131 tools in a single MCP server for one platform is an extreme mismatch — far past the 50+ threshold where an agent can meaningfully survey the surface. Many are admin/niche one-offs (kill switch, backup drill status, IOC hits, workspace quotas) that dilute the core repo/PR/CI workflow tools.
Coverage is very broad: full repo/PR/issue lifecycle, CI runs and logs, secrets, variables, tokens, leases, sandboxes, merge train and admin security operations — few obvious dead ends. Minor gaps (no per-job CI re-run, no PR review-comment creation distinct from merjax_comment_pr) are acknowledged in the descriptions and can be worked around.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
GitHub Copilot MCP: code, repo, PR, workflow tools for AI assistants.
Software factory for AI agents: issue and PR reviews, auto-fixes, stacked PRs and a merge queue.
Git collaboration for AI agents and people: tasks, hand-offs, reviews, teams, shared memory.
Team memory for AI coding agents and code reviews, reviewed by humans and served over MCP.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables automated AI-powered code review for pull requests across GitHub, GitLab, Bitbucket, and Azure DevOps via webhooks, and manual code review through MCP tools using Groq, Claude, or GPT-4.1-
- AlicenseNot gradedqualityBmaintenanceEnables AI tools to drive role-aware Git collaboration through nine MCP tools, including starting tasks, staging/committing/pushing changes, submitting pull requests with GitHub-native auto-merge, checking status, syncing, and listing team rosters.MIT

ThinkReview MCPofficial
AlicenseNot gradedqualityCmaintenanceHosted MCP server that enables AI code reviews on GitHub, GitLab, Azure DevOps, and Bitbucket PR/MR URLs via a single tool (review_url_code), integrating with Cursor, Claude Code, Claude Desktop, and GitHub Copilot through OAuth or Bearer token authentication.1MIT- AlicenseNot gradedqualityCmaintenanceA secure and scalable Git MCP server giving AI agents powerful version control for local and (soon) serverless environments.Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.