Deepgram MCP integration for AI agents.
Connect AI agents to Deepgram through 8 structured actions, including get model, get project, and get project model. Review authentication, inputs, workflows…
- 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 Deepgram integration exposes
The Deepgram Agent App exposes 8 provider-backed actions for ai and developer tools work. Its current contract lets an authorized agent get metadata for one public deepgram model, get details for one deepgram project, and get metadata for one model available to a deepgram project. 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 Deepgram account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Deepgram capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_modelREADGet metadata for one public Deepgram model.
INPUTS: modelId
get_projectREADGet details for one Deepgram project.
INPUTS: projectId
get_project_modelREADGet metadata for one model available to a Deepgram project.
INPUTS: projectId / modelId
list_modelsREADList the latest public Deepgram models.
INPUTS: includeOutdated
list_project_balancesREADList the outstanding balances for a Deepgram project.
INPUTS: projectId
list_project_keysREADList the API keys associated with a Deepgram project.
INPUTS: projectId / status
list_project_modelsREADList the models available to a specific Deepgram project.
INPUTS: projectId / includeOutdated
list_projectsREADList the Deepgram projects available to the current API key.
INPUT CONTRACTS
Know what the action needs before it runs.
get_model
modelIdOPTIONAL- The unique identifier of the Deepgram model.
get_project
projectIdOPTIONAL- The unique identifier of the Deepgram project.
get_project_model
projectIdOPTIONAL- The unique identifier of the Deepgram project.
modelIdOPTIONAL- The unique identifier of the Deepgram model.
list_models
includeOutdatedOPTIONAL- Whether to include non-latest Deepgram model versions in the response.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Model
Get metadata for one public Deepgram model. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_modelVerify with Get Project
Get details for one Deepgram project. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_projectSAFETY BOUNDARY
Operate Deepgram with explicit limits
- Authorize Deepgram with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Deepgram 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 Deepgram rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Deepgram task completed successfully.
CONNECTION MODEL
API key
Deepgram API key sent as Authorization: Token <API_KEY>. Create or manage keys in the Deepgram Console and API key guide: https://developers.deepgram.com/docs/create-additional-api-keys.
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 Deepgram.