Practice in the browser with WebMCP
The interactive desktop is a simulation. When your browser and AI client support the experimental WebMCP API, SlidePane exposes three tools on the demo page. These tools only inspect and change simulated windows; they cannot reach your real Mac windows, installed apps or licence.
slidepane_demo_inspect: Read the available practice desktops and their current window and layout state.slidepane_demo_action: Choose a practice desktop by demoId, run a supported layout command, select a simulated window or set its window gap. For an add command, appKind chooses Code (0), Notes (1), Browser (2) or Music (3).slidepane_demo_scenario: Switch a practice desktop to a supported scenario such as horizontal, vertical, stacks, monitors, profiles or shortcuts.
WebMCP support is experimental and depends on the browser and client. The integration uses document.modelContext, with a navigator.modelContext fallback for earlier implementations. Where that API is unavailable, the demo still works through its standard buttons and keyboard controls. Computer-use assistants can use the visible controls and semantic labels.
Connect local MCP to the Mac app
The local MCP bridge is a separate Node script in the SlidePane source checkout: scripts/slidepane-mcp.mjs. It runs over stdio, opens no network listener and does not add itself to an AI client. Configure it explicitly in the client you want to use.
- Install Node 20 or newer on macOS and obtain the SlidePane source checkout containing scripts/slidepane-mcp.mjs.
- Install the current SlidePane app, grant Accessibility access, and enable window management yourself. The app needs an active free trial or licence.
- In your client’s documented MCP configuration, launch Node with the absolute path to scripts/slidepane-mcp.mjs. Use an absolute Node executable path too if the client does not inherit your terminal PATH.
- Read workspace status, choose an existing window ID, then request a supported arrangement. Read status again to verify its effect before chaining dependent actions.
{
"mcpServers": {
"slidepane": {
"command": "node",
"args": ["/absolute/path/to/your-checkout/scripts/slidepane-mcp.mjs"]
}
}
}This is an example of the common JSON client configuration format. Replace the path with your checkout. Configuration locations depend on your client. The bridge supports initialize-based MCP revisions 2025-11-25, 2025-06-18, 2025-03-26 and 2024-11-05; clients supporting only the newer 2026-07-28 protocol need a compatible bridge. Full setup and capabilities are in docs/AI_AUTOMATION.md in the checkout.
slidepane_status: Read management status, existing window IDs and app names, displays, groups, focus and undo availability.slidepane_arrange: Request focus, movement, resizing, centering, stacking, tabs, direction changes, transfer to the next display, undo or pause-and-restore. Arrangement requires running, unpaused management; the native app also checks that its free trial or licence is active.
A successful arrangement result means the request was dispatched, not that the window has moved: status is "dispatched" and confirmed is false. App delivery and layout updates are asynchronous. Read status again to verify the effect, particularly after focusing a window and before resizing it.
What the local bridge shares
The bridge exposes app names, bundle identifiers, window IDs and layout geometry to the connected MCP client. It excludes document titles, document contents, screenshots, licence keys, profiles and configuration rules. The bridge makes no network requests; your AI client determines how it handles the returned workspace data.
The bridge cannot start or resume window management, enter a licence key, buy a licence, launch another app or run arbitrary shell commands. You stay in control of enabling management. Its pause action can ask SlidePane to restore the original window positions.
Automation questions
Can the browser demo arrange my real Mac windows?
No. Browser WebMCP tools operate only on the website’s simulated desktop. Native window arrangement requires the installed Mac app and a separately configured local MCP client.
Does every browser or AI assistant support WebMCP?
No. WebMCP is experimental and support varies by browser and client. Standard demo buttons, keyboard controls and semantic labels remain available for people and computer-use assistants.
Does installing SlidePane connect it to my AI client?
No. Configure the local Node MCP bridge explicitly in your client. It uses stdio and does not install client settings or open a network listener.
Does a successful MCP action confirm that a window moved?
No. The native bridge reports dispatch separately from execution. Read workspace status again to verify the requested change before sending an action that depends on it.