Hoo MCP — AI Music Production Assistant

io.github.kimny1143Published by GitHub account kimny1143v1.1.0Updated Oct 24, 2026

AI music production assistant — audio profiling, AI mixing sessions, and service inquiries.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Remote MCP server for AI music production: audio profiling, AI mixing sessions, and service inquiries.

What you can do
  • Profile audio tracks to analyze their sound characteristics.
  • Run AI-assisted mixing sessions on submitted audio.
  • Send and handle service inquiries related to music production.
When to use it
Useful when an assistant should help with music production work such as analyzing audio, running AI mixing sessions, or handling production service inquiries, without building that tooling locally.
Requirements
Remote streamable HTTP endpoint; no local package or runtime. Requires bearer authentication: an API key sent in the Authorization header, generated through the provider's connect page. Network access to the hosted endpoint.
Before you install
The server requires an API key in the Authorization header; treat it as a secret and keep it out of shared logs. Audio you submit is sent to a third-party hosted service for profiling and mixing, so avoid uploading material you cannot share externally. Inquiries may send messages on your behalf.

Installation

In SourceWeft

  1. Open Hoo MCP — AI Music Production Assistant in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.kimny1143%2Fhoo-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "hoo-ai-music-production-assistant": {
      "type": "http",
      "url": "https://hoo-mcp.glasswerkskimny.workers.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.