Deepgram Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 26, 2026

Query the Deepgram API: projects, project balances, and API keys.

VerifiedSTDIODesktop onlyDeveloper ToolsAI & ML

Overview

AI-generated overview

Local MCP server that lets an assistant query the Deepgram API for projects, project balances and API keys.

What you can do
  • List and inspect Deepgram projects
  • Check project balances
  • Look up API keys associated with the account
  • All actions go through the Deepgram API using the account's own credentials.
When to use it
Useful when you want an assistant to check Deepgram account state — which projects exist, what balance remains, and which API keys are registered — without opening the dashboard.
Requirements
Runs locally as an npm package (deepgram-mcp) over stdio, so Node.js is needed. A Deepgram account and API credentials are required, although the manifest declares no environment variables or headers.
Before you install
The server works with Deepgram API keys, which are sensitive credentials; the manifest does not say how they are supplied. API key listings may expose key metadata, and any balance or project data is sent to the assistant and the model provider.

Installation

In SourceWeft

  1. Open Deepgram Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestOct 17, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.