scroll-world
A skill that turn any brand into a scrollable 3D world landing page
Gleap's official MCP server: tickets, contacts, CRM, help center and support stats. OAuth sign-in.
Skills that teach the AI this kind of work; they work alongside this one
A skill that turn any brand into a scrollable 3D world landing page
This one is in the “Apps that connect to AI” tab, which is ordered without stars, in this order
| 1. In Claude’s connector directory | No | |
|---|---|---|
| 2. Tried by our team | No | |
| 3. Works for Thai users | No | |
| 4. Usage without stars | 20/100 | Popularity 0 · Freshness 12 · Still answering 8 · Likes from users +0 |
| 5. Listed on | 2026-11-21 |
Likes from users: 0 · Adds at most 5 points to the order (1 per person). It cannot be bought.
Quality: Passed 4/4 basic checks (shown, not used for ordering)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Gleap. Follow https://mcp.popnx.com/i/gleap-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 4/4 checks · What you ask goes through the maker’s server (mcp.gleap.ai) · ✓ Commands checked Nov 21, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
The name and URL are filled in for you. Check them and click Add · if you are signed out, Claude asks you to sign in first
Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
CustomizeConnectors
Click “Add” → “Custom” → “Web” and fill in these 2 fields
Copy each value into the field with the same name in Claude, then click Continue
Gleaphttps://mcp.gleap.ai/mcp+ConnectorsGleap
Use Gleap and tell me what you can do for me, then show me one thing✓ If Claude says it is using Gleap or shows a Gleap tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
Gleaphttps://mcp.gleap.ai/mcpStart a new chat and pick Gleap from your plugins before typing
Use Gleap and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using Gleap or shows a Gleap tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user gleap https://mcp.gleap.ai/mcpYou should see Gleap listed as connected
Use Gleap and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Gleap or shows a Gleap tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use Gleap and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Gleap or shows a Gleap tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use Gleap and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Gleap or shows a Gleap tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://mcp.gleap.ai/mcpJSON settings are under “For developers” below
Claude Code
claude mcp add --transport http --scope user gleap https://mcp.gleap.ai/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"gleap": {
"url": "https://mcp.gleap.ai/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"gleap": {
"type": "http",
"url": "https://mcp.gleap.ai/mcp"
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 22, 2026
The registry name was verified against the domain gleap.ai (the registry checks domain ownership)
Code last changed yesterday
Not applicable: a cloud server run by the owner of gleap.ai; you don't run code from the repo
Responded in 497 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/gleap-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 4 of 4 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed yesterday, and the latest version (1.0.1) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: PostHog, Relaticle, ChatbotX, X (Twitter) MCP Server by Xquik, Betterlytics
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Query analytics, manage feature flags and experiments, and investigate errors in PostHog.
Open-source CRM your AI agents can write to: companies, people, opportunities, tasks and notes.
Omnichannel customer messaging, CRM contacts, flows, sequences, broadcasts, and AI automation.
Xquik is the world's fastest and cheapest X (Twitter) data API with the most complete X data.
Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.
| This one Gleap | PostHog | Relaticle | ChatbotX | X (Twitter) MCP Server by Xquik | Betterlytics | |
|---|---|---|---|---|---|---|
| Runs where | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | Yes |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | NOASSERTION | AGPL-3.0 | NOASSERTION | MIT | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Connect your Gleap workspace to Claude and other AI assistants via the Model Context Protocol. Manage tickets, contacts, help center articles, and statistics using natural language.
Install dependencies, then build and run the server locally:
npm install # install dependencies
npm run build # compile TypeScript to build/ npm start # run the compiled server (node build/index.js)
Use npm run dev to recompile automatically on file changes while you work.
Node.js 22 (engines in package.json). Before opening a PR, run npm run typecheck, npm test and npm run build; CI runs them too. Coding agents: see AGENTS.md.
https://mcp.gleap.ai/mcphttps://mcp.us.gleap.ai/mcpNo API key or client ID setup is required. The OAuth flow handles authentication automatically.
Send these headers with every request:
| Header | Value |
|---|---|
x-gleap-api-key | Your Gleap API key |
x-gleap-project-id | Your project: the Project ID (Settings → Project → General) or its internal ID |
A coding agent working a Gleap ticket names its coding session, with the sessionId argument of a tool (report_progress, send_message, …) or for every call with the header x-gleap-session-id (the client sets it from .gleap/session.json, a Kai Code sandbox from its MCP config; OAuth and API-key connections alike). The server then sends X-Gleap-Session-Id with every write of that tool call (reads go without it), plus X-Gleap-Session-Explicit: 1 when the id came from the tool's own sessionId argument (Gleap refuses every write that explicitly names a stopped session): Gleap books the writes to the session's agent (an agent's reply does not stop the agent the way a teammate's does) and checks each write against the session (the episode guard). A session id that does not count for the write (another project's session, one not linked to the written ticket, or one left behind in .gleap/session.json) is ignored: the write is then the caller's own, as without a session. The results then also carry what Gleap says about the session, whatever the tool:
stop: true: the ticket is no longer the session's (a teammate took it over, replied to the customer, unassigned the agent or stopped the session). The result is only the STOP instruction, with structuredContent.gleapStop: true: the field Kai Code's runner and the Gleap plugin act on (never words in a result). Only this server sets it; a field of that name in API data is dropped.newCustomerMessages: what the customer wrote that the agent has not been shown, listed after the result.staleThread: true in the result): the agent reads them, adjusts and sends once more.Without a session id nothing changes: no header, no extra lines.
| Tool | Description |
|---|---|
search_tickets | Full-text search across tickets |
find_tickets | Filter tickets by status, priority, assignee, tags, date |
get_ticket | Get a specific ticket by ID |
create_ticket | Create a new ticket |
get_ticket_types | List ticket types with their custom fields, status lanes and priorities |
get_ticket_messages | Get the full conversation history (messages) for a ticket |
get_ticket_activity_log | Get the console logs, network requests and click trail the SDK captured with a ticket. Coding agents call it on bug reports before reproducing, to see the console errors, failed requests and the user's clicks. Headers are never returned, secrets are redacted and long logs are trimmed (errors and failed requests first); section and search narrow it |
send_message | Reply to a customer or add an internal note (Markdown). Agent workflows: the agent asks its operator in its own conversation (an instruction to answer or update the customer is the approval), then sends; with sessionId the reply is the session agent's and Gleap refuses a stale one (stale_thread, with the new messages) or one after a stop |
draft_reply_to_composer | Stage a drafted reply in the ticket's dashboard composer for a person to review, edit and send. Sends nothing. For a person's own AI client, also when a .gleap/session.json from another ticket is still around: Gleap refuses Kai runs and the coding session working that ticket (410), which ask their operator and send with send_message |
report_progress | Report the fix status on the Gleap coding session you were started from (deeplink hand-off loop; session-scoped since 2026-08), the same snapshot every runtime reports: status (queued, working, needs_input, completed, failed, cancelled), step while working (investigating, reproduced, fixing), a one-line message, question with needs_input (kind, prompt, options, audience customer or team), customerLine (one sentence of status the customer may read), howSolved (one paragraph on how the ticket was solved, sent with the last report; it feeds Kai Support's learning), agentKind, agentName and device. The older phase still works: status wins, and a report with only status also sends the phase it stands for, for a Server from before the fix status. Registers PRs (completed with prUrl) and takes the two fix messages: customerUpdateMessage (sent right away) and customerShipMessage (sent when the fix is live, by the project's post-merge setting); the result says what happened to each. The ticket is done when the customer confirms or 24 hours after the last answer without a reply, not at the merge. The result also carries stop, newCustomerMessages (see Coding sessions) and the hook block for .gleap/session.json |
update_plan | Live checklist on the Gleap coding session (sessionId or ticketId, like report_progress): the whole list each call, statuses pending/in_progress/completed/cancelled |
wrap_up | End-of-turn card on the session: recap, at most one question, 0-2 actions (merge_pr, open_pr, review_changes, open_preview; send_customer_update is removed and refused) |
share_screenshot | Post a screenshot (optionally a before/after pair) into the session thread. Returns the curl -T upload commands to run (the server cannot read local files); imageBase64 (≤ 1.5 MB each) for agents without a shell |
publish_artifact | Publish a self-contained HTML page (≤ 1 MB) into the session thread; artifactId publishes a new version |
get_agent_workflow | The Gleap ticket workflow (fix, answer, feature) as Markdown, plus the .gleap/session.json content for the Gleap plugin |
get_ticket_screenshot | The ticket's SDK screenshot as image content (Gleap file hosts only, ≤ 2 MB) |
describe_database | The team's own databases Kai Code may read (read-only, this ticket's customer only): tables, columns, masked columns, query format. Kai Code runs on a ticket only (the run key's ticket pin); refused for every other connection |
query_database | One read-only query (a SQL SELECT or a MongoDB JSON request) on the team's database, kept to the ticket's customer (scope: team across customers always waits for a data owner); at most 200 rows, sensitive columns masked. It may wait for a person's approval (status: pending with a queryId). Values from results never go into code, tests, fixtures, commits or PRs. Kai Code runs on a ticket only |
get_query_result | The status of a query that waited for approval, and its rows once a data owner let it run (kept a day). Kai Code runs on a ticket only |
get_workflows | List all workflows in the project (live and draft), with their channels, whether Kai Support answers in them (kaiAnswers) and the agent they pass to |
get_workflows_available_for_ticket | List the live workflows startable on a specific ticket |
run_ticket_workflow | Manually start a workflow on a ticket (the "Start a workflow" action) |
get_setup_status | Where the project stands for AI support: the Hard tickets settings (hardTickets: on a click or automatically, on Kai Code Cloud or a Bridge machine; ticketDone: thank-you and review ask), the default team, and (admins of a new workspace) the signup steps left |
get_agents | The project's AI agents: name, live or draft, customer-facing or team |
set_ai_mode | Removed (stub for one release): AI-first and AI-assisted are gone; does nothing and points to update_workflow and the Hard tickets settings |
start_kai_resolve | Removed (stub for one release): Kai Resolve is Kai Support's hard-ticket mode, started with Work on it on the ticket or automatically; does nothing and says so |
update_workflow | Change which channels a workflow runs on (addChannels / removeChannels) and whether it is live; never its steps |
get_workflow_build_options | What a workflow can use, by name: teams, tags, Your API endpoints, webhooks, integrations, sequences, contact fields, message variables |
get_workflow_steps | One workflow step by step, with path ids and step numbers, what could go live and the hashes publish_workflow_draft needs |
create_workflow_draft | Build a new conversation workflow from steps; always a draft, no customer gets it |
change_workflow_draft | Edit a workflow's name, trigger, channels, audience and steps; a change to a live workflow waits as a draft |
publish_workflow_draft | Make a draft live or apply a waiting change, for the version the person agreed to (draftHash), with the editor's publish checks |
create_team / update_team | Create a team, rename it, add or remove members (others stay), change how it hands out tickets |
set_default_team | The team agents escalate to when nobody else is named (admins) |
search_contacts | Full-text search across contacts |
get_contacts | Filter contacts by email, name, company |
get_contact | Get a specific contact by ID |
create_contact | Create a new contact |
get_companies | List/search the project's companies (organisations) |
get_company | Get a company by its external companyId, incl. custom data |
update_company | Create or update a company (name, plan, value, custom data) |
get_pipelines | List CRM pipelines with their stages |
get_pipeline | Get a pipeline incl. stages and fields (fieldIds for entry values) |
get_pipeline_stats | Per-stage counts and field aggregations (e.g. sum of deal values per stage) plus pipeline totals |
get_pipeline_entries | List a pipeline's entries, optionally for one stage |
get_pipeline_entry | Get one entry with its pipeline context |
add_pipeline_entry | Add a company/contact to a pipeline (stage + initial values) |
move_pipeline_entry | Move an entry to another stage |
update_pipeline_entry_values | Update an entry's field values (merge; null clears) |
remove_pipeline_entry | Remove an entry from a pipeline (record itself is untouched) |
get_record_pipelines | Which pipelines a company/contact is on |
| get_help_center_sites | List the projec