Connect your AI assistant to Gleap.

Use the Gleap MCP server to let Claude, ChatGPT, Codex, Cursor, VS Code, and custom assistants work with tickets, contacts, statistics, help center content, and changelogs.

4.6/5 on G2
Trusted by 4,500+ teams worldwide
01
Gleap MCP server
Customer context inside your AI assistant.
Connect once through the Gleap MCP server
Read setup guide
Powering 4,500+ of the fastest-moving software teams
Give your AI tool controlled access to Gleap. Add https://mcp.gleap.io/mcp once with Streamable HTTP, authenticate with OAuth, and your assistant can call structured Gleap tools directly. While other teams copy customer data between tabs, yours just asks.
What the Gleap MCP server exposes
Structured tools for support, content, and reporting
Ticket management
Search, filter, inspect, and create tickets with search_tickets, find_tickets, get_ticket, and create_ticket.
Contact management
Find contacts, inspect customer profiles, list matching users, and create new contacts from your AI assistant.
Statistics
Ask for facts, lists, bar-chart data, or raw statistics when you need support performance and feedback trends.
Help center collections
Browse the collection tree, inspect collections, create new sections, and update existing help center structure.
Help center articles
Retrieve article details, list articles in a collection, create localized drafts, and update existing content.
News and changelogs
Read, create, update, and delete news or changelog entries when release communication should start from a prompt.
Connect with OAuth first
API key headers are for legacy or test setups.
Most teams connect through OAuth with their Gleap account. If your client only supports custom HTTP headers, use project for your Gleap Project ID and api-key for your Gleap API Key.
Tobi Duelli
Tobi Duelli
Gleap team
Read setup guide
Supported OAuth clients
Same server URL across the AI tools your team already uses
Claude Desktop and Claude Code
Add the Gleap MCP server, approve OAuth, and ask Claude to work with tickets, contacts, docs, and trends.
Cursor
Connect Cursor through its MCP setup flow so customer reports and support context can follow you into code.
VS Code
Use Gleap from MCP-compatible VS Code workflows when product questions need live customer context.
OpenAI clients
Connect supported OpenAI client flows to the same Gleap workspace and tool permissions.
Google clients
Use supported Google client flows when OAuth is available for your MCP setup.
Custom MCP clients
Building your own client? Contact Gleap to whitelist your redirect domain before using OAuth in production.
Server URL and transport
One endpoint for MCP-compatible assistants.
Use https://mcp.gleap.io/mcp as the server URL and select Streamable HTTP as the transport. Once connected, your assistant can call the available Gleap tools directly from the client.
Open setup guide
Use the API for product workflows
When your backend should call Gleap directly.
MCP is for people asking AI assistants to work with Gleap context. The Server API is for product code, imports, reporting jobs, and scheduled workflows that should run the same way every time.
Open API docs
“Essential to our development process.”
Gleap was implemented within minutes and helps MARK.ONE fix bugs quickly while building real customer relationships.
Mark Breuß
Founder, MARK.ONE
Example prompts
Plain-language requests, structured Gleap actions.
01
Triage unassigned tickets
“Show me all open high-priority tickets that have not been assigned to anyone.” Your assistant can filter tickets and return IDs, titles, and creation dates.
02
Draft help center content
“Create a password reset article in English and German.” Your assistant can find the right collection and create a localized draft for review.
03
Compare support performance
“What was our average first response time last month compared with the month before?” Your assistant can query statistics and summarize the trend.
Stop copying tickets into prompts. Bring Gleap context into your AI assistant.
4.6 / 5
G2 · 4,500+ teams