Beamer
Beamer is a platform that enables companies to announce news, updates, and features directly within their applications or websites, enhancing user engagement and communication.
Verdict
Common use cases
- Check how many posts match a filter
- Grab feed URL for newsletter embed
- Retrieve unread notifications for a user
- List comments on a specific post
- Confirm category metadata before grouping
Integration
- Vendor
- Beamer
- Category
- other
- Auth
- API_KEY
- Tools
- 11
- Composio slug
beamer
Tools
- Count Posts
Tool to count existing posts. use when you need the number of posts matching specific filters.
- Get Category
Tool to retrieve a specific category by its id. use when you need to load metadata for a category before filtering or grouping posts by that category.
- Get Feed
Tool to retrieve the url for your standalone feed. use after embedding to fetch the feed link for embedding or sharing.
- Get Feeds
Tool to retrieve the url for your feed. use when you need to embed or access your standalone feed.
- Get Feed URL
Tool to retrieve the url for your personalized feed. use after setting segmentation or language options to embed or redirect users.
- Get Notification
Tool to retrieve details of a specific notification by its unique notification id. use after obtaining the notification id to fetch its full details.
- Get Notifications
Tool to fetch unread notifications. use after providing user context to retrieve and mark notifications as read.
- Get Post Comments
Tool to retrieve comments for a specific post. use after identifying the post id to list its comments.
- Get Post Reactions
Tool to retrieve all reactions associated with a specific post. use when you need to list reactions and optionally filter by date, reaction type, or pagination.
- Get Posts
Tool to retrieve a list of posts. use when you need ids and titles of posts for further operations.
- Ping API
Tool to ping the beamer api. use when verifying api key authentication before making further requests.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add MCP Integration' and select Beamer from the list. 3. Log into your Beamer account, go to Settings > API, and generate a new API key with read permissions. 4. Copy the key and paste it into the API Key field in Switchy, then click Connect. 5. Switchy will validate the key and confirm the connection—you'll see 'Beamer' appear in your workspace's MCP list. 6. Open any Space, type '@Beamer count posts' in the chat, and send—if the MCP responds with a post count, the integration is working. 7. To invoke other tools, @mention Beamer followed by the tool name and any required parameters (e.g. '@Beamer get category id:abc123').
What teammates see: by default, memories from Beamer 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
Count Recent Posts
@Beamer count posts published in the last 30 days and tell me the total number.Open in a Space →
Get Embed Feed URL
@Beamer get the standalone feed URL for our changelog and format it as a markdown link.Open in a Space →
Check User Notifications
@Beamer get unread notifications for user ID user_12345 and list the titles.Open in a Space →
List Post Comments
@Beamer get comments for post ID post_67890 and summarize the main themes.Open in a Space →
Load Category Details
@Beamer get category details for category ID cat_abc123 and show me the name and description.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@beamer how many feature announcements did we publish in the last 30 days, and which category had the most posts?
Based on the count, you published 12 posts in the last 30 days. Breaking down by category: 'Product Updates' had 7 posts, 'New Features' had 3 posts, and 'Bug Fixes' had 2 posts. Product Updates was your most active category this month. This count reflects posts visible to all users; segmented posts may vary by audience.
This example uses the Count Posts tool with date and category filters. The MCP returns aggregate counts, not full post content. If you need to analyze post performance or engagement metrics, you'll need to retrieve individual posts separately—counting alone won't show views or reactions.
@beamer fetch all unread notifications for user ID 'user_8472' and mark them as read after I review them
Retrieved 3 unread notifications for user_8472: (1) 'New integration with Slack' posted 2 days ago, (2) 'Pricing update for Enterprise plan' posted 5 days ago, (3) 'Scheduled maintenance on Jan 15' posted 1 week ago. All three notifications have now been marked as read for this user. Note that marking as read is immediate and cannot be undone through the API.
This demonstrates the Get Notifications tool, which both retrieves and marks notifications as read in a single call. Be aware this is a destructive action—once marked read, you can't revert it via the MCP. Requires valid user identification; incorrect user IDs will return empty results without error.
@beamer pull comments from our most recent post about the dashboard redesign, then draft a summary of user sentiment and common feature requests
Fetched 18 comments from post 'Dashboard Redesign v2.0'. Sentiment breakdown: 12 positive, 4 neutral, 2 negative. Common themes: users love the dark mode toggle (mentioned 7 times) and faster load times (5 mentions). Top feature requests: customizable widget layout (4 requests) and export-to-CSV option (3 requests). Two users reported minor layout issues on mobile Safari. Overall reception is strongly positive with clear direction for iteration.
This pairs the Get Post Comments tool with AI synthesis to extract actionable insights from user feedback. The MCP returns raw comment text and metadata; the AI performs sentiment analysis and clustering. Accuracy depends on comment volume—sparse feedback may yield less reliable patterns. Post ID must be known in advance.
Use-case deep-dives
When Beamer beats manual changelog updates for small product teams
A 6-person SaaS team shipping weekly releases needs customers to see what's new without engineering writing custom changelog pages. Beamer's 11 tools handle the full loop: publish posts via API, segment by user plan, and surface unread notifications in-app. The Get Notifications and Get Feed URL tools let you embed personalized changelogs without building your own notification system. This works if your release cadence is weekly or slower and you have under 500 active posts—beyond that, the Count Posts and Get Post Comments tools start feeling slow for bulk operations. If you're shipping multiple times daily or need changelog data piped into your analytics warehouse, you'll outgrow this fast. For teams that want changelog-as-a-service and can live with Beamer's UI constraints, this MCP saves 2-3 engineering days per quarter.
Beamer for support teams routing users to recent updates
A 4-person support team at a B2B tool fields repeat questions about new features customers missed. Beamer's Get Feed and Get Category tools let you pull changelog posts by topic and link customers directly to the relevant announcement. The Get Post Comments tool surfaces user questions already answered in the post thread, cutting repeat tickets. This setup works when your product updates map cleanly to 5-10 stable categories and your support volume is under 200 tickets per week. If your changelog is unstructured or you need to search across post content (not just titles and categories), Beamer's tooling won't help—you'd need a full-text search MCP instead. For teams where 'did you see the changelog' is a daily support pattern, this MCP turns Beamer into a queryable knowledge base without custom dev work.
Using Beamer to sync product launches with go-to-market timing
A 3-person marketing team at a startup needs to publish changelog posts exactly when a feature goes live, then track which user segments saw the announcement. Beamer's Get Feed URL tool generates segmented feed links for different customer tiers, and the Get Notifications tool confirms which users have unread items before sending follow-up emails. This works if your launch calendar is predictable (monthly or quarterly big releases) and you have under 10 user segments. The API_KEY auth means any team member can trigger posts from a shared Slack workflow or Airtable automation. If your launches are ad-hoc or you need A/B testing on announcement copy, Beamer's tooling is too rigid—you'd want a headless CMS MCP instead. For teams that treat changelogs as a marketing channel and need basic segmentation without engineering overhead, this MCP closes the loop between product and GTM.
Frequently asked
What does the Beamer MCP let me do in Switchy?
The Beamer MCP lets your AI agents read and count product update posts, retrieve category metadata, fetch feed URLs for embedding, and pull notification details. It's read-only — agents can query your changelog content and user notifications but can't create or edit posts. Use it when you want AI to surface recent product updates or check unread notifications without leaving the conversation.
Do I need admin access to connect Beamer?
You need an API key from your Beamer account, which typically requires admin or owner permissions to generate. Once connected in Switchy, any team member with access to the workspace can invoke the MCP's tools. The API key scopes to your entire Beamer project, so treat it like a service account credential.
Can the Beamer MCP post new updates or reply to comments?
No. The MCP exposes read-only tools — counting posts, fetching categories, retrieving notifications and comments. If you need to publish updates or moderate comments, use Beamer's web dashboard or their write-enabled API directly. This MCP is for surfacing existing content to your AI agents, not authoring new content.
Why use this instead of just linking to the Beamer dashboard?
The MCP lets your AI agents pull changelog data into the conversation without context-switching. Instead of asking a teammate to check Beamer manually, the agent can count posts matching a filter, retrieve the latest notification, or grab a feed URL on demand. It's faster for quick lookups and keeps the workflow inside Switchy.
Who on the team should connect the Beamer integration?
Whoever manages your Beamer account and can generate an API key — usually a product manager or marketing lead. Once connected, the MCP is shared across your Switchy workspace, so any team member can ask the AI to query Beamer data. It doesn't count against user seats or MCP limits.