Skip to main content
Glama
Audio Transcriber MCP Server

Audio Transcriber MCP Server

by Ichigo3766

Servidor MCP de transcripciones de voz a texto de OpenAI

Un servidor MCP que proporciona capacidades de transcripción de audio utilizando la API de OpenAI.

Instalación

Configuración

  1. Clonar el repositorio:

git clone https://github.com/Ichigo3766/audio-transcriber-mcp.git
cd audio-transcriber-mcp
  1. Instalar dependencias:

npm install
  1. Construir el servidor:

npm run build
  1. Configure su clave API de OpenAI en sus variables de entorno.

  2. Agregue la configuración del servidor a su entorno:

{
  "mcpServers": {
    "audio-transcriber": {
      "command": "node",
      "args": [
        "/path/to/audio-transcriber-mcp/build/index.js"
      ],
      "env": {
        "OPENAI_API_KEY": "",
        "OPENAI_BASE_URL": "", // Optional
        "OPENAI_MODEL": "" // Optional
      }
    }
  }
}

Reemplace /path/to/audio-transcriber-mcp con la ruta real donde clonó el repositorio.

Related MCP server: whisper-telegram-mcp

Características

Herramientas

  • transcribe_audio - Transcribe archivos de audio usando la API de OpenAI

    • Toma la ruta del archivo como parámetro obligatorio

    • Parámetros opcionales:

      • save_to_file: Booleano para guardar la transcripción en un archivo

      • idioma: código de idioma ISO-639-1 (p. ej., "en", "es")

Licencia

Este servidor MCP cuenta con la licencia MIT. Esto significa que puede usar, modificar y distribuir el software libremente, sujeto a los términos y condiciones de la licencia MIT. Para más detalles, consulte el archivo de LICENCIA en el repositorio del proyecto.

Available Tools

1 tool
transcribe_audioC

Transcribe an audio file using OpenAI Whisper API

Inputs: filepath (required), language, save_to_file.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and singular, making it impossible for an agent to misselect between non-existent alternatives.

    Naming Consistency5/5

    The single tool name follows a clear verb_noun pattern (transcribe_audio), and with only one tool, there is no inconsistency to evaluate. The naming is straightforward and aligns with common conventions.

    Tool Count2/5

    A single tool is too few for a server named 'Audio Transcriber MCP Server', as it suggests a limited scope that may not cover related operations like transcription status checks, file management, or configuration. This minimal set could hinder agent workflows that require more comprehensive functionality.

    Completeness2/5

    The tool set is severely incomplete for audio transcription tasks. While it provides a core transcription function, it lacks essential operations such as listing available transcriptions, retrieving transcription results, handling errors, or managing audio files, which are typical in such domains and could lead to agent failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers