Connecting other AI apps

Dax can hand your board to a different AI app instead of answering itself. Deskboard runs a small server that other apps connect to, and that app then gets the same abilities Dax has on that board.

This works with any app that supports MCP, including Claude Code, Codex and Gemini CLI.

Note

The other app has to be running on the same computer. This is a local connection and nothing is exposed to the internet.

Turning it on

1. Open Provider settings from the top of the Dax panel and go to the MCP Server tab.
2. Leave the Port as it is unless something else on your machine is already using it. The default is 41436.
3. Save. The Dax panel becomes a server view rather than a chat.
4. Click Start Server.

The panel shows whether the server is running, along with the address to connect to. Use the copy button beside it and paste that into the other app’s MCP configuration.

One address per board

Each board gets its own address, named after the board:

http://localhost:41436/my-project

Several boards can be served at once, each on its own address. The board has to be open in Deskboard for its address to answer.

What the other app can do

The same things Dax can:

• List and search your files
• Read documents, spreadsheets, presentations and code
• Create and edit files
• Add, change and remove widgets, and rearrange the board

Changes still come to you

Connecting another app does not hand over control of your files.

File edits are staged exactly as they are for Dax itself, and board changes arrive with a keep or undo waiting. The review cards appear in the Deskboard panel, and you accept or reject them there. See Reviewing changes.

While a review is waiting, the connected app cannot do anything else until you decide. It is told that it is waiting on you.

Turning it off

Stop Server in the same panel. Starting and stopping is per board.