Migrating from Local MCP to Remote MCP

Remote MCP lets AI clients access Dessix even when the local App is not open. Local MCP can continue to work, but Remote MCP is the recommended path going forward.

What Changes

Item	Local MCP	Remote MCP
Runtime	Electron local process	Dessix server
App required	Yes	No
Authentication	Local App bridge	Access token
Data source	Local App data	Dessix cloud data
Tool names	dessix_*	dessix_*
Function signatures	Local MCP schema	Compatible with Local MCP

Compatibility

Remote MCP keeps the existing tool names and input schemas:

• dessix_list_workspaces
• dessix_get_current_workspace
• dessix_search_blocks
• dessix_read_block
• dessix_create_block
• dessix_update_block
• dessix_delete_block
• dessix_restore_block
• dessix_create_folder
• dessix_rename_folder
• dessix_move_folder
• dessix_delete_folder
• dessix_move_block
• dessix_list_folder_children

These tools cover workspaces, content blocks, and folders.

Migration Steps

1. Create an access token from the Dessix App workspace settings advanced panel.

2. Add a new Remote MCP server in your MCP client.

3. Set the endpoint to:

   https://api.dessix.io/v1/mcp

4. Add the request header:

   Authorization: Bearer dx_live_xxx

5. Keep your existing tool arguments unchanged.

6. Verify the connection with dessix_list_workspaces and dessix_get_current_workspace.

7. Verify data access with dessix_search_blocks or dessix_read_block.

Workspace Rules

If workspace_id is omitted, Remote MCP uses the most recently opened workspace recorded on the server. If the user has never created a workspace, it returns NO_WORKSPACE_SELECTED.

Behavior Changes

• Remote MCP does not depend on the current App page.
• Remote writes sync back to Dessix.
• Remote writes use server-side permission checks and can only access the token owner's data.
• Folder deletion matches the Dessix App: the target folder and sub-folders are deleted, and their content moves to trash.
• Oversized content is truncated and marked with truncation fields.

Rollback

You can keep Local MCP as a fallback during migration. Both can coexist, but new configurations should prefer Remote MCP.