@intentwake/mcp

@intentwake/mcp

Local stdio MCP bridge for complete IntentWake file transfers.

The bridge exposes three semantic tools:

• upload_list_file streams an allowed local file into a canonical IntentWake list.
• append_list_file streams an allowed local file into a canonical append session.
• download_result_to_file saves an already-unlocked NDJSON or CSV result artifact locally. It never unlocks or charges.

File bytes move directly between the local process and IntentWake transfer endpoints. They do not enter MCP arguments, results, or model context.

Requirements

• Node.js 22 or newer.
• An IntentWake connection token with the scopes needed by the tools you call.
• One or more absolute local roots that you explicitly approve.

Configure

Run the server with:

npx -y @intentwake/mcp

Configure these values in your MCP client's user-level secret/environment settings, not in a project or tracked file and not as visible command arguments:

• INTENTWAKE_CONNECTION_TOKEN: the IntentWake connection bearer.
• INTENTWAKE_ALLOWED_ROOTS: approved absolute roots separated by : on macOS/Linux or ; on Windows.
• INTENTWAKE_MCP_URL: optional hosted control-plane URL override.
• INTENTWAKE_API_URL: optional public API URL override used for canonical CSV streams.

With no allowed roots configured, every file operation is refused. There are no implicit current directory or Downloads defaults.

File safety

Source paths resolve to real paths inside an approved root and must be regular files. Directories, devices, outside paths, and symlink escapes are refused. Upload and append parts stream in bounded byte ranges and resume the same hosted session with the same idempotency key if transfer URLs expire.

Downloads default to overwrite=false. The bridge writes a unique sibling temporary file, computes byte count and SHA-256 while streaming, verifies expectations supplied by IntentWake, and atomically installs the completed file. Partial temporary files are removed after failures. If the bound destination directory moves outside its configured root during a transfer, the in-progress temporary file moves with that directory. The bridge rechecks directory identity and root ancestry before streaming, after staging, and at installation; it removes the temporary file through the bound directory and returns destination_changed without installing a result.

NDJSON downloads use an already-authorized result artifact URL. CSV downloads stream the existing authenticated IntentWake CSV response; the bridge does not transform result rows locally. Locked artifacts fail closed and must be unlocked separately through an explicit IntentWake operation.

The hosted HTTP MCP endpoint remains available for clients without local filesystem access.