MCP SSH Server for Windsurf

Created By
yoi-hibinoa year ago
MCP SSH server for Windsurf integration
Overview

what is MCP SSH Server for Windsurf?

MCP SSH Server for Windsurf is a Model Context Protocol (MCP) compatible SSH server designed for seamless integration with the Windsurf IDE, enabling efficient SSH operations.

how to use MCP SSH Server for Windsurf?

To use the MCP SSH Server, clone the repository, install the required dependencies, configure your SSH connection settings in the Windsurf MCP configuration file, and run the server using Python.

key features of MCP SSH Server for Windsurf?

  • Full MCP protocol support for SSH operations
  • Auto-connect to predefined SSH servers
  • Interactive terminal interface for SSH sessions
  • Support for both password and key-based authentication
  • Compatible with Windsurf IDE through MCP integration

use cases of MCP SSH Server for Windsurf?

  1. Facilitating SSH connections for development environments.
  2. Managing remote servers through the Windsurf IDE.
  3. Executing commands on remote servers seamlessly.

FAQ from MCP SSH Server for Windsurf?

  • What are the requirements to run the MCP SSH Server?

You need Python 3.7 or higher, along with Flask and Paramiko libraries.

  • How do I troubleshoot connection issues?

Ensure that the MCP endpoints are correctly configured and that the server is running on the specified port.

  • Can I use this server with other IDEs?

This server is specifically designed for integration with Windsurf IDE.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yoi-hibino
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago