Skip to content

Workspaces ​

A workspace is one project directory exposed to AI clients: file I/O, command execution, search and diagnostics inside it are open; outside it, paths are read-only or invisible by default. Each workspace has its own UUID endpoint.

Add and remove ​

Panel (recommended): "Workspaces" card → Add → type an absolute path or browse to it (folders can be created inline); an optional display name can be set.

Command line:

bat
aeasymcp workspace add D:\Projects\demo
aeasymcp workspace list
aeasymcp workspace remove <uuid>

At least one workspace must remain. Removing a workspace never deletes anything on disk.

Management ​

Each workspace entry supports:

  • Enable / disable: a disabled workspace's /mcp/<uuid> returns 404; re-enabling restores it;
  • Rename: changes the display name only, never the endpoint;
  • Repoint: point the workspace at a new directory while keeping the UUID — client configurations need no change;
  • Delete: remove it from the registry (files untouched).

All changes take effect immediately while the service runs — no restart needed.

The launch directory is never auto-registered ​

Starting the program from any directory (double-click, home, desktop) does not register that directory as a workspace. Workspaces are added only via the panel, workspace add, or an explicit flag:

bat
:: Explicitly select and register a workspace (when that is what you want)
aeasymcp serve -workspace D:\Projects\demo

This is a deliberate safety design: sensitive paths like your home directory are never accidentally exposed.

Single-instance behavior ​

While the service is already running, launching the program again:

  • Without arguments: prints a notice with the panel address and exits — it does not register the current directory and does not start a competing instance;
  • With -workspace <path>: forwards that directory to the running instance and prints its endpoint;
  • With -new-instance: forces a separate copy (for testing builds; port conflicts fail loudly).

How multiple workspaces work ​

All registered workspaces share one listening port (default 18765), routed by UUID:

http://127.0.0.1:18765/mcp/<uuid-A>   → workspace A
http://127.0.0.1:18765/mcp/<uuid-B>   → workspace B
  • Give different clients (or sessions) different workspaces for natural isolation;
  • Unknown UUIDs return 404;
  • In public mode each workspace is an independently recyclable route (see Public Access); your tier sets the minimum retained count.