Get the FREE Ultimate OpenClaw Setup Guide →

Vibe-Coding-Dev-Setup

This repository contains a complete developer setup for .NET backend vibe coding with GitHub Copilot.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio andreaskarz-vibe-coding-dev-setup npx -y mssql

How to use

This MCP setup provides a cohesive developer environment where Copilot can access a suite of tools via MCP servers. The six configured servers include Azure DevOps for work items, repos, and pipelines; Sequential Thinking for structured problem solving; Microsoft Learn as a remote knowledge source for official docs; Memory to persist agent knowledge; MongoDB and SQL Server connectors for database access. After installing and starting the MCP setup, open VS Code and enable Agent Mode in Copilot Chat. From there, select the MCP servers you want to enable under the 'Select Tools' area to give Copilot context and capabilities across your project.

How to install

Prerequisites:

  • Node.js (>= 20.x) and npm installed
  • Git installed
  • VS Code (or VS Code Insiders) with the Copilot extension installed

Steps:

  1. Clone this repository: git clone <repo-url> C:\Repos\Vibe-Coding-Dev-Setup cd C:\Repos\Vibe-Coding-Dev-Setup

  2. Install dependencies (assuming package.json is present in the repo): npm install

  3. Run the MCP setup script to configure and cache MCP servers: npm run setup-mcp

  4. Restart VS Code, then open Copilot Chat in Agent Mode and select the MCP servers you want to enable (Azure DevOps, memory, MongoDB, MSSQL, etc.).

Notes:

  • You can perform a dry run with: npm run setup-mcp:dry-run
  • Quick re-setup without cache warming: npm run setup-mcp:quick

Environment preparation (optional):

  • If your databases require authentication, set MDB_MCP_CONNECTION_STRING and MSSQL_MCP_CONNECTION_STRING in your environment or a .env file before launching VS Code.

Additional notes

Tips and common issues:

  • Ensure environment variables are set before starting VS Code so MCP servers can connect on first run.
  • If using MonoRepos, consider symlinking the .github configuration from this setup to your project to maintain a single source of truth for Instructions, Skills, Agents, and Prompts.
  • When using the HTTP remote server (Microsoft Learn), ensure network access to the remote endpoint is available from your development environment.
  • Restart VS Code after the MCP setup finishes to ensure mcp.json is loaded correctly. If an MCP server asks for authentication on first use (e.g., Azure DevOps organization), follow the prompts to complete the setup.

Related MCP Servers

Sponsor this space

Reach thousands of developers