@customaise/mcp 3.1.0 — chat clients can read what they ask for

The release that makes chat clients first-class, and the sync that makes this repository real.

output: "file" | "inline" | "auto" on the context tools

get_page_context and get_console_context spool their full payload to a workspace file and return a summary plus the path. Right for an IDE agent; a dead end in a chat client, whose model has no file tools to open what was written. All three context tools (screenshot included) now take output: inline returns the whole payload in the response, with the screenshot arriving as an MCP image block. auto follows CUSTOMAISE_MCP_OUTPUT, which the .mcpb bundle presets for Claude Desktop. No client sniffing: every file-mode response carries the retry instruction, and in live testing the model selected inline from the tool descriptions alone.

Also in 3.1.0

• All 19 tools declare all four annotation hints honestly; tools that write files say so.
• An unwritable workspace falls back to inline delivery instead of discarding a result a cap unit already paid for.
• An empty capture fails instead of writing a zero-byte PNG marked success; non-PNG captures are no longer corrupted.
• Oversized inline payloads are shortened by trimming lists, never by truncating JSON.
• ws 8.21.3, clearing CVE-2026-45736 and CVE-2026-48779.
• The customaise CLI forwards CUSTOMAISE_MCP_OUTPUT from the invoking shell; shot -o FILE always writes the file it was asked for.

This repository is now the complete package

Previous syncs hand-copied a subset; this one ships every source file, all 37 test suites, the lockfile, and the .mcpb build, kept honest by scripts/sync-public-mirror.mjs. The 3.0.0 release (the customaise terminal control plane, the MCP 2026-07-28 revision, get_bridge_status) is covered in CHANGELOG.md.

Install: npx -y @customaise/mcp · npm: @customaise/mcp@3.1.0 · Claude Desktop: customaise.mcpb