Heartbeat
Plug-and-play online communities. Heartbeat provides tools for creating and managing online communities with features for users, channels, events, messages, and more.
Verdict
Common use cases
- Pull event rosters before a cohort kickoff
- Audit group membership for access reviews
- Reactivate alumni who want back in
- Draft welcome emails using new-member lists
- Summarize channel activity for weekly updates
Integration
- Vendor
- Heartbeat
- Category
- other
- Auth
- API_KEY
- Tools
- 7
- Composio slug
heartbeat
Tools
- Get Events
Tool to retrieve event information from the community. Use when you need to list events with optional pagination support.
- List channels
Tool to retrieve a paginated list of channels in the community. Use when you need to list, browse, or search for channels in the Heartbeat community. Supports filtering by archived status, channel type, and pagination.
- List Groups
Tool to retrieve a paginated list of access groups in the community. Use when you need to browse groups with optional filters for parent groups or user membership. Supports cursor-based pagination.
- List Users
Tool to retrieve a paginated list of users in the Heartbeat community. Use when you need to get user information with optional filtering by creation date, group membership, or role.
- Reactivate User
Tool to reactivate a previously deleted user by email to allow them to access the community again. Use when you need to restore access for a user who was previously removed.
- Retrieve Group
Tool to retrieve a single group by its ID. Use when you need to get detailed information about a specific group in the Heartbeat community.
- Retrieve User
Tool to retrieve a single user by their ID. Use when you need to get detailed information about a specific user in the Heartbeat community.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Search for Heartbeat in the MCP directory and click Connect. 3. You'll be prompted to paste an API key — log into your Heartbeat community admin panel, go to Settings > API, and generate a new key with read and user-management scopes. 4. Copy the key and paste it into the Switchy prompt, then click Authorize. 5. Switchy confirms the connection and shows the seven available tools. 6. Open any Space, type '@Heartbeat list the next three events' and send — if the MCP returns event names and dates, you're connected. 7. Use '@Heartbeat list users created in the last week' to test user lookup, or '@Heartbeat retrieve group [group-id]' to verify group access. 8. If a tool fails, double-check your API key has the correct scopes in Heartbeat and hasn't expired.
What teammates see: by default, memories from Heartbeat are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Upcoming Events Brief
@Heartbeat get the next five events from the community and write a short paragraph for each — include the event name, date, and a one-sentence description of what members can expect.Open in a Space →
New Member Welcome
@Heartbeat list all users created in the last seven days, then draft a welcome message I can send to each one — mention their name and invite them to introduce themselves in the General channel.Open in a Space →
Channel Inventory
@Heartbeat list all channels that aren't archived, then create a table with channel name, type, and member count — flag any that look inactive or redundant.Open in a Space →
Group Membership Check
@Heartbeat retrieve group [paste-group-id-here] and tell me how many members it has, who the admins are, and whether it's set to private or public.Open in a Space →
Reactivate Alumni
@Heartbeat reactivate the user with email [paste-email-here], then confirm they're back in the community and let me know which groups they were originally part of.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Heartbeat list all upcoming events in the next 30 days and show me which channels they're posted in
Based on the community calendar, there are 8 upcoming events in the next 30 days. The largest is 'Q1 Product Roadmap Review' on March 15 in #product-updates (47 RSVPs), followed by 'Community Office Hours' recurring weekly in #general (avg 12 attendees), and 'Design System Workshop' on March 22 in #design (18 RSVPs). Three smaller events are scheduled in #regional-emea and two in #customer-success. This illustrative example shows how the MCP surfaces event metadata including dates, channels, and engagement metrics.
Demonstrates read-only event discovery across the community. Requires API key with events:read scope. The MCP returns raw event objects; the AI synthesizes them into a readable summary. Pagination applies if your community has 50+ events—this example assumes a typical result set.
@Heartbeat find all users who joined in the last 7 days and add them to the 'New Members' group automatically
Found 14 users who joined between March 1-7, 2025. However, the Heartbeat MCP provides read-only user listing and cannot directly modify group memberships. I can retrieve the 'New Members' group details (ID: grp_abc123) and show you the list of new user IDs, but you'll need to add them via the Heartbeat dashboard or a separate API call with write permissions. This illustrative example shows the MCP's current scope boundary.
Highlights a common limitation: this MCP focuses on data retrieval, not bulk write operations. The tools can list users and retrieve group details, but group membership changes require manual action or additional integrations. Useful for auditing and reporting workflows, less so for automation.
@Heartbeat compare activity levels across all channels and recommend which ones we should archive based on low engagement
Analyzing 23 active channels in your community: 6 channels show zero posts in the last 90 days (#legacy-project, #archive-2023, #temp-collab, #old-announcements, #deprecated-api, #sunset-feature). Another 4 have fewer than 5 posts per month with no recent replies (#niche-topic, #regional-apac, #beta-testers, #partners-only). The most active channels are #general (340 posts/month), #product-updates (89 posts/month), and #support (156 posts/month). This illustrative summary suggests archiving the 6 dormant channels and monitoring the low-activity group. The MCP provides channel metadata; the AI performs the engagement analysis.
Showcases synthesis: the MCP lists channels with metadata, the AI reasons over engagement patterns. Requires channels:read scope. The MCP doesn't calculate 'activity scores'—the AI infers from post counts and timestamps. Actual archival must be done manually in Heartbeat; this is a decision-support workflow.
Use-case deep-dives
When Heartbeat MCP speeds up new community manager handoffs
A nonprofit hires a new community manager to run their 800-member Heartbeat space. The outgoing manager left no documentation on who has admin access, which channels are archived, or how groups map to program cohorts. The Heartbeat MCP wins here: the new manager asks Switchy to list all users filtered by role, pull group memberships, and surface archived channels in one conversation. Within 20 minutes they have a spreadsheet of admins, a channel audit, and a group hierarchy they can actually understand. This works because Heartbeat's API exposes the access-control layer cleanly and the MCP's pagination handles communities under 2,000 users without choking. If your community tops 5,000 members or you need bulk user edits (not just lookups), you'll hit rate limits and want a dedicated admin dashboard instead.
Heartbeat MCP for post-event member engagement checks
A 12-person EdTech startup runs monthly virtual workshops through Heartbeat and wants to follow up with no-shows. Their ops lead used to export event RSVPs manually, cross-reference with actual attendees in Zoom, then tag people in Heartbeat channels. Now they ask Switchy to pull the last three events, compare RSVP lists against a Zoom CSV, and draft personalized check-in messages for the 40 people who didn't show. The Heartbeat MCP handles the event retrieval and user lookups; Switchy drafts the messages in one session. This scenario works when your event volume is under 10 per month and your community is small enough that personalized outreach matters. If you're running 50 events a quarter, you need a CRM integration, not an MCP query flow.
When to use Heartbeat MCP for membership hygiene sweeps
A coaching network with 300 members organizes access around cohorts that graduate every quarter. The admin team needs to archive old groups, reactivate alumni who rejoin, and confirm no one has lingering access to expired program channels. They ask Switchy to list all groups, filter by parent group, pull user counts, and flag groups with zero activity in 90 days. The Heartbeat MCP surfaces the candidates for archival in two minutes; the admin confirms and archives manually in Heartbeat's UI. This works because the MCP exposes group hierarchy and user membership in a way the Heartbeat dashboard doesn't surface all at once. The trade-off: if your access model is more complex than nested groups (say, role-based permissions across 50 channels), the MCP won't replace a real access audit tool. For quarterly hygiene on a straightforward group structure, it's the fastest path to a clean list.
Frequently asked
What does the Heartbeat MCP do in Switchy?
It connects your Heartbeat community to Switchy's AI workspace so you can query members, channels, events, and access groups without leaving the conversation. Your team can ask questions like "who joined this week" or "what events are coming up" and get answers pulled directly from Heartbeat's API. Useful for community managers who want fast lookups without opening the Heartbeat dashboard.
Do I need admin access to connect Heartbeat MCP?
Yes. You'll need a Heartbeat API key, which only workspace admins can generate from your Heartbeat settings. The key grants read access to users, channels, groups, and events, plus write access to reactivate deleted members. If you're not an admin in Heartbeat, ask whoever manages your community to create the key and share it with your Switchy workspace owner.
Can the Heartbeat MCP send messages or create events?
No. It's read-only except for one action: reactivating a previously deleted user. You can list events, channels, groups, and members, but you can't post messages, create new events, or modify channel settings. If you need to take action based on what the MCP finds, you'll still open Heartbeat's web app or use their full API directly.
Why use this instead of just logging into Heartbeat?
Speed and context. If your team is already working in Switchy and someone asks "how many people are in the product feedback group
Who on the team should connect the Heartbeat MCP?
Whoever manages your Heartbeat community and has API key access. Typically a community manager, customer success lead, or ops person. Once connected in Switchy, anyone in your workspace can query the data through conversations. The API key stays private to Switchy; individual team members don't need their own Heartbeat logins to ask questions.