MCP on Desktop
On RealTimeX Desktop, a Local MCP server runs on your device.
Open MCP management from Settings > Agents > MCP Servers, then switch to the Local MCP tab.
When Desktop local MCP is the right choice
Use Desktop local MCP when:
- the server should run directly on your computer
- the MCP package expects local commands such as
npx,uvx,node, or another installed runtime - the tools need access to files or services that are reachable from your machine
If the provider already hosts the server for you, use the Remote MCP tab instead.
What you can do in the UI
The current Desktop flow supports:
- browsing suggested local server entries
- adding a custom local MCP server
- importing or editing the server configuration
- filling placeholder fields for templated servers
- testing the connection before saving
- enabling or disabling the server
- reviewing discovered tools
- enabling only selected tools
Command availability still matters
RealTimeX Desktop manages the MCP server record, but it does not magically install every external dependency for you.
If a local MCP server depends on a command such as npx, uvx, node, or another binary, that command still needs to exist on your machine and be usable from the RealTimeX environment.
If a server fails to connect, verify:
- the required runtime is installed
- the command path is correct
- any URLs, headers, or env-style values in the config are valid
Typical setup flow
- Open
Settings > Agents > MCP Servers. - Choose
Local MCP. - Pick a suggested server or click
Add Local MCP Server. - Import or edit the configuration.
- Fill placeholder fields if the template asks for them.
- Run the connection test.
- Save the server.
- Enable the server if it is not already enabled.
- Review the tool list and disable anything you do not want exposed.
- Assign the server in workspace or agent configuration.
Using local MCP from agents
Adding a local MCP server to Desktop does not automatically expose it everywhere.
After setup, assign it in the relevant workspace or agent configuration so the agent can actually call those tools.
See Agent Setup for the assignment side of that flow.
Troubleshooting on Desktop
- If no tools appear, confirm the server is both configured and enabled.
- If a tool list fails to load, re-run the connection test and check the server definition.
- If an agent does not call the tool, confirm the server is assigned to that workspace or agent context.
- If auth is the blocker, you may need a remote server connection instead of a local one.