Deepgram CLI MCP
Deepgram
stdioTool names not enumerated0
About Deepgram CLI MCP
Deepgram’s official CLI MCP proxies developer API capabilities into a coding client.
What you can use it for
- Use Deepgram speech, transcription, synthesis and developer API operations from a coding agent.
Connection and setup
- Hosting
- local
- Transport
- stdio
- Endpoint
- Local process; no hosted endpoint documented
- Authentication
- Uses stored dg login credentials, or DEEPGRAM_API_KEY for CI.
Requirements
- Official Deepgram CLI installed and `dg` on the MCP client PATH
- Deepgram account/API credentials
Setup steps
- Install the official CLI using https://cli.deepgram.com/ instructions.
- Run `dg login` and finish its authentication flow.
- Configure the MCP client to launch `dg` with argument `mcp`.
- Reload the client and inspect tools/list; tool availability is proxied from the live developer API.
Tools
No individual tool names are documented in the reviewed sources.
Official Deepgram MCP source says the tool list is fetched dynamically from Deepgram API at runtime; exact names depend on API exposure, so no static catalog rows are recorded.
Limitations and notes
- Available tools depend on the Deepgram API and authenticated credentials.
Original sources
- official cli repository
Official Deepgram CLI repository.
- verified organization avatar
Developer organization avatar; fallback tier D, visually checked.
- official documentation
Official Deepgram docs document `dg mcp` over stdio or optional SSE and say tools proxy the authenticated developer API, whose list must be inspected live.
- official crawl4ai tool inventory audit
Official docs say the CLI proxies the remote API’s current tool list and direct clients to inspect it after connecting; tools are account/service-version dependent.
Documentation checked 2026-10-28T19:00:00.000Z. Connection has not been runtime tested.
