mcpField
N
noisy-coding

noisy-coding

Local
github.com/noisyDeveloper Tools14Updated 3w ago
Repository

About noisy-coding

Noisy Studio is a desktop voice interface for Claude Code users, enabling spoken exchanges with a coding agent while it works. It combines speech recognition, spoken replies, per-conversation voice and character settings, and a conversation dashboard.

Key features

  1. 01Speech recognition and spoken replies
  2. 02Per-conversation voice and character settings
  3. 03Dashboard for followed conversations
  4. 04Bundled Python engine

Use cases

  1. 01Talk with Claude Code by voice
  2. 02Review followed conversations in the dashboard

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "noisy-noisy-coding": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "XAI_API_KEY",
        "docker.io/noisy/noisy-coding:2.13.3"
      ],
      "env": {
        "XAI_API_KEY": "<XAI_API_KEY>"
      }
    }
  }
}
Run commanddocker run -i --rm -e XAI_API_KEY docker.io/noisy/noisy-coding:2.13.3
Environment variables to set
XAI_API_KEYSecretxAI API key for Grok voice synthesis and transcription (configured once on the dashboard, stored in the config volume)

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
ocidocker.io/noisy/noisy-coding:2.13.3

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Noisy Studio

Talk to your coding agent while it works. Noisy Studio is a native desktop app with speech recognition, spoken replies, per-conversation voice and character settings, and a dashboard for the conversations you are following.

https://github.com/user-attachments/assets/331ca147-b325-4b89-9704-a3bba206f2f8

Install

Download the macOS Apple Silicon app from Releases, move Noisy Studio.app to Applications, and open it. Complete provider and audio setup in the app. The app includes its own Python engine; ordinary Claude installation needs neither Python nor a separate service manager.

For Claude Code, install the companion plugin:

claude plugin marketplace add noisy/noisy-studio
claude plugin install noisy-studio@noisy

Restart Claude Code and ask it to set up Noisy Studio voice. Keep the app and plugin versions together: the plugin launches the engine bundled with the app. The internal plugin name remains noisy-studio for compatibility.

Installation and troubleshooting covers permissions, providers, updates, and a spoken round trip. The Codex preview uses the same app and currently requires uv for its integration processes. macOS is the validated release platform; other platforms are source development.

Development

Use local development for the isolated daemon on 7765 and dashboard hot reload. The installed app owns 9765 and has separate settings. See desktop packaging for signed app builds.

  • Agent hooks
  • Ports
  • Product naming
  • Storybook - how the dashboard and the widget are meant to look, published from main. Run it locally with cd dashboard && npm run storybook. Its title shows the commit it was built from, so a story can be cited by URL and version.

API credentials belong in the app's provider settings, never in chat or source. Offline providers download their models on first use and then run locally.

Upgrading to the V3 technical names

V3 uses noisy-studio throughout packages, commands and integrations. Older installations need an explicit upgrade; see the agent-friendly upgrade and rollback guide before replacing an existing installation.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.