The Gleap MCP server for your AI tools.

The Gleap MCP server is a hosted Model Context Protocol server at https://mcp.gleap.io/mcp (https://mcp.us.gleap.ai/mcp for projects hosted in the US) that connects an AI client to one Gleap project. It exposes over 90 tools for tickets, conversations, contacts, companies, help center, outbound messages (surveys, emails, chat messages, banners, info cards, checklists, tours, tooltips, push and news), feature requests, statistics, pipelines, workflows and coding sessions, so an assistant can read customer context and take supported actions with your review.

Any MCP client that supports Streamable HTTP and OAuth: Claude.ai, Claude Desktop and Claude Code, Codex in the CLI and IDE extension, Cursor, and custom clients. Clients that can send custom headers may use an API key instead of OAuth. The setup guide lists the current client steps.

OAuth with PKCE and dynamic client registration. Your client opens the Gleap sign-in, you choose the project, and Gleap issues a token scoped to that project. No API key appears in a prompt or a deep link. Clients that support custom headers can send x-gleap-api-key and x-gleap-project-id instead.

Yes. It is an MCP server built around a customer support workspace: tickets and their full conversations, the customer and company behind them, the help center they were answered from, the feature requests they voted on and the statistics of the support team. It also covers pipelines, workflows and the coding sessions that fix confirmed bugs.

Read-only tools include search_tickets, find_tickets, get_ticket_messages, search_contacts, get_help_center_article, search_feature_requests, get_statistics_facts, search_knowledgebase and ask_code. Writes such as send_message, update_ticket, create_help_center_article and run_ticket_workflow are annotated as writes so your client can ask before running them.

No. draft_reply_to_composer stages the reply in the ticket composer for everyone viewing the ticket and sends nothing. send_message is a separate tool for the customer reply or an internal note. Gleap's instructions tell coding tools to send a reply when you ask them to answer the customer, and to draft one only when you ask for a draft; your client's tool approvals decide which calls need your confirmation.

On plans with Kai Code, choosing Open in Claude Code, Codex or Cursor on a ticket creates a coding session and opens the tool with a kickoff prompt. The tool fetches the ticket over MCP, then calls report_progress at each phase: investigating, reproduced, fixing, pr_opened with the PR link, blocked or done. The ticket shows the status live, and after the PR merges Gleap follows your configured customer-update workflow. With the PR the tool passes two customer messages: Gleap sends one right away (the fix is built and is being reviewed) and the other when the fix is live, following your post-merge setting. Read more about Kai Code.

Yes. Kai Code and Kai Resolve use the MCP servers configured under Kai Code settings, from presets such as Gleap, Linear, GitHub, HubSpot, Jira and Stripe to any custom HTTP or stdio server. Custom agents pick tools from the same catalog, with individual tools switched off per agent.

During an investigation Kai Resolve may query the connected MCP servers, for example a database, to answer questions the customer would otherwise have to re-supply. Destructive tools such as deletes, refunds and database drops are blocked for Kai Resolve and its sandboxed investigator. Kai Resolve's own Gleap access is five tools: the customer's ticket history, similar tickets and feature requests. See Kai Resolve.

Use the Server API when your own code calls Gleap, for imports and application integrations. Use MCP when an AI client chooses and calls tools in response to a request. The integration directory covers native integrations and Composio connectors.

No. The Gleap MCP server is part of the platform on Team, Pro and Enterprise; Starter has no API or MCP access. Usage in your own AI client is billed by that client. Kai Resolve, Kai Code and custom agents are included from Team, with AI usage billed separately. See pricing.

Tokens are scoped to one project and verified on every request. Tool annotations identify write operations for your client. Drafting and sending are separate tools; configure client approvals and agent permissions for the actions you allow. The trust center covers SOC 2, GDPR and the security overview.

Yes. Agents draft surveys, emails, chat messages, banners, info cards, checklists, product tours, tooltips, push and news, then set the trigger, page rules, audience and schedule. get_targeting_options lists the events and contact attributes your project tracks, and preview_outbound_audience counts who matches before anything goes live. When the audience needs an event you do not track yet, get_event_tracking_guide returns the tracking code for your SDK or backend. Publishing is a separate tool for after your approval; one-off sends need the recipient count you approved, and one-off emails and push never go to every contact. See outbound messages.

The Gleap platform keeps conversations, bug reports, feature requests and knowledge in one workspace. MCP extends that context to the AI tools your team already uses and lets coding tools close the loop on tickets. Read how Gleap agents close the loop from report to release.