anomalyco / anomalyco/opencode

[FEATURE]: Voice input MCP server for CLI terminal tools

Open
#41,413 5 comments 0 reactions 1 assignee View on GitHub

@jlongster is already working on this.

Since Aug 9, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Feature request

  • I have searched for existing issues and confirmed this is not a duplicate
Problem

Terminal-based AI coding tools (OpenCode CLI, Claude Code, Cursor) cannot use voice input because terminal apps do not support clickable microphone icons. Users must type all prompts manually.

Proposed Solution

Add voice input support via a standalone MCP server (@opencode-ai/voice-mcp) that provides:

  1. voice_transcribe — Record audio from microphone and transcribe to text
  2. voice_type — Record, transcribe, and type at cursor position
  3. voice_status — Check voice input availability
Implementation
  • MCP server using @modelcontextprotocol/sdk
  • Local Whisper transcription via faster-whisper (Python)
  • Cross-platform recording (sox/ffmpeg)
  • 100% local — no cloud API required
  • Works with OpenCode CLI, Claude Code, Cursor, and any MCP-compatible tool
Usage

Users add to their config:

{
  "mcpServers": {
    "voice": {
      "command": "npx",
      "args": ["-y", "@opencode-ai/voice-mcp"]
    }
  }
}
Differentiation from existing issues

Existing issues (#41364, #33300, #35219, #37742, #39688) focus on desktop app voice input (GUI microphone button). This issue is about CLI/terminal voice input via MCP server, which works across all MCP-compatible tools.

Benefits
  • Works in any terminal app (not just desktop)
  • No subscription required
  • 100% local processing
  • Simple one-line config
  • Cross-platform (macOS, Linux, Windows)
Testing
  • Tested on macOS with faster-whisper base model
  • Recording works with sox
  • MCP server verified with tool listing
Next Steps
  1. Review this issue
  2. If approved, submit PR with implementation
  3. Publish to npm as @opencode-ai/voice-mcp

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.