Pre-launch — Gluecron is in final validation. Public signups and git hosting for non-owner users open after launch review.
Commit4cd9a67unknown_key

fix: declare Gluecron MCP server in .mcp.json so sessions actually load it

fix: declare Gluecron MCP server in .mcp.json so sessions actually load it

The server was declared under an mcpServers key in .claude/settings.json,
which Claude Code never reads for MCP servers — project-scoped servers
must live in .mcp.json at the repo root. This is why no AI session ever
had the gluecron_* write tools (gluecron_create_pr, gluecron_merge_pr,
...) despite CLAUDE.md instructing their use. Also documents the cloud-
session workflow for running PRs through the canonical Gluecron remote.

Requires GLUECRON_PAT in the session environment; header expansion via
${GLUECRON_PAT}.

https://claude.ai/code/session_01RHwR7NK4HawRujV4dJmtab
Claude committed on June 13, 2026Parent: bc519ae
2 files changed+2424cd9a67f48422d6b71fcb64c83d5eade9474bee7
2 changed files+24−2
Added.mcp.json+11−0View fileUnifiedSplit
1{
2 "mcpServers": {
3 "gluecron": {
4 "type": "http",
5 "url": "https://gluecron.com/mcp",
6 "headers": {
7 "Authorization": "Bearer ${GLUECRON_PAT}"
8 }
9 }
10 }
11}
ModifiedCLAUDE.md+13−2View fileUnifiedSplit
1010
1111**For any AI session working in this repo:**
1212
13- Use the Gluecron MCP server (`.claude/settings.json` already points
14 there). Tools: `gluecron_create_pr`, `gluecron_merge_pr`,
13- Use the Gluecron MCP server. It is declared in `.mcp.json` at the
14 repo root (project scope — this is the file Claude Code actually
15 loads MCP servers from, on both web/cloud sessions and the CLI; the
16 old `mcpServers` block in `.claude/settings.json` was never read).
17 Tools: `gluecron_create_pr`, `gluecron_merge_pr`,
1518 `gluecron_create_issue`, `gluecron_comment_pr`, etc. See
1619 `src/lib/mcp-tools.ts` for the full 15-tool surface.
20- **Cloud (web) sessions:** the clone comes from the GitHub mirror and
21 `git push` to origin goes through the GitHub proxy. To run a PR
22 through Gluecron: (1) push the feature branch to origin as usual,
23 (2) also push it to the canonical remote —
24 `git push https://x:${GLUECRON_PAT}@gluecron.com/ccantynz/Gluecron.com.git HEAD:<branch>`
25 (requires `gluecron.com` in the environment's network allowlist) —
26 then (3) open the PR with `gluecron_create_pr`. If gluecron.com is
27 unreachable, fall back to GitHub and say so in the session.
1728- Do NOT call any `mcp__github__*` write tool. The settings file's
1829 `permissions.deny` already blocks them; if you encounter a deny
1930 error, switch to the equivalent `gluecron_*` tool.
2031