Audio MCP Server

Created By
GongRzhea year ago
Overview

what is Audio MCP Server?

Audio MCP Server is a Model Context Protocol server that provides audio input/output capabilities for AI assistants like Claude, enabling interaction with your computer's audio system.

how to use Audio MCP Server?

To use the Audio MCP Server, clone the repository, set up a virtual environment, install dependencies, and configure it with Claude Desktop. After setup, you can interact with the server through Claude by asking it to list audio devices, record audio, or play audio files.

key features of Audio MCP Server?

  • List available audio devices on your system
  • Record audio from microphones with customizable settings
  • Playback of recent recordings and audio files
  • Future implementation of text-to-speech functionality

use cases of Audio MCP Server?

  1. Recording audio for transcription or analysis
  2. Playing back audio for review or testing
  3. Integrating audio capabilities into AI assistant workflows

FAQ from Audio MCP Server?

  • What are the system requirements?

Python 3.8 or higher and audio input/output devices are required.

  • How do I configure the server with Claude Desktop?

You need to add specific configuration settings to the Claude Desktop configuration file based on your operating system.

  • What should I do if no audio devices are found?

Ensure your devices are connected, recognized by the OS, and that you have the necessary permissions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
GongRzhe
Star
0
Language
Python
License
MIT 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