Ewe Suite

One standard for assistants and scripts

Ewe Paint, Ewe Write and Ewe Sound share the same MCP connections and command-line options. Each app supplies its own editing commands. Commands work in the live editor, with its normal state and undo history.

Help is included with every app

Each Windows installation includes AGENTS.md, the full tools.json command catalogue, cli-help.txt and ewe-cli.ps1 beside the executable. The CLI needs PowerShell 5.1 or later; it needs no Node.js or AI client installation.

ewepaint.exe --help
ewewrite.exe --help
ewesound.exe --help
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\ewe-cli.ps1 -Help

Each executable also accepts --version, --guide and --list. Help and command discovery work while the app is closed. In PowerShell, pipe executable output to Out-String when needed. The corresponding script options are -Guide and -List.

Use the command line

Run these commands from the chosen app's installation folder:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\ewe-cli.ps1 -Launch -Tool get_state
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\ewe-cli.ps1 -Tool history -ArgumentsFile C:\path\history.json
powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\ewe-cli.ps1 -Tool NAME -ArgumentsFile C:\path\arguments.json

-Launch opens the app if closed. Without it, the CLI attaches to or enables an existing editor. Calls leave it open. Results are JSON; exit code 0 means success and 1 means failure. Read the app's guide before editing or saving files. Use an arguments file for reliable JSON input from any shell; for this history example, history.json contains {"action":"list"}.

Connect through MCP

For a client-owned editor, configure the app's installed executable as the MCP command with arguments ["--mcp"]. This uses stdio in an isolated window, which closes when the client disconnects.

To control an existing window, run its executable with --agent, then connect a Streamable HTTP MCP client to its local endpoint. The app keeps its current work.

AppDefault HTTP endpointCommands and guide
Ewe Painthttp://127.0.0.1:47816/mcpAgent help · Schemas
Ewe Writehttp://127.0.0.1:47817/mcpAgent help · Schemas
Ewe Soundhttp://127.0.0.1:47818/mcpAgent help · Schemas

--mcp-http=PORT selects a custom port at initial launch; pass that port to the CLI with -Port. MCP tools/list and CLI -List use the same catalogue. MCP guide, executable --guide and CLI -Guide return the same manual.

Normal launches leave local access off. Enabling MCP lasts for that session and is restricted to the local computer. Disable it in the app's agent help, close the app, or call agent_control with {"enabled":false}. Read guide and get_state first and preserve unsaved work.