Gleap

@Gleap show me all open tickets assigned to the mobile team that were created in the last 7 days

Based on the Gleap project data, there are 8 open tickets assigned to the mobile team from the past week. The breakdown includes: 3 bug reports (two related to iOS push notifications, one Android crash on startup), 2 feature requests (offline mode and biometric login), and 3 user feedback items about onboarding flow. The highest priority item is the iOS push notification issue affecting approximately 200 users, created 2 days ago. This is an illustrative example showing how Gleap's ticket retrieval would surface team-specific workload.

This example demonstrates Gleap's ticket filtering and search capabilities. Requires API key with read access to tickets. Note that the actual ticket structure and custom fields vary by your Gleap project configuration—some teams use different priority schemes or custom statuses beyond the default open/closed states.

@Gleap create a new support ticket for the bug report I just received: user can't upload profile photos larger than 2MB on Safari desktop

I've created ticket #GT-1847 in your Gleap project with the title 'Safari desktop: Profile photo upload fails above 2MB'. The ticket is set to 'Open' status, assigned to the web team, and tagged with 'bug' and 'safari'. Priority is marked as Medium based on the single-browser scope. The ticket includes the reproduction details you provided and is now visible in your Gleap dashboard for triage. This illustrative example shows how ticket creation captures the essential context.

This example shows Gleap's ticket creation workflow. The MCP will use your default project settings for team assignment and priority unless you specify otherwise in the prompt. Side-effect: creates a real ticket in your Gleap workspace that will appear in team queues and trigger any configured notifications or automations.

@Gleap review the last 15 closed tickets about login issues and draft a help center article covering the most common problems

After analyzing 15 recently closed login-related tickets in Gleap, the most frequent issues are: password reset emails landing in spam (6 tickets), two-factor authentication code delays (4 tickets), and session timeout confusion (3 tickets). I've drafted a help center article titled 'Troubleshooting Login Problems' with sections addressing each issue. The draft includes step-by-step solutions pulled from your support team's actual responses, plus a note about the recent SMTP configuration change that resolved the spam folder problem. This illustrative example shows how Gleap data can inform documentation.

This example combines Gleap's ticket retrieval with AI synthesis to generate documentation from support patterns. The MCP provides the raw ticket data; the AI identifies themes and drafts content. You'll need to review the output for accuracy and create the actual help center collection using Gleap's content tools—this prompt doesn't auto-publish articles.

When Gleap beats separate tools for early-stage support ops

A 6-person SaaS team handling 40-60 support tickets weekly hits the sweet spot for this MCP. You're running standup and need to archive resolved tickets, reassign new ones to the right engineer, and update help docs based on recurring questions—all without switching between Intercom, Notion, and Linear. Gleap's 29 tools cover the full loop: create tickets from chat messages, route them to teams you define on the fly, then push resolutions into help center collections. The API key auth means any teammate can invoke these actions from Switchy without waiting on admin provisioning. If your ticket volume climbs past 200/week or you need advanced automation rules, you'll outgrow this and want a dedicated ticketing platform. Below that threshold, this MCP collapses three subscriptions into one workflow.

Using Gleap to close onboarding loops in shared workspace

A 4-person customer success team onboarding 10-15 new accounts per month can use this MCP to track engagement checklists without leaving Switchy. You create a checklist for each customer cohort ("Enterprise Q1 2025"), then retrieve and update it as milestones hit—first login, feature adoption, support ticket closure. The "Get a Checklist" and related tools let you query status mid-standup and decide who follows up. This works when your onboarding steps are linear and you're not running complex conditional logic (if they skip step 2, trigger email 3). If your playbook branches heavily or you need Salesforce sync, you'll want a purpose-built CS platform instead. For teams under 20 active onboardings at once, this MCP keeps the process visible in the same workspace where you're already coordinating.

When Gleap's collection tools speed up docs-as-code workflows

A 3-person product team shipping a feature next Tuesday needs to publish 8-12 help articles before launch. You're drafting in Notion, but Gleap hosts your live help center. This MCP's "Create a Collection" and "Get a Collection" tools let you scaffold the article structure from Switchy, assign writing to teammates, then push finalized content without opening the Gleap dashboard. You create collections for "New Feature Overview" and "Troubleshooting", retrieve them to check what's missing, then bulk-create articles as you finish drafts. This shortcut matters when you're under deadline and context-switching kills momentum. If your help center has 500+ articles or you need versioning and approval workflows, you'll want a headless CMS instead. For launch sprints with tight timelines and small doc sets, this MCP keeps the work in one place.