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.
@advenimus
Basic information
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
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"
}
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
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.
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.
Conduit ships a built-in MCP server that exposes every connection and credential operation as tools for AI agents — no other manager offers this.
No. Conduit does not include its own AI. You bring your own Claude Code or Codex subscription, and Conduit never proxies your API calls.
All credentials live in a local AES-256 encrypted vault. Cloud sync is optional and uses zero-knowledge encryption; keys never leave the client.
The MCP server communicates over a local Unix socket (or named pipe on Windows). Conduit never sees your API keys, tokens, or conversation content.
Yes. The entire desktop client — including the Electron app, protocol handlers, FreeRDP helper, MCP server, and credential vault — is Apache 2.0 licensed.

Location compliance records for multi-location businesses: sites, compliance fields, policies, SOPs and evidence files, with admin-controlled write approvals.

Multiplayer coding in the agentic era through an MCP server for real-time codebase sync between your agents.
Find the AI tells in your prose. Deterministic, local, runs in CI. MCP server + CLI + Action.

Read, find, update and add the leads in your TruLata account, and list your published blog posts, from any MCP client. AI marketing software for service businesses. Sign in with OAuth; nothing to paste.

Official MCP server for Taklo, all-in-one software for installation and maintenance companies in the Netherlands and Belgium (CRM, work orders, quotes, invoicing, VAT). Gives AI assistants live answers about Taklo's pric
Comments