Windsurf MCP Configuration

Created By
danilopezmellaa year ago
Configuration and setup files for using Model Control Protocol (MCP) servers with Windsurf in an SSH environment
Overview

What is Windsurf MCP Configuration?

Windsurf MCP Configuration is a repository that provides configuration and setup files for using Model Control Protocol (MCP) servers with Windsurf in an SSH environment.

How to use Windsurf MCP Configuration?

To use this project, follow the setup instructions provided in the documentation located in the docs directory. You will need to configure the MCP servers as per the guidelines.

Key features of Windsurf MCP Configuration?

  • Configuration files for various MCP servers including Perplexity, Context7, Sequential Thinking, Brave Search, and GitHub.
  • Detailed documentation for environment setup, file transfers, and MCP server configuration.
  • Helper scripts for starting and managing MCP servers.

Use cases of Windsurf MCP Configuration?

  1. Setting up advanced search capabilities using the mcp-perplexity-search server.
  2. Retrieving library documentation with the context7 server.
  3. Performing complex problem-solving with the sequential-thinking server.
  4. Conducting web and local searches using the brave-search server.
  5. Interacting with GitHub repositories through the GitHub MCP server.

FAQ from Windsurf MCP Configuration?

  • What are the requirements to use this project?

You need Node.js (installed via NVM), Docker (for GitHub MCP server), and various NPM packages for MCP servers.

  • Where can I find the setup instructions?

The setup instructions are available in the docs directory of the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
danilopezmella
Star
0
Language
Shell
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)

2 days ago