Gleap for Claude Code and Codex
Work your Gleap support queue from your coding agent: triage tickets, look up customers, draft replies grounded in your help center, and fix or answer tickets as a tracked Gleap coding session, with your plan, screenshots and a closing wrap-up visible to your team in Gleap.
This repository is a plugin marketplace named gleap with two plugins. Install the one that matches where your Gleap workspace is hosted, not both:
| Plugin | Region | MCP server |
|---|
gleap | EU | https://mcp.gleap.ai/mcp |
gleap-us | US | https://mcp.us.gleap.ai/mcp |
Both have the same skills and hooks.
Install in Claude Code
From your shell:
claude plugin marketplace add GleapSDK/gleap-claude-plugin
claude plugin install gleap@gleap
US workspaces install gleap-us@gleap instead. Inside a session, /plugin marketplace add GleapSDK/gleap-claude-plugin followed by /plugin install gleap@gleap does the same, and on Claude Code 2.1.275 or later one line is enough:
/plugin install gleap --marketplace GleapSDK/gleap-claude-plugin
Start a new session (or run /reload-plugins), then open /mcp, select the plugin's gleap server and choose Authenticate. Your browser opens for the OAuth sign-in: sign in and pick the Gleap project. No API key.
Already added the Gleap MCP server yourself with claude mcp add? If the tools show up twice, remove your own copy with claude mcp remove gleap --scope user.
Updates: third-party marketplaces don't auto-update by default. Turn it on under /plugin → Marketplaces → gleap → Enable auto-update, or run claude plugin update gleap@gleap.
Install in Codex
From your shell:
codex plugin marketplace add GleapSDK/gleap-claude-plugin
codex plugin add gleap@gleap
US workspaces add gleap-us@gleap instead. In the ChatGPT desktop app, add the marketplace the same way and open codex://plugins/install/gleap?marketplace=gleap (or browse Plugins); in the Codex CLI, /plugins opens the plugin browser. Start a new session afterwards.
Codex doesn't run plugin hooks until you trust them: run /hooks in the CLI and trust the three Gleap hooks. Trust is tied to the exact hook definition, so Codex asks again when a plugin update changes a hook.
Sign-in: the plugin bundles the Gleap MCP server as gleap. If Codex doesn't prompt you to sign in, run codex mcp login gleap. (The Codex docs don't yet say how OAuth for a plugin-bundled server is started from the CLI; the desktop app signs in on install.)
What's included
MCP server. The hosted Gleap MCP server for your region: tickets, contacts, companies, CRM pipelines, help center, surveys, feature requests, analytics, and the coding-session tools (report_progress, update_plan, share_screenshot, publish_artifact, wrap_up, get_ticket_screenshot). Read tools are annotated read-only; anything that creates, updates or deletes asks first.
Skills
| Skill | What it does |
|---|
fix-ticket | Fixes a ticket or builds a feature request as a tracked Gleap coding session that owns the ticket until the customer says it is solved: reports in, saves the session file, works by the Gleap workflow that ships inside the skill, keeps a plan, shares screenshots, opens the PR, asks you before anything goes to the customer, and ends each turn with wrap_up. |
answer-ticket | Investigates a ticket in the code and data, shows you the answer and sends it when you say yes, as a tracked session that owns the ticket until it is solved. No code changes, no PR. |
triage-inbox | Ranks the open queue by what costs most if it waits, clusters tickets sharing a root cause, and proposes owners and priorities. |
draft-support-reply | Reads the full thread and the customer's history, grounds the answer in your help center, and drafts a reply in the customer's language. |
In Claude Code they run as /gleap:fix-ticket 1234 (or /gleap-us:…), or Claude picks them up when you ask it to fix or answer a Gleap ticket. In Codex, ask for it ("fix Gleap ticket #1234") or pick the skill.
Hooks. The hooks run scripts/gleap-hook.mjs (Node 18 or later, no dependencies):
| Event | Claude Code | Codex | Sends |
|---|
| After the agent updates its plan | PostToolUse on TodoWrite, TaskCreate, TaskUpdate | PostToolUse on update_plan | the plan items (text and status) |
| When a turn ends | Stop | Stop | the agent's last message, at most 4,000 characters |
| When a session starts or resumes | SessionStart | SessionStart | nothing but "still here" |
| After a Gleap tool answers STOP | PostToolUse on the Gleap MCP tools | (not used) | nothing: it deletes .gleap/session.json, because the session is over |
Gleap uses the plan for the live checklist on the session, and the last message as the turn's recap when the agent ended a turn without calling wrap_up (an agent's own wrap_up always wins).
Session header (Claude Code). The plugin's MCP config has a headersHelper (the same script, mcp-headers): when Claude Code connects to the Gleap MCP server, it adds x-gleap-session-id with the id of the session in .gleap/session.json. Gleap then books the session's writes (a reply, a status change) to the session's agent and checks them: a write after Gleap stopped the session is refused, and a reply the customer has overtaken is sent back to be re-read. No session file, an expired one or one of the other region: no header, as before. Only the session id is sent, never the token. Claude Code reads the file when it connects, from the folder it was started in (or a folder inside the repository); the agent also passes its sessionId on each call. Codex has no such helper for plugins, so there the agent passes sessionId only.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
