What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: review pull requests.Similar tools
Listed for the same task: review pull requestsReviews
No review yet. Used Gluecron? Be the first to help others choose.What it does
Gluecron is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to one capability: code review. That makes it a candidate for tasks such as review pull requests or scan code for vulnerabilities.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)Hosted endpoint
https://gluecron.com/mcpstreamable-http
In Claude Code: claude mcp add --transport http gluecron https://gluecron.com/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"gluecron": {
"url": "https://gluecron.com/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 1d agoONLINE Gluecron answered an MCP connection on 13 Nov 2026 and introduced itself as gluecron 1.0 (MCP protocol 2025-06-18).
131 tools offered to AI assistants
merjax_repo_search· Search Merjax repositories by keyword (name + description), case-insensitively. Returns public repos plus any private repos owned by the authenticated caller. Default 20 per page, max 50; `total` is the full match count and `nextOffset` pagmerjax_repo_read_file· Read a single file from a repository at a given ref (branch / tag / commit). Private repos are readable when the authenticated caller has access. Returns the text content (binary files rejected).merjax_repo_list_issues· List open issues for a public repository. Returns up to 50 ordered by most-recent.merjax_repo_explain_codebase· Return the cached AI 'explain this codebase' Markdown for a public repo (most recent commit). Returns null when no cached explanation exists yet.merjax_repo_health· Compute the current health report for a public repo: overall score (0-100), letter grade, per-category breakdown (security/testing/complexity/dependencies/documentation/activity), and a list of insights to fix next. Backed by computeHealthSmerjax_create_issue· Create a new issue on a Merjax repository. Requires authenticated caller with write access on the target repo. Returns {number, url}.merjax_comment_issue· Add a comment to an existing issue. Requires authenticated caller with write access. Returns {commentId}.merjax_close_issue· Close an open issue. Requires authenticated caller with write access. Idempotent — closing an already-closed issue is a no-op. Returns {state}.merjax_reopen_issue· Reopen a previously closed issue. Requires authenticated caller with write access. Idempotent. Returns {state}.merjax_create_pr· Open a new pull request. `head_branch` is required; `base_branch` defaults to the repo default branch. Requires authenticated caller with write access. Returns {number, url}.merjax_get_pr· Fetch the full detail record of a pull request (title, body, state, branches, draft, author, timestamps), plus `mergeable` (true / false / null unknown) and `mergeState` from the same conflict probe the merge gate uses: status up-to-date |merjax_list_prs· List pull requests on a repo, filtered by state (open|closed|merged|all). Authenticated callers only. Returns up to 50 summary rows.
Show 88 more
merjax_comment_pr· Add a comment to a pull request. Requires authenticated caller with write access. Returns {commentId}.merjax_merge_pr· Merge an open PR. Enforces the same checks as the HTTP merge flow: not a draft, head SHA resolves, GateTest+AI-review hard gates pass, branch-protection rules satisfied. M3: soft-blocks when the pre-merge risk score is `critical` unless `comerjax_close_pr· Close an open pull request without merging. Requires authenticated caller with write access. Idempotent. Returns {state}.merjax_fork_repo· Fork a repository to the authenticated caller's namespace. Mirrors POST /:owner/:repo/fork. Returns {owner, repo, url}. Requires 'repo' scope.merjax_delete_repo· Delete a repository — a SOFT delete (2026-10-19): it disappears at once from git, web, REST, MCP, CI, webhooks, search and pages, its name stays reserved, and it can be restored with merjax_restore_repo until restorable_until (90 days by demerjax_update_repo· Update repository description / visibility / default_branch / automation dials / merge-conflict AI mode / GateTest switch. Requires 'admin' access on the repo (owner, org owners/admins, admin collaborators) and 'repo' scope. Returns {ok: trmerjax_search_repos· Search repositories by owner, name, owner/name or description, case-insensitively: every public repo, plus the private ones you own or collaborate on when authenticated. Omit `query` (authenticated) to list YOUR repositories — the ones youmerjax_whoami· Who this connector is on this Merjax instance: the signed-in username and email, whether that account is a site admin, the token's scopes, and how many repositories it owns or collaborates on. Call it first when a repository seems missing —merjax_clone_url· Return the authenticated HTTPS clone URL for a repo + a credential-helper hint. Use this instead of embedding tokens in URLs. Returns {url, owner, repo, defaultBranch, hint} using the repo's stored casing.merjax_create_deploy_token· Mint a short-lived, repository-scoped HTTPS clone credential (a deploy token) for a sandbox or CI box that has no PAT. By default it returns NO token: {id, exchangeUrl, exchangeExpiresAt, gitConfig, url}. Run the gitConfig lines right beformerjax_create_repo_token· Mint a fine-grained repository token (`gcft_…`) for ONE repository and return it once. It authenticates the REST API (/api/v2 and the GitHub-compatible /api/v3), git over HTTPS and the container registry (images under owner/repo, by contentmerjax_list_repo_tokens· List the fine-grained repository tokens you have minted (never the secret): repository, permissions, state (active / expired / revoked), expiry and last use. Needs 'repo' scope.merjax_revoke_repo_token· Revoke one of your fine-grained repository tokens by id (from merjax_list_repo_tokens). It stops working on its next use. Needs 'repo' scope. Audit-logged.merjax_list_tokens· List your own tokens (never a secret): type, name, status (active / expiring / expired / revoked / never_used / stale), last 4 characters, scopes or permissions, repository, expiry, last use (time, IP, client), use count and rotation state.merjax_get_token· One of your tokens by type and id (from merjax_list_tokens): everything list shows plus the audit trail (create, edits with a before/after diff, rotations, revocation). Never the secret. `type` is pat (personal access token, glc_), repo (remerjax_rotate_token· Rotate one of your tokens: mint a new secret with the same name, scopes / permissions, repository and expiry, returned ONCE as `token`. `grace_seconds` (default 0, max 604800 = 7 days) keeps the old secret working that long; 0 kills it now.merjax_revoke_token· Revoke one of your tokens by type and id. It stops working on its next use; this cannot be undone. `type` is pat (personal access token, glc_), repo (repository token, gcft_) or deploy (deploy token, gcdt_). PATs need 'admin' scope; repositmerjax_list_repo_secrets· List a repository's workflow secrets — NAMES ONLY, with created/updated times; values are never returned. Use it to check that a secret such as CRON_SECRET exists before a workflow needs it. Needs admin access to the repository and 'repo' smerjax_set_repo_secret· Create or replace one workflow secret on a repository, used in workflows as ${{ secrets.NAME }}. The name is saved upper-cased (cron_secret → CRON_SECRET); trailing spaces/newlines are removed from the value. The value is WRITE-ONLY: it ismerjax_delete_repo_secret· Delete one workflow secret from a repository by name (cron_secret is read as CRON_SECRET). Idempotent: deleting a secret that is already gone succeeds with deleted:false, already_deleted:true, so a retry is safe. Workflows that reference itmerjax_list_deleted_repos· List deleted repositories you can restore or purge: your personal ones and those of organizations you own (a site admin may pass all: true for the whole instance). Each has its id, full_name and restorable_until — after that date it is purgmerjax_restore_repo· Restore a deleted repository by id (from merjax_list_deleted_repos) before its restorable_until date: git data, LFS objects, issues, PRs, collaborators and webhooks come back exactly as they were. Cancelled CI runs stay cancelled and stoppemerjax_purge_repo· PERMANENTLY delete an already-deleted repository now, instead of waiting for its restore window to end. IRREVERSIBLE: the git data, LFS objects, issues, PRs, releases, packages, CI history and settings are removed and cannot be restored (damerjax_list_variables· List Actions configuration variables (${{ vars.NAME }}) with their values. Pass owner + repo for a repository variable, owner + repo + environment for an environment variable, or org for an organisation variable (organisation variables needmerjax_get_variable· Read one Actions variable by name. Pass owner + repo for a repository variable, owner + repo + environment for an environment variable, or org for an organisation variable (organisation variables need an admin-scoped token). Not found is anmerjax_set_variable· Create or replace an Actions variable (plain text, not for secrets — use merjax_set_repo_secret). Pass owner + repo for a repository variable, owner + repo + environment for an environment variable, or org for an organisation variable (orgamerjax_delete_variable· Delete an Actions variable by name. Pass owner + repo for a repository variable, owner + repo + environment for an environment variable, or org for an organisation variable (organisation variables need an admin-scoped token). A variable thamerjax_delete_branch· Delete a branch the way `git push --delete` would: write access, then branch protection (allow_deletion), rulesets and the push inspection apply; webhooks and CI fire. The default branch is never deleted. Pass expected_sha to delete only ifmerjax_edit_comment· Replace the text of a comment on an issue or pull request (by comment id). Its author or a repository writer only; the previous text is kept in the edit history; the same text again is `unchanged`; a concurrent edit is a conflict, never ovemerjax_delete_comment· Delete a comment on an issue or pull request (by comment id), with its edit history. Its author or a repository writer only. A missing comment is a not-found error, never reported as deleted. Mirrors DELETE /api/v3/repos/:o/:r/issues/commenmerjax_list_token_spend· Today's model spend (UTC day), the daily bucket in force and the state (active | suspended) of every personal access token of yours, as /settings/tokens/spend shows it. Canary tokens are not listed: they never authenticate. Needs `user` scomerjax_set_token_bucket· Set the daily model-spend bucket of one of your personal access tokens: daily_cents (1–1000000; 0 = the platform default; -1 = no bucket) or daily_usd ("2.50", "default", "none"). The call that would cross the bucket is refused and the tokemerjax_resume_token· Resume one of your personal access tokens that suspended itself (daily bucket spent, or the tripwire): it authenticates again; today's spend still counts against its bucket, so raise the bucket first with merjax_set_token_bucket if it is spmerjax_list_loop_secrets· List the secrets a hosted Claude loop (or an organisation) holds — names and dates, never values. Pass loop (the hosted Claude loop's id, from /connect/claude/deploy) for the loop's own secret — its owner only — or org (organisation slug, amerjax_set_loop_secret· Create or replace a secret a hosted Claude loop runs with (reaches it as process.env.NAME at invoke time only; sealed at rest, scrubbed from its logs). Pass loop (the hosted Claude loop's id, from /connect/claude/deploy) for the loop's ownmerjax_delete_loop_secret· Delete a hosted-loop (or organisation-level) secret by name. Pass loop (the hosted Claude loop's id, from /connect/claude/deploy) for the loop's own secret — its owner only — or org (organisation slug, admin-scoped token) for an organisatiomerjax_list_ai_workspaces· The three provider workspaces every model call is billed to by its purpose (ws-control-plane, ws-hosted-loops, ws-ci-gates): each with its daily spend limit, rate limit, today's spend and calls (UTC day), and the platform ceiling above allmerjax_set_ai_workspace_quota· Set a provider workspace's daily spend limit (cents, UTC day) and calls per minute; 0 = no cap at that level (the platform ceiling still applies). Site admins with an admin-scoped token only. Safe to retry: the same numbers again change notmerjax_press_kill_switch· Press the platform kill switch: pause every model call and suspend every personal access token minted or used in the last N hours (KILL_SWITCH_WINDOW_HOURS, default 24), platform-wide. Git, CI, merges and deploys are unaffected. One forensimerjax_undo_kill_switch· Undo the last kill switch press: give every token it suspended its previous expiry back and unpause AI (unless AI was already paused before the press, which stays as it was). A press already undone, or none at all, is a precondition failuremerjax_set_pr_ai_settings· Choose the model for a pull request's AI tasks (review, risk summary, CI fixes, conflict proposals): a model id from the catalog, or null / "" to inherit the repository's or the platform's choice. Write access to the repository. run_via ("smerjax_import_action· Site admins only (needs an 'admin'-scoped token). Import a third-party GitHub Action at ONE tag, branch or full commit SHA into the Merjax mirror namespace (gluecron-actions/<owner>--<repo>), so workflows that say `uses: owner/repo@ref` canmerjax_revoke_all_credentials· Site admins only (needs an 'admin'-scoped token). Revoke every browser session, personal access token (repository tokens included) and OAuth grant — for every user (scope 'platform') or for one (scope 'user' + username). Optionally force amerjax_backup_status· Site admins only (needs an 'admin'-scoped token). Backup and restore-drill health: whether the newest backup set is verified on an offsite target and how old it is, whether offsite copies are immutable (Object Lock), when a restore drill lamerjax_learning_status· Site admins only (needs an 'admin'-scoped token). Whether CI failures are being turned into lessons: classified failures, lesson.pattern events (matched to a docs/ops/CI_GATE_LESSONS.md row, or candidates), recurring candidates, and failuremerjax_security_ioc_hits· Site admins only (needs an 'admin'-scoped token). Campaign indicator-of-compromise hits: pushes, token uses and repositories that matched a reviewed signature in src/lib/security/campaign-iocs.json (e.g. the Gheist campaign: ci-sync-XXXXXXmerjax_label_issue· Attach one or more labels to an issue. Labels are created if they don't yet exist on the repo. Requires 'repo' scope. Returns {labels}.merjax_unlabel_issue· Detach a label from an issue. Idempotent. Requires 'repo' scope. Returns {removed: boolean}.merjax_assign_issue· Assign (or, with remove: true, unassign) users on an issue or pull request. Real assignees since 2026-10-12 — up to 10 per thread, only users who can read the repository; the old `assignee:<username>` labels were migrated. Pass `assignee` (merjax_search_issues· Search issues by title/body keyword on a single repo, filtered by state. Returns ranked rows.merjax_request_changes· Request changes on a PR. Records a 'changes requested' review by the caller, which holds the PR on every merge path (web button, API, MCP merge, merge queue, merge train, autopilot) until the caller approves or someone with write access dismerjax_dismiss_review· Dismiss the standing 'changes requested' reviews on a PR (all of them, or one reviewer's), so they no longer hold the merge. Requires 'repo' scope and write access; the reason is required and audited.merjax_search_prs· Search pull requests by title/body keyword on a repo.merjax_list_pr_comments· List every comment on a pull request in chronological order: general comments (kind `issue_comment`), inline review comments (`review_comment`: path, line, thread {id, inReplyToId, position, replies, resolved, resolvedAt, resolvedBy}) and rmerjax_open_draft_pr· Open a draft pull request. Same payload as merjax_create_pr but forces is_draft=true. Useful for AI-in-progress PRs that shouldn't run mergeability checks yet.merjax_set_pr_draft· Mark a pull request ready for review (draft=false) or convert it back to a draft (draft=true). Same rule as the web 'Ready for review' button: the caller needs write access and must be the PR author or the repository owner; only an open PRmerjax_generate_pr_description· Generate an AI commit-message-style description for a diff. Uses src/lib/ai-commit-message.ts under the hood; gracefully degrades to a heuristic when ANTHROPIC_API_KEY is missing. Returns {subject, body}.merjax_update_pr_branch· Bring a PR branch up to date with its base: merge the base into the head server-side (the PR page's 'Update branch'). Never a force-push — the new head is a merge commit moved through the push gates, so it gets CI. On conflict nothing changmerjax_list_pr_conflicts· What stands between a PR and a clean merge, as the merge gate, the PR page and the Conflicts tab see it (one shared probe): status up-to-date | clean | conflicts | unknown, `mergeable`, the base/head shas the answer is for, files settled wimerjax_resolve_pr_conflict· Save a resolution for ONE conflicted file of a PR, as a draft for the exact (base_sha, head_sha) pair merjax_list_pr_conflicts returned (a moved branch is refused: reload). Pass exactly one of: `content` (the whole resolved file — no conflimerjax_commit_pr_conflict_resolution· Commit the saved resolutions for a PR's conflicts ON THE PR HEAD as a two-parent merge commit (old head, base tip) — never on the base branch — moved through the push gates so CI runs on it before anything merges. Every unresolved file needmerjax_list_ready_to_merge· Pull requests that are green and clean and that nobody has merged: open, not a draft, CI green at the head, no gate failing or running, no standing request for changes, branch protection satisfied, no conflicts (the merge gate's own conflicmerjax_repo_rating· The repository's letter rating A+/A/B/C/D/F — the health report's grade (the same number merjax_repo_health and the /health page show; A is 85+) — with the score, the six categories (score, weight, points still available), `to_a`: the ordermerjax_propose_pr_conflict_resolution· Ask AI (Opus 5.5) to PROPOSE a resolution for each conflict block of a PR's text files — the Conflicts tab's 'Propose resolutions' button. Nothing is committed: each proposal (the block's lines, an explanation, a confidence 0..1) is storedmerjax_update_pr· Edit a pull request's title, body, base branch and/or draft state. Title / body / base: the PR's author or anyone with write access; draft: the same rule as merjax_set_pr_draft (write access and the PR author or repo owner; marking ready stmerjax_set_auto_merge· Arm (enabled: true) or disarm (enabled: false) auto-merge on one PR: it merges by itself through the full gated merge chain (CI, required checks, branch protection, CODEOWNERS, risk) once CI and every required check are green and no reviewemerjax_get_pr_checks· List every check at a PR's current head — workflow runs, gates and commit statuses — with status, conclusion, whether branch protection requires it, and the run's log URL; plus each required check's state (passing / pending / failing / missmerjax_rerun_failed_jobs· Re-run a failed or cancelled workflow run at the SAME commit (same inputs, same PR merge preview) — the run page's Re-run. Merjax re-runs every job of the run (per-job re-run does not exist yet); a successful or still-running run is refusedmerjax_get_branch_protection· Read the branch-protection rule that applies to a branch (exact name or the glob that covers it): required checks, require_pr_run, required approvals, AI / human review, green gates, force-push / deletion, auto-merge; plus `merge_train` {onmerjax_set_branch_protection· Set branch protection for one branch (partial update: fields you omit keep their value). Edits the rule named exactly after the branch; when only a glob rule covers it, a new exact rule is created seeded from the glob's settings and checks.merjax_approve_pr· Approve a pull request: records an 'approved' review by the caller — the same review the web form and POST /api/v2/repos/:owner/:repo/pulls/:number/reviews write, so it counts toward branch protection's required approvals and clears the calmerjax_read_file· Read a file from a repo at a given ref. Mirrors GET /api/v2/repos/:owner/:repo/contents/:path. Returns {path, size, content, encoding, totalLines}. Pass `start_line` / `end_line` (1-based, inclusive) to read only part of a text file. A textmerjax_write_file· Create or update a file on a branch via git plumbing. Wraps `createOrUpdateFileOnBranch`. Pass `content` as a UTF-8 string OR `content_base64` for binary. Meets the same branch protection, rulesets and secret scan as a git push, and fires Cmerjax_delete_file· Delete a file from a branch via git plumbing. Requires the existing blob sha (optimistic concurrency) and 'repo' scope. Meets the same branch protection, rulesets and secret scan as a git push, and fires CI/webhooks like one. Mirrors DELETEmerjax_list_tree· List directory contents at a ref. `path` scopes the listing to a subtree and is honoured in BOTH modes; `recursive: true` walks the whole subtree instead of one level. Always returns the same shape: {path, ref, recursive, entries, truncatedmerjax_get_commit· Fetch a single commit by SHA: metadata plus the list of files it changed (path, status, additions, deletions). Mirrors GET /api/v2/repos/.../commits/:sha. Patch bodies are NOT included — use merjax_get_diff for those.merjax_get_diff· Read the actual changes in a commit or a branch range. Pass `sha` for one commit against its first parent, or `base`+`head` for everything head adds since the merge base (what a PR proposes). Returns {files:[{path, oldPath?, status, additiomerjax_create_branch· Create a new branch ref pointing at an existing sha. Mirrors POST /api/v2/repos/.../git/refs. Gated like a push of the new branch (rulesets, secret scan of commits no other ref reaches) and fires CI/webhooks. Requires 'repo' scope. Returnsmerjax_atomic_multi_file_commit· Apply a set of file writes + deletes as a single atomic commit on a branch (creates the branch if it doesn't exist). The killer agent tool: blob/tree/commit/ref-update sequence. Each change is `{path, content?, content_base64?, deleted?}`.merjax_apply_patch· Commit a patch to a branch without sending whole files — the way to change a few lines of a large file. `patch` is a unified diff as `git diff` prints it (one commit, `message` required) OR `git format-patch` mbox output (each patch becomesmerjax_ship_spec· Drop a spec file in .gluecron/specs/ with status: ready so the autopilot picks it up. Wraps voice-to-pr.shipAsSpec — handle both voice + manual specs. Requires 'repo' scope.merjax_voice_to_pr· Interpret a free-form voice transcript and either ship it as a spec or create an issue (caller picks via `as`). Wraps src/lib/voice-to-pr.ts. Requires 'repo' scope.merjax_refactor_across_repos· Plan + execute a refactor that spans multiple repos owned by the caller. Wraps src/lib/multi-repo-refactor.ts. `dry_run: true` returns the plan only. Requires 'repo' scope.merjax_explain_repo· Return the cached AI 'explain this codebase' Markdown for a repo. Pure read — never triggers a new generation (use the web UI for that).merjax_chat_with_repo· Start a new chat with a repo: creates a chat row, sends the first user message, streams + persists the assistant reply. Returns {chat_id, reply}. If the AI service does not answer this fails with a JSON-RPC error carrying {chat_id, ai_errormerjax_chat_continue· Send another message to an existing repo chat. Returns the assistant's reply. If the AI service does not answer this fails with a JSON-RPC error carrying {chat_id, ai_error} rather than returning apology copy as a reply.merjax_generate_tests· Generate tests for a PR via Claude. Wraps src/lib/ai-test-generator.generateTestsForPr. Mode 'follow-up-pr' opens a new PR; 'append-commit' commits onto the head branch. Requires 'repo' scope.merjax_generate_commit_message· Generate a commit message for a diff. Same engine as merjax_generate_pr_description but explicit for the commit-message use case.
The first 100 are shown.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://gluecron.com/mcp | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Website | https://gluecron.com | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| Version | 1.0.0 | DECLARED | SRC-001 Official MCP Registry | 5d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 5d ago |
Change history
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Gluecron still online?
Free alerts · no account▲ 0Do you run Gluecron? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Gluecron
How do I connect Gluecron?
Use the hosted endpoint https://gluecron.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Gluecron offer?
When Electra Index connected on 13 Nov 2026, it listed 131 tools: merjax_repo_search, merjax_repo_read_file, merjax_repo_list_issues, merjax_repo_explain_codebase, merjax_repo_health, merjax_create_issue, merjax_comment_issue, merjax_close_issue and more. The full list is in "Live check" above.
Is Gluecron online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.
What can I use Gluecron for?
Based on its description, it is most relevant to: review pull requests, scan code for vulnerabilities, migrate a codebase to a new framework, write technical documentation.