MCP server
Gluecron ships a Model Context Protocol (MCP) server at POST /mcp. Add it to Claude Code and you can create issues, open PRs, merge pull requests, and more — all from an AI session, with full gate enforcement on every write.
1. Install Claude Code
If you don't have Claude Code yet, install it from claude.ai/code or via npm:
npm install -g @anthropic-ai/claude-code2. Generate a personal access token
MCP write tools require authentication. Create a token at /settings/tokens — choose the admin scope so merge and close operations are allowed. The token is shown once; copy it immediately. Tokens start with glc_.
3. Add the MCP config
Add the Gluecron server to your Claude Code .claude/settings.json (or the global~/.claude/settings.json):
{
"mcpServers": {
"gluecron": {
"type": "http",
"url": "https://gluecron.com/mcp",
"headers": {
"Authorization": "Bearer glc_your_token_here"
}
}
}
}If you self-host Gluecron, replace gluecron.com with your instance URL.
Alternatively, one-click setup is available at /connect/claude — it generates the JSON snippet with your token pre-filled.
4. Verify the connection
Start Claude Code in your project directory:
claude
# In the session, ask:
# "List open PRs on my-org/my-repo"
# Claude will call gluecron_list_prs and return the results.Available tools
The MCP server exposes the following tools. Read-only tools work without authentication; write tools require a token with the appropriate scope.
Read-only tools
| Tool | Description |
|---|---|
gluecron_repo_search | Search public repos by keyword. Returns up to 20 results. |
gluecron_repo_read_file | Read a single file from a public repo at a given ref (branch / tag / commit). |
gluecron_repo_list_issues | List open issues for a public repo. Returns up to 50 ordered by most-recent. |
gluecron_repo_explain_codebase | Return the cached AI "explain this codebase" Markdown for a public repo. |
gluecron_repo_health | Compute the health report for a public repo: overall score (0-100), letter grade, per-category breakdown, and actionable insights. |
Write tools (require auth)
| Tool | Description |
|---|---|
gluecron_create_issue | Create a new issue. Returns {number, url}. |
gluecron_comment_issue | Add a comment to an existing issue. Returns {commentId}. |
gluecron_close_issue | Close an open issue (idempotent). Returns {state}. |
gluecron_reopen_issue | Reopen a closed issue (idempotent). Returns {state}. |
gluecron_create_pr | Open a new pull request. Returns {number, url}. |
gluecron_get_pr | Fetch full PR detail (title, body, state, branches, draft, author). |
gluecron_list_prs | List PRs filtered by state (open|closed|merged|all). Returns up to 50 rows. |
gluecron_comment_pr | Add a comment to a pull request. Returns {commentId}. |
gluecron_merge_pr | Merge an open PR. Enforces gate checks, branch-protection rules, and the pre-merge risk score. Returns {merged, sha?, reason?, riskScore?}. |
gluecron_close_pr | Close a PR without merging (idempotent). Returns {state}. |
Example Claude session
# Open an issue
User: "Open an issue on my-org/api titled 'Rate limiter not resetting'"
Claude: [calls gluecron_create_issue]
Created issue #42: /my-org/api/issues/42
# Create a PR from a feature branch
User: "Open a PR from feat/rate-limit-fix into main"
Claude: [calls gluecron_create_pr with head_branch=feat/rate-limit-fix]
Opened PR #17: /my-org/api/pulls/17
# Merge after review
User: "Merge PR #17 — I've reviewed it"
Claude: [calls gluecron_merge_pr with number=17]
Merged PR #17. SHA: a3f9c2dGate enforcement on merge
gluecron_merge_pr enforces the same checks as the web UI merge button:
- PR must not be a draft.
- Head branch ref must resolve.
- GateTest hard gates must pass (secrets scan, dependency advisories, policy violations).
- Branch-protection rules must be satisfied.
- If the pre-merge risk score is critical, the tool returns
merged: falsewith a prompt to re-call withconfirm_high_risk: true.
One-click Claude Desktop extension
Download the .dxt extension at /gluecron.dxt. Open it in Claude Desktop — it installs the MCP config automatically. No JSON editing needed.