Conduit Desktop
@advenimus
About Conduit Desktop
Cross-platform remote connection manager (SSH, RDP, VNC, web) with a built-in MCP server exposing 60+ tools. Connect Claude Code or Codex to your infrastructure and let AI agents execute commands in SSH terminals, take screenshots of RDP/VNC desktops, drive web sessions, and read
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"conduit": {
"command": "node",
"args": [
"/Applications/Conduit.app/Contents/Resources/mcp/dist/index.js"
],
"env": {
"CONDUIT_SOCKET_PATH": "/Users/YOUR_USERNAME/Library/Application Support/conduit/conduit.sock",
"CONDUIT_ENV": "production"
}
}
}
}Tools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is Conduit Desktop?
Conduit Desktop is a cross-platform remote connection manager for SSH, RDP, VNC, and web sessions, packaged with an encrypted credential vault and a built-in Model Context Protocol (MCP) server. It allows AI agents like Claude Code or Codex to drive all connection, session, and credential operations through tool calls, making it an infrastructure bridge for DevOps, SREs, sysadmins, and AI-first engineers.
How to use Conduit Desktop?
Install the app from GitHub Releases or conduitdesktop.com, then register its MCP server with your AI agent. For Claude Code, run a command like claude mcp add conduit -- node "/Applications/Conduit.app/Contents/Resources/mcp/dist/index.js" --env CONDUIT_SOCKET_PATH="..." --env CONDUIT_ENV="production" (paths vary by OS). After setup, ask your agent to list connections, run commands, or interact with remote desktops — the agent communicates with Conduit over a local Unix socket or Windows named pipe.
Key features of Conduit Desktop
- Multi-protocol support: SSH, RDP, VNC, web sessions in one app
- Built-in MCP server with 60+ tools for AI agents
- Encrypted AES-256 credential vault with auto-lock
- In-app agent chat panel for Claude Code and Codex
- Local-first design; optional zero-knowledge team vaults (Pro)
- Import from Devolutions Remote Desktop Manager and Conduit exports
- Cross-platform macOS, Windows, Linux with OS-native themes
Use cases of Conduit Desktop
- Ask an AI agent to run commands over SSH on production servers
- Automate RDP/VNC remote desktop operations like clicking and typing
- Fill web forms and navigate intranet portals through an AI agent
- Manage a fleet of servers with shared, approval-gated credential access
- Build custom workflows using the MCP server from any MCP-compatible client
FAQ from Conduit Desktop
How is Conduit different from other remote connection managers?
Conduit ships a built-in MCP server that exposes every connection and credential operation as tools for AI agents — no other manager offers this.
Does Conduit ship its own AI or require an additional subscription?
No. Conduit does not include its own AI. You bring your own Claude Code or Codex subscription, and Conduit never proxies your API calls.
Where are credentials stored?
All credentials live in a local AES-256 encrypted vault. Cloud sync is optional and uses zero-knowledge encryption; keys never leave the client.
What transport does the MCP server use?
The MCP server communicates over a local Unix socket (or named pipe on Windows). Conduit never sees your API keys, tokens, or conversation content.
Is the Conduit Desktop client open source?
Yes. The entire desktop client — including the Electron app, protocol handlers, FreeRDP helper, MCP server, and credential vault — is Apache 2.0 licensed.
Frequently asked questions
How is Conduit different from other remote connection managers?
Conduit ships a built-in MCP server that exposes every connection and credential operation as tools for AI agents — no other manager offers this.
Does Conduit ship its own AI or require an additional subscription?
No. Conduit does not include its own AI. You bring your own Claude Code or Codex subscription, and Conduit never proxies your API calls.
Where are credentials stored?
All credentials live in a local AES-256 encrypted vault. Cloud sync is optional and uses zero-knowledge encryption; keys never leave the client.
What transport does the MCP server use?
The MCP server communicates over a local Unix socket (or named pipe on Windows). Conduit never sees your API keys, tokens, or conversation content.
Is the Conduit Desktop client open source?
Yes. The entire desktop client — including the Electron app, protocol handlers, FreeRDP helper, MCP server, and credential vault — is Apache 2.0 licensed.
Basic information
More Productivity MCP servers
Todoist MCP Server
greirsonMCP server that connects Claude to Todoist for natural language task and project management with bulk operations
ATLAS: Task Management System
cyanheadsA Model Context Protocol (MCP) server for ATLAS, a Neo4j-powered task management system for LLM Agents - implementing a three-tier architecture (Projects, Tasks, Knowledge) to manage complex workflows. Now with Deep Research.
Computer Control MCP
AB498MCP server that provides computer control capabilities, like mouse, keyboard, OCR, etc. using PyAutoGUI, RapidOCR, ONNXRuntime. Similar to 'computer-use' by Anthropic. With Zero External Dependencies.
Sitespeak Claude Plugin
sitespeakaiManage your SiteSpeakAI chatbot from Claude Code - a plugin and MCP server for optimizing chatbots in plain English.
Desktop Commander MCP
wonderwhy-erThis is MCP server for Claude that gives it terminal control, file system search and diff file editing capabilities
Comments