MCP server
dg mcp runs a local stdio bridge to Deepgram’s hosted docs MCP server at https://api.dx.deepgram.com/kapa/mcp, authenticated with your dg credentials. It exposes one tool, search_deepgram_knowledge_sources. Use dg mcp when your editor runs only stdio MCP servers; otherwise add the hosted server directly from Agentic Developer Tools. Add one of the two.
Start the MCP server
Starts the bridge over stdio, the only transport dg mcp supports.
Transport
dg mcp runs only over stdio. --transport, --host, and -p/--port still exist as flags, kept for compatibility with older MCP client configs, but they’re ignored except for --transport stdio; passing --transport sse (or anything other than stdio) now fails outright:
--base-url still sets the Deepgram developer API host (default https://api.dx.deepgram.com), and --debug still turns on debug logging.
Configuration
Claude Code
Add to your project’s .mcp.json:
Or add globally:
OpenAI Codex
Add the server from the terminal:
Or add it to ~/.codex/config.toml, which the Codex CLI, IDE extension, and desktop app share:
Gemini CLI
VS Code and GitHub Copilot
Add to .vscode/mcp.json:
Cursor
Add to .cursor/mcp.json:
Other MCP clients
Any client that runs stdio MCP servers reads the same entry. Add it to the client’s MCP configuration file:
Available tools
dg mcp exposes one tool, search_deepgram_knowledge_sources. The server answers questions from the Deepgram documentation.
Authentication
The bridge uses the credentials stored by dg login. With no stored dg login credential and no DEEPGRAM_API_KEY, dg mcp still starts and completes the stdio handshake; the credential check only runs on the first search_deepgram_knowledge_sources call, which fails with dg mcp can't start the documentation search: No API key is set. Run dg login or set DEEPGRAM_API_KEY, then restart the MCP server. Your editor shows the server as connected even though every tool call will fail until a credential is set and the server is restarted.
For CI environments: