See all features
AI Integration

Your servers, accessible to AI

SSHive includes a built-in MCP server that lets Claude Code, Cursor, and Claude Desktop interact with your SSH and SFTP sessions — directly from your machine.

MCP Server ActiveAuto-configuredLocal & Secure
Download SSHiveSee setup
SSHive — Settings / MCP

MCP Server (Model Context Protocol)

Lets AI assistants (Claude, Cursor, Cline…) access active SSH sessions.

Enable MCP server
Starts a local HTTP server on 127.0.0.1
Active
Port
49422
Token Bearer
988ca074-565f-444a-918…
Auto-configured clients
Claude CodeCursorClaude Desktop
What is MCP?

Model Context Protocol — the bridge between AI and your infrastructure

MCP (Model Context Protocol) is an open standard created by Anthropic that allows AI assistants to interact with external tools and data sources. SSHive implements an MCP server that exposes your active SSH and SFTP sessions as tools — so Claude can execute commands, read files, and browse your remote servers without leaving the conversation.

Instant access

No copy-paste, no context switching. Your AI assistant directly queries your servers through SSHive's active sessions.

100% local

The MCP server runs on 127.0.0.1 with Bearer token authentication. Nothing leaves your machine — no cloud relay, no third-party proxy.

Zero configuration

Activate MCP in Settings and SSHive auto-configures Claude Code, Cursor, and Claude Desktop. Ready in seconds.

Claude Code — Terminal
claude>List all running Docker containers on my production server
Using SSHive MCP to access session "NMS"…
ssh_execute
session: "NMS"  command: "docker ps --format 'table {{.Names}}\t{{​.Status}}'"
Result
NAMES            STATUS
api-gateway      Up 14 days
web-frontend     Up 14 days
postgres-db      Up 14 days
Your production server has 3 containers running: api-gateway, web-frontend, and postgres-db — all up for 14 days with no issues.
SSH via AI

Execute commands through natural language

Ask Claude to check Docker containers, view logs, restart services, or run any command on your remote servers. SSHive's MCP server bridges the conversation to your live SSH sessions.

  • Claude picks the right session automatically from your active connections
  • Full stdout/stderr output returned directly in the conversation
  • Works with any SSH session — no special server-side setup needed
SFTP via AI

Browse and read remote files with AI

Claude can list directories, read configuration files, and even write files on your remote servers through SSHive's SFTP tools. Perfect for debugging config issues or reviewing logs.

  • List directory contents on any active SFTP session
  • Read remote files — configs, logs, scripts — directly in Claude's context
  • Write files back to the server for quick fixes
Claude Code — SFTP via MCP
claude>Show me the Nginx config for the API
sftp_list
session: "NMS"  path: "/etc/nginx/sites-enabled/"
sftp_read_file
session: "NMS"  path: "/etc/nginx/sites-enabled/api.conf"
server {
    listen 443 ssl;
    server_name api.example.com;
    location / {
        proxy_pass http://127.0.0.1:3000;
    }
}
Your API reverse proxy is configured on api.example.com (port 443) and forwards traffic to localhost:3000. The SSL configuration looks standard.
MCP Tools

5 tools for full server access

Each tool maps to a specific SSH or SFTP operation, giving AI assistants precise control over your remote servers.

ssh_list_sessions

Lists all active SSH sessions with host, user, port, and connection status.

ssh_execute

Executes a command on a specific SSH session and returns stdout/stderr.

sftp_list

Lists files and directories at a given path on a remote server.

sftp_read_file

Reads the content of a remote file and returns it as text.

sftp_write_file

Writes content to a file on the remote server.

Setup

Ready in 3 clicks

SSHive auto-configures your AI clients. For other tools, copy the JSON config below.

1

Open SSHive Settings

Navigate to Settings > MCP in the SSHive sidebar.

2

Enable the MCP server

Toggle the switch to activate the local MCP server on port 49422. A Bearer token is automatically generated.

Done — Claude Code, Cursor & Claude Desktop are auto-configured

SSHive writes the configuration to each client's settings file automatically. Just restart your AI client and you're connected.

Streamable HTTP (Claude Desktop, Cursor, Cline)
{
  "mcpServers": {
    "sshive": {
      "type": "http",
      "url": "http://127.0.0.1:49422/mcp",
      "headers": {
        "Authorization": "Bearer <your-token>"
      }
    }
  }
}
SSE — Server-Sent Events (legacy)
{
  "mcpServers": {
    "sshive": {
      "type": "sse",
      "url": "http://127.0.0.1:49422/sse",
      "headers": {
        "Authorization": "Bearer <your-token>"
      }
    }
  }
}
Compatible Clients

Works with your favorite AI tools

Claude CodeAuto

Full integration — auto-configured when MCP is enabled in SSHive.

CursorAuto

Auto-configured — SSHive writes to Cursor's MCP settings file.

Claude DesktopAuto

Auto-configured — seamless integration with Claude Desktop app.

Cline

Compatible via manual Streamable HTTP configuration.

Secure by design

The MCP server never exposes your sessions to the internet. Everything stays on your machine, protected by authentication and local-only binding.

Server binds to 127.0.0.1 only — not reachable from the network
Bearer token authentication on every request
Auto-generated cryptographic tokens
No cloud relay — direct local communication
Token regeneration with one click
MCP server can be disabled at any time

Give your AI superpowers

Download SSHive and connect Claude Code, Cursor, or Claude Desktop to your servers in seconds.

Download SSHiveSee all features