Beebole MCP integration for AI agents.
Connect AI agents to Beebole through 1 structured actions, including execute graphql. Review authentication, inputs, workflows, and safety guidance.
- ACTION CONTRACTS
- 1
- 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 Beebole integration exposes
The Beebole Agent App exposes 1 provider-backed actions for productivity and developer tools work. Its current contract lets an authorized agent execute a json-friendly beebole graphql query or mutation against the connected account. 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 Beebole account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Beebole capabilities.
Showing 1 of 1 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
execute_graphqlWRITEExecute a JSON-friendly Beebole GraphQL query or mutation against the connected account.
INPUTS: query / variables / operationName
INPUT CONTRACTS
Know what the action needs before it runs.
execute_graphql
queryREQUIRED- The GraphQL query or mutation document to execute.
variablesOPTIONAL- GraphQL variables keyed by variable name.
operationNameOPTIONAL- The GraphQL operation name to execute when the document defines multiple operations.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Execute Graphql
Execute a JSON-friendly Beebole GraphQL query or mutation against the connected account. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
execute_graphqlControl Execute Graphql
Execute a JSON-friendly Beebole GraphQL query or mutation against the connected account. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
execute_graphqlVerify with Execute Graphql
Execute a JSON-friendly Beebole GraphQL query or mutation against the connected account. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
execute_graphqlSAFETY BOUNDARY
Operate Beebole with explicit limits
- Authorize Beebole 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 Beebole rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Beebole task completed successfully.
CONNECTION MODEL
API key
Beebole API key sent with the apikey header. In Beebole, open the initials button at the bottom of the left sidebar, then open API Key to copy or reset it: https://beebole.com/help/api/introduction.
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
- 0
- 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 Beebole.