deepgram-mcp
Deepgram's Model Context Protocol server — gives AI editors (Claude Code, Cursor, Windsurf, and others) direct access to Deepgram's speech, transcription, and audio intelligence tools.
Standalone package. Install deepgram-mcp directly if you want just the MCP server without the full CLI suite. If you already use the Deepgram CLI (pip install deepctl), deepgram-mcp is included as a dependency and the dg mcp command wraps it — no separate install needed.
Why deepgram-mcp is different
Most MCP servers ship tools as hardcoded Python. When the provider adds a new tool, you must upgrade the package to get it.
deepgram-mcp fetches its tool list from Deepgram's API at runtime. New tools appear in your editor the next time you connect — no package upgrade required.
Requirements
A Deepgram API key. Get one free at console.deepgram.com.
Set it as an environment variable:
export DEEPGRAM_API_KEY=your_api_key_here
Installation
pip install deepgram-mcp
Editor setup
Claude Code
Add to .mcp.json in your project root (or ~/.claude/mcp.json for global):
{
"mcpServers": {
"deepgram": {
"command": "deepgram-mcp",
"env": {
"DEEPGRAM_API_KEY": "your_api_key_here"
}
}
}
}
Or via CLI:
claude mcp add deepgram -- deepgram-mcp
Cursor
Add to .cursor/mcp.json:
{
"mcpServers": {
"deepgram": {
"command": "deepgram-mcp",
"env": {
"DEEPGRAM_API_KEY": "your_api_key_here"
}
}
}
}
Windsurf
Add to your Windsurf MCP config:
{
"mcpServers": {
"deepgram": {
"command": "deepgram-mcp",
"env": {
"DEEPGRAM_API_KEY": "your_api_key_here"
}
}
}
}
Usage
stdio (default — for editor integration)
deepgram-mcp --api-key your_api_key_here
SSE (HTTP server)
deepgram-mcp --transport sse --port 8000
Options
| Flag | Default | Description |
|---|---|---|
--transport |
stdio |
Transport mode: stdio or sse |
--port |
8000 |
Port for SSE server |
--host |
127.0.0.1 |
Host for SSE server |
--api-key |
$DEEPGRAM_API_KEY |
Deepgram API key |
--base-url |
https://api.dx.deepgram.com |
Deepgram developer API base URL |
--debug |
false |
Print debug info to stderr |
Use as a library
import asyncio
from deepgram_mcp import run_proxy
asyncio.run(run_proxy(
transport="stdio",
host="127.0.0.1",
port=8000,
api_key="your_api_key_here",
base_url="https://api.dx.deepgram.com",
debug=False,
))
Deepgram CLI
If you use the Deepgram CLI, dg mcp wraps this package and handles authentication automatically:
dg mcp
dg mcp --transport sse --port 8000
License
MIT — see LICENSE.
Metadata
Release files for deepgram-mcp 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| deepgram_mcp-0.1.1.tar.gz | 6.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| deepgram_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.0 kB
Release files / deepgram_mcp-0.1.1.tar.gz
| Download URL | deepgram_mcp-0.1.1.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
907955b48130f57d91a81342f1adeeb7a37153d042e1e7affc8fc85f90e3bf54
|
|
BLAKE2b-256 checksum How to use checksums |
eaad828d8a554df8125c5e63d9056c1765705b6e64a139e5cac36fe31d27e859
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 4, 2026.
Transparency logRelease files / deepgram_mcp-0.1.1-py3-none-any.whl
| Download URL | deepgram_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eff4904eaee6d424c5201f949e308bc29bd2c2621c74ce38839e2ba180dc4d9a
|
|
BLAKE2b-256 checksum How to use checksums |
e8f1aeeb3fe25c34d7d23c052bfec9a98f7410bf2b4771de5038f0e94dac6e77
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 4, 2026.
Transparency log