Deepgram MCP connector for AI agents

Tools your transcription agent reaches for on Deepgram MCP, scoped per user.

CALL ANY TOOL

The Deepgram MCP connector exposes a knowledge search tool that lets agents query Deepgram's full documentation and technical knowledge base.

deepgrammcp_search_deepgram_knowledge_sources

Search Deepgram docs

Search Deepgram documentation and knowledge sources for the most relevant results for a given query.

Parameters

Name

Type

Required

Description

query

string

Required

The search query to find relevant results in Deepgram's documentation and knowledge sources.

Build your Agent

Same auth pattern across every framework.

from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="deepgrammcp")

mcp = MultiServerMCPClient({
    "deepgrammcp": {
        "url": "https://mcp.scalekit.com/deepgrammcp",
        "headers": {"Authorization": "Bearer " + token}
    }
})
tools = await mcp.get_tools()

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "deepgrammcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/deepgrammcp
// Pass: Authorization: Bearer + token

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "deepgrammcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/deepgrammcp
// Pass: Authorization: Bearer + token

from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="deepgrammcp")
# Connect to MCP at https://mcp.scalekit.com/deepgrammcp
# Pass: Authorization: Bearer + token

Try these prompts

Paste any prompt into your agent to get started.

Search & discover

Copy the prompt

Copied

Search the Deepgram docs for how to implement real-time transcription with WebSockets.

Copy the prompt

Copied

Find Deepgram documentation on speaker diarization and how to enable it in a streaming session.

API & integration guidance

Copy the prompt

Copied

Look up how to use Deepgram's Nova model for batch transcription and what languages are supported.

Copy the prompt

Copied

Search for Deepgram's best practices for handling punctuation and formatting in transcription results.

SEE HOW AUTH WORKS

User authorises once. Every agent call after uses their token with scope enforcement.

Authorize

Your user connects

Deepgram MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Deepgram MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Deepgram MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Deepgram MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

No items found.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought.

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.

// shared token
 audit → bot_service_account

 // scalekit
 audit → user_abc ✓

02.

Authentication is not authorization

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Deepgram MCP as the user or as a shared key?

Scalekit resolves a per-user credential for each call. The Deepgram MCP audit log shows the real user identity, not a shared service account.

Where is the Deepgram MCP token stored?

In Scalekit's AES-256 encrypted vault, isolated per tenant. Tokens are auto-refreshed before expiry and revocable from a single dashboard without code changes.

Can I limit what the agent is allowed to do in Deepgram MCP?

Pass a toolNames filter to listScopedTools. Scalekit enforces the allowed set before every API call — the agent cannot invoke tools outside the approved list.

What happens when a user revokes Deepgram MCP access?

The token is invalidated at the next tool call. The agent fails closed rather than falling back to a shared key. Other users are unaffected and the revocation event is logged with a timestamp.

Deepgram's API has usage-based billing. Will an agent running on behalf of multiple users cause unexpected charges?

Because Scalekit issues per-user credentials, each user's API calls are attributed to their own Deepgram account or project key. This keeps usage and billing traceable per user rather than pooled under a single account, and lets you set spend limits at the individual level.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit