Demodesk MCP integration for AI agents.
Connect AI agents to Demodesk through 8 structured actions, including batch get recording transcripts, get current user, and get recording. Review authentica…
- ACTION CONTRACTS
- 8
- 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 Demodesk integration exposes
The Demodesk Agent App exposes 8 provider-backed actions for productivity and ai work. Its current contract lets an authorized agent get transcripts for up to 100 demodesk recording tokens in one request, get the demodesk user represented by the current api key, and get one demodesk recording by public recording token. 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 Demodesk account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Demodesk capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
batch_get_recording_transcriptsREADGet transcripts for up to 100 Demodesk recording tokens in one request.
INPUTS: recordingTokens / lang / format
get_current_userREADGet the Demodesk user represented by the current API key.
get_recordingREADGet one Demodesk recording by public recording token.
INPUTS: token
get_recording_transcriptREADGet the transcript for one Demodesk recording token.
INPUTS: token / lang / format
list_recording_scorecardsREADList scorecards linked to a Demodesk recording.
INPUTS: token
list_recording_summariesREADList AI-generated summaries attached to a Demodesk recording.
INPUTS: token
list_recordingsREADList Demodesk recordings with cursor pagination and optional filters.
INPUTS: cursor / limit / filters
list_usersREADList active Demodesk users visible to the current API key.
INPUTS: search / cursor / limit
INPUT CONTRACTS
Know what the action needs before it runs.
batch_get_recording_transcripts
recordingTokensREQUIRED- Public Demodesk recording tokens.
langOPTIONAL- Language code used to request an on-the-fly translation.
formatOPTIONAL- Transcript response format to request from Demodesk.
get_recording
tokenREQUIRED- Public Demodesk recording token.
get_recording_transcript
tokenREQUIRED- Public Demodesk recording token.
langOPTIONAL- Language code used to request an on-the-fly translation.
formatOPTIONAL- Transcript response format to request from Demodesk.
list_recording_scorecards
tokenREQUIRED- Public Demodesk recording token.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Batch Get Recording Transcripts
Get transcripts for up to 100 Demodesk recording tokens in one request. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
batch_get_recording_transcriptsVerify with Get Current User
Get the Demodesk user represented by the current API key. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_current_userSAFETY BOUNDARY
Operate Demodesk with explicit limits
- Authorize Demodesk with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Demodesk data may still be sensitive and should be minimized before it enters model context.
- 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 Demodesk rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Demodesk task completed successfully.
CONNECTION MODEL
API key
Demodesk API key sent as a Bearer token. Generate one in Demodesk under Settings > Integrations > Other, as described in the official API reference: https://demodesk.com/api/docs/index.html
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
- 8
- WRITE SIGNALS
- 0
- 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 Demodesk.