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
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago