In-app MCP server
The In-app MCP server lets AI agents on your computer, such as Claude Code or Cursor, work with Routix Dash on your iPhone or iPad over the local network. They get the same tools as the in-app agent: they can read your configuration, add and change sources and data pieces, write transformers, and check logs.
The agent uses its own AI model. Routix Dash does not send anything to an AI provider for it; the agent connects to the app directly.
What you need
- Any plan. On Free, agents can make changes in 25 edit sessions per device. See Free plan limit and Plans.
- The agent's computer and your iPhone or iPad on the same local network. The server accepts agent connections even if you declined iOS's Local Network request; that permission only affects connections the app opens to devices on your network (see Local network access).
Turn it on
Open the menu → AI settings → In-app MCP server, and turn on MCP server. It is off until you turn it on.
The line under the switch shows the state:
- Green dot — the server is running. You also see the port and when the last request came, and from which address.
- Red dot — the server couldn't start. The reason is shown next to it.
- Gray dot — the server is off.
The server uses port 47302, and only that port. If another program already uses it, the app shows an error. To use a different port, tap Port.
Connect an agent
Tap Connect an agent. The screen lists the addresses of this device. Tap the one the agent's computer can reach, then choose:
- Copy Claude Code command — paste it into a terminal on the agent's computer.
- Copy JSON setup — add it to
.mcp.json, Cursor, or another MCP client. - Copy address — just the address, if you set up the client by hand.
The copied setups already contain the access token. A JSON setup looks like this:
{
"mcpServers": {
"routix-dash-ios": {
"type": "http",
"url": "http://192.168.1.20:47302/mcp",
"headers": { "Authorization": "Bearer <token>" }
}
}
}
Some clients can only run local commands. For them, use mcp-remote:
npx mcp-remote http://192.168.1.20:47302/mcp --allow-http --header "Authorization: Bearer <token>"
What agents can do
- The in-app agent's tools, plus the screen tools below. The agent can't show dialogs in the app. When it needs something from you, it asks in its own chat.
- Secrets stay on the device. Ask the agent to use ENV variables such as
env.api_key, and enter the values yourself in the app. - Live network actions follow AI permissions. Sending requests, refreshing a data source, or sending data out works only for the operations turned on in AI settings → AI permissions. The app can't ask you while an agent works, so everything else is refused.
- See the app screen. Turn on See and move the app screen in AI settings → AI permissions to let agents take screenshots of the app, scroll, and open any screen, including settings and editors. They can look and scroll, but they can't tap or type.
- Opening a screen doesn't change your configuration. A custom screen or bottom sheet runs its On open and On close actions, so the agent can open one only when Tap on screen is on too.
- Screenshots show everything on the screen, such as variable values, API keys, and live data. They go only to the connected agent.
- The agent never closes a sheet or dialog you opened, or a screen with unsaved changes; it asks you to.
- This works on every plan, uses no edit sessions, and works even when Allow configuration changes is off.
- Render previews. Turn on Render previews in AI settings → AI permissions to let agents draw a data piece, component, Freeform section, custom screen, or bottom sheet as a picture with live data, to check how it looks.
- The picture is drawn in the background: your screen doesn't change, and a custom screen or bottom sheet doesn't run its On open or On close actions. The pictures go only to the connected agent.
- The same setting lets the in-app assistant check its work (see AI assistant).
- Allow configuration changes. Turn it off to let agents only read the configuration and app state.
- Snapshots on request. Ask the agent to save a configuration snapshot and it appears in Settings → Configuration snapshots. Named snapshots need Pro. Saving one uses no edit session, and it's refused while Allow configuration changes is off.
- No configuration export. Agents are told not to show, export, or import your configuration; use Settings → Configuration export / import for that. An agent still reads the configuration to change it, so connect only agents you trust.
Changes from an agent apply and save right away, like your own edits. Before the first change of a session, the app saves a checkpoint named MCP: before agent edits. You find it in the history of the in-app agent, and the agent can restore it too. While the in-app agent is working, changes from MCP agents are refused; they can try again when it finishes.
At the end of its work the agent can add a short summary to that checkpoint. Tap the checkpoint and choose Summary to see what was done and which problems came up. If the agent writes none, the summary lists the changes it made.
Free plan limit
On Free, agents can read without limit: configuration, status, logs, and help. Changes to the configuration are limited to 25 edit sessions per device.
- A session starts with the agent's first change, or with a checkpoint it creates.
- The session lasts until the agent stops changing things for 10 minutes.
- Undoing with a checkpoint restore does not use a session.
- The count is kept on this device only.
While the server is on, AI settings → In-app MCP server shows Remaining edit sessions: X of 25. When none are left, changes are refused. The agent gets the message "Free plan: all 25 MCP edit sessions are used. Pro removes the limit." Reading still works.
Pro has no edit limit.
Safety
- The connection uses plain HTTP protected by a token. Anyone on the same network who sees the traffic can read the token, so turn the server on only on networks you trust.
- If the token gets out, open Connect an agent → Regenerate token. Connected agents then need the new setup.
- The server pauses while the app is in the background and starts again when you return to the app.
- Turn the server off when you don't need it.