Asr_mcp_server

Created By
vidau-aia year ago
A Model Context Protocol (MCP) server that provides ASR(Automatic Speech Recognition) capabilities using the whisper engine. This server exposes TTS functionality through MCP tools, making it easy to integrate speech synthesis into your applications.
Overview

what is ASR MCP Server?

ASR MCP Server is a Model Context Protocol (MCP) server that provides Automatic Speech Recognition (ASR) capabilities using the Whisper engine, enabling easy integration of speech synthesis into applications.

how to use ASR MCP Server?

To use the ASR MCP Server, ensure you have Python 3.10 or higher, the uv package manager, and OpenAI Whisper installed. Configure the MCP settings and run the server using the provided command.

key features of ASR MCP Server?

  • Provides ASR capabilities using the Whisper engine.
  • Exposes Text-to-Speech (TTS) functionality through MCP tools.
  • Easy integration into various applications.

use cases of ASR MCP Server?

  1. Integrating speech recognition in customer service applications.
  2. Enabling voice commands in mobile and web applications.
  3. Developing accessibility features for users with disabilities.

FAQ from ASR MCP Server?

  • What are the prerequisites for using ASR MCP Server?

You need Python 3.10 or higher, the uv package manager, and OpenAI Whisper.

  • Can I use ASR MCP Server for multiple languages?

Yes! The server supports multiple languages depending on the Whisper engine capabilities.

  • Is there any cost associated with using ASR MCP Server?

The server is open-source and free to use.

Server Config

{
  "mcpServers": {
    "asr_mcp_server": {
      "command": "/YOUR_CONDA_PATH/bin/uv",
      "args": [
        "--directory",
        "/YOUR_PATH/asr_mcp_server",
        "run",
        "asr_server.py"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
vidau-ai
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago