GameCult/AquaSynth
Watch
9
0
Fork
You've already forked AquaSynth
 0
Code Issues Pull requests 4 Projects Releases Packages Wiki Activity Actions

Document shared Dings MCP deployment boundary

Browse source
This commit is contained in:
Meta Vens 2026-08-21 21:00:57 +02:00
commit e02faf6c92
1 changed files with 7 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

7
tools/AquaSynthDingsMcp/README.md
View file

@ -8,6 +8,13 @@ All MCP instances are command bridges. One persistent
Aqua synthesis child, mixer, master volume, and mute state. Windows Volume Aqua synthesis child, mixer, master volume, and mute state. Windows Volume
Mixer and MCP volume tools address the same session. Mixer and MCP volume tools address the same session.
Do not register this STDIO bridge globally in an agent harness that creates a
separate MCP client for every root agent, subagent, or critic. STDIO ownership
means one resident .NET bridge per client even though audio authority is already
shared by `AquaSynthDingsHost.exe`. Keep the bridge disabled in that topology,
use the direct CLI for local smokes, or expose one supervised Streamable HTTP MCP
server when notifications need to be available across many concurrent agents.
```powershell ```powershell
dotnet run --project tools/AquaSynthDingsMcp dotnet run --project tools/AquaSynthDingsMcp
``` ```