Skip to Content
BlogL’agent passe par le MCP local

Agents call plans on this computer

You already edit the site in Cursor, then switch to Image Optimizer to click a plan. Version 2.0.5 on 13 September 2026 hands saved plans to local MCP. The agent talks. This computer exports.

Local MCP
One sentence
upsert_plansave plan
Run locally

Cursor, Claude, or VS Code call saved plans over local MCP. Image bytes never enter the chat.

What it does and does not

Does: get_status, list_plans, upsert_plan, optimize_paths, cancel_optimize, ping. Say what you need. The host model maps format, quality, and target size onto a whitelist. This computer validates and patches the plan. Copy the chat install prompt from Settings → Integration.

Does not: an in-app chat box that writes plans. That path was rejected. It also does not expose set_settings, licensing, or image bytes to the agent.

The app must stay running (minimized is fine). Integration defaults off. Quota is the same 300 as the window and watch folders. See Plans.

Do not

  • Do not read picture bytes into the chat “so the model can see quality.”
  • Do not fake the server with stdio or npx. Transport is local HTTP.
  • Do not rename the six built-in plans. Built-in ids are read-only. Save a copy.

Back to the map. Daily loop: Compress without uploading.

Dernière mise à jour