MCP Server Setup #

Overview #

Model Context Protocol (MCP) servers extend AI assistant capabilities by providing direct access to external tools and services. This project uses multiple MCP servers for development workflow automation.

Configured MCP Servers #

1. Supabase MCP #

Purpose: Database management, schema inspection, SQL queries, RLS policy management

Configuration:

{
  "supabase": {
    "command": "npx",
    "args": [
      "mcp-remote",
      "https://mcp.supabase.com/mcp?project_ref=lgdzajifbikspcyqymat"
    ]
  }
}

Capabilities:

• Query database schema and tables
• Execute SQL queries
• Inspect RLS policies
• Manage Edge Functions
• View migration history
• Check database advisors (security/performance)

Authentication: OAuth flow via browser on first use

Documentation: https://supabase.com/docs/guides/getting-started/mcp

2. Netlify MCP #

Purpose: Deployment management, site configuration, environment variables

Configuration:

{
  "netlify": {
    "command": "npx",
    "args": [
      "-y",
      "@netlify/mcp"
    ]
  }
}

Capabilities:

• Create and deploy projects
• Manage environment variables
• Configure access controls
• Install/uninstall extensions
• Manage form submissions
• Fetch user and team information

Prerequisites:

• Node.js 22+
• Netlify CLI installed: npm install -g netlify-cli

Authentication: Uses Netlify CLI authentication

Documentation: https://docs.netlify.com/build/build-with-ai/netlify-mcp-server/

3. Playwright MCP #

Purpose: Browser automation and E2E testing

Configuration:

{
  "playwright": {
    "args": [
      "@playwright/mcp@latest",
      "--extension"
    ],
    "command": "npx",
    "disabled": false,
    "env": {
      "PLAYWRIGHT_MCP_EXTENSION_TOKEN": "oOpnWL_5j63pBvmyGCnhpo-JBbE-7SpM15hWv7pW8vw"
    }
  }
}

Capabilities:

• Navigate and interact with web pages
• Take screenshots
• Fill forms
• Click elements
• Execute JavaScript
• Capture console logs and network requests

4. GitHub MCP #

Purpose: GitHub repository management, issues, PRs, workflows

Configuration:

{
  "github": {
    "serverUrl": "https://api.githubcopilot.com/mcp/",
    "headers": {
      "Authorization": "Bearer YOUR_GITHUB_PAT"
    }
  }
}

Capabilities:

• List and search repositories
• Create, read, update issues
• Manage pull requests
• Search code and commits
• Create and manage branches
• Read and write files
• Manage GitHub Actions workflows
• Create gists

Prerequisites:

• GitHub Personal Access Token with appropriate scopes

Setup Instructions: See @/Users/alex/Documents/RetroComputerDD/docs/GITHUB_PAT_SETUP.md

Documentation: https://github.com/github/github-mcp-server

5. Testiny MCP #

Purpose: Test management integration

Configuration:

{
  "testiny": {
    "args": [
      "mcp-remote",
      "https://testiny.dotsource.de/api/v1/mcp-server"
    ],
    "command": "npx",
    "env": {
      "AUTHORIZATION": "Bearer tny_aJB7eg1OZ3jD9AWVMGwzqkqQEWFQUo6OAZ2sax8rV2G8dcfu"
    }
  }
}

Installation #

Windsurf Configuration #

MCP servers are configured in: ~/.codeium/windsurf/mcp_config.json

Backup location: @/Users/alex/Documents/RetroComputerDD/.mcp-config-backup.json

Setup Steps #

1. Install prerequisites:

   # Netlify CLI (required for Netlify MCP)
   npm install -g netlify-cli
   
   # Supabase CLI (already installed)
   npm install -g supabase

2. Restart Windsurf to load MCP servers

3. Authenticate services:

   • Supabase: Browser OAuth flow on first use
   • Netlify: Uses existing CLI authentication (netlify login)
   • Playwright: Token pre-configured
   • Testiny: Token pre-configured

4. Verify connection:

   • Open Windsurf Settings → Tools & MCP
   • Check all servers show as "Connected"

Usage Examples #

Supabase MCP #

"Show me all tables in the database"
"What RLS policies exist on the members table?"
"Execute: SELECT COUNT(*) FROM profiles"
"Check for security advisors"

Netlify MCP #

"List all environment variables for this site"
"Deploy the current project"
"Show me the latest deploy logs"
"Add environment variable FEATURE_FLAG=true to preview context"

Playwright MCP #

"Navigate to localhost:8080 and take a screenshot"
"Fill the login form with test credentials"
"Click the submit button and wait for navigation"

Troubleshooting #

MCP Server Not Connected #

1. Check Windsurf Settings → Tools & MCP
2. Restart Windsurf
3. Verify Node.js version: node --version (need 22+ for Netlify)
4. Check logs in Windsurf Developer Tools

Supabase Authentication Issues #

# Re-authenticate
supabase login

# Verify project link
supabase link --project-ref lgdzajifbikspcyqymat

Netlify Authentication Issues #

# Re-authenticate Netlify CLI
netlify logout
netlify login

# Verify authentication
netlify status

Node Version Issues #

Netlify MCP requires Node.js 22+. Check version:

node --version

If needed, update via nvm:

nvm install 22
nvm use 22

Security Considerations #

• Never connect MCP to production data in CI environments
• MCP servers have full access to configured services
• Tokens and credentials are stored in Windsurf config
• Use preview/staging environments for testing
• Review MCP actions before confirming destructive operations

Backup and Recovery #

Backup location: ~/.codeium/windsurf/mcp_config.json.backup

Restore backup:

cp ~/.codeium/windsurf/mcp_config.json.backup ~/.codeium/windsurf/mcp_config.json

Project backup: @/Users/alex/Documents/RetroComputerDD/.mcp-config-backup.json

Resources #

• Model Context Protocol Docs
• Supabase MCP Docs
• Netlify MCP Docs
• Windsurf MCP Docs
• MCP Client List