Beamer MCP integration for AI agents.
Connect AI agents to Beamer through 4 structured actions, including count unread posts, create post, and get feed url. Review authentication, inputs, workflo…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Beamer integration exposes
The Beamer Agent App exposes 4 provider-backed actions for communication and productivity work. Its current contract lets an authorized agent count unread beamer posts for one end-user context, create a new beamer changelog post with one or more translations, and retrieve the standalone beamer feed url with optional language and segmentation filters. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Beamer account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Beamer capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
count_unread_postsREADCount unread Beamer posts for one end-user context.
INPUTS: userId / filterByUserId
create_postWRITECreate a new Beamer changelog post with one or more translations.
INPUTS: title / content / category / publish / archive
get_feed_urlREADRetrieve the standalone Beamer feed URL with optional language and segmentation filters.
INPUTS: language / filterByUrl / filter
list_postsREADList existing Beamer posts with optional changelog, audience, and analytics filters.
INPUTS: filter / forceFilter / filterUrl / dateFrom / dateTo
INPUT CONTRACTS
Know what the action needs before it runs.
count_unread_posts
userIdOPTIONAL- The end-user identifier used together with filterByUserId.
filterByUserIdOPTIONAL- Whether to include single-user posts that match the provided userId.
create_post
titleREQUIRED- The translated post titles in Beamer order.
contentREQUIRED- The translated post content values in the same order as the titles.
categoryOPTIONAL- The category to assign to the new post.
publishOPTIONAL- Whether to publish the post immediately.
archiveOPTIONAL- Whether the post should start archived.
get_feed_url
languageOPTIONAL- A two-letter ISO-639 language code used by Beamer for feed localization.
filterByUrlOPTIONAL- Whether URL segmentation should be applied to the feed URL.
filterOPTIONAL- An optional segmentation filter string to apply.
list_posts
filterOPTIONAL- Retrieve posts with a matching segmentation filter.
forceFilterOPTIONAL- Only retrieve posts that match this segmentation filter.
filterUrlOPTIONAL- Retrieve posts with a matching segmentation URL.
dateFromOPTIONAL- An ISO-8601 date-time string accepted by the Beamer API.
dateToOPTIONAL- An ISO-8601 date-time string accepted by the Beamer API.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Count Unread Posts
Count unread Beamer posts for one end-user context. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
count_unread_postsControl Create Post
Create a new Beamer changelog post with one or more translations. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_postVerify with Get Feed Url
Retrieve the standalone Beamer feed URL with optional language and segmentation filters. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_feed_urlSAFETY BOUNDARY
Operate Beamer with explicit limits
- Authorize Beamer with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Beamer rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Beamer task completed successfully.
CONNECTION MODEL
API key
Beamer API key sent in the Beamer-Api-Key header. Find or manage it in Settings > API after signing in: https://app.getbeamer.com/settings.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Beamer.