⚠️ SUPERSEDED — do not follow this document.
This describes an earlier attempt that targeted the pre-Nuxt
web/src/tree, which no longer exists. The files it references (web/src/composables/useMcpSetup.js,web/src/views/ProjectDetail.vue) were removed in the Nuxt 4 migration, and even at the time it was written the backend endpoint and the UI were listed as "To Do" — the "✅ Complete" marks apply only to a composable that never reached a running application.The feature is now actually implemented. See MCP_SETUP.md.
Visual Studio 2026 MCP Configuration Setup
Visual Studio 2026 MCP Configuration Setup
Overview
Enhanced MCP setup composable with dedicated Visual Studio 2026 support, including automatic .mcp.json generation and direct project directory integration.
Features
1. VS 2026 Dedicated Configuration (mcpVS2026Json)
- MCP server configuration optimized for Visual Studio 2026
- Minimal, focused configuration with server type and URL
- Includes project and agent context in URL parameters
- Ready for extension with additional capabilities as needed
2. Root Directory .mcp.json
- Auto-generated
.mcp.jsonfile for project root - Recognized automatically by Visual Studio 2026
- No manual configuration required after extraction
- Includes full environment context (project, agent, capabilities)
3. Direct Project Integration
- New
copyMcpFilesToProject()function writes files directly to project - No need to manually copy or extract files
- Automatic directory structure creation
- API-based file management
4. Multi-IDE Support
Generates configuration for:
- Visual Studio 2026 -
.mcp.jsonin project root - VS Code -
.vscode/settings.jsonand.vscode/mcp.json - Command Line - PowerShell and Bash scripts
- GitHub Copilot -
.github/copilot-instructions.md
Configuration Files Generated
.mcp.json (Visual Studio 2026 - Root Directory)
{
"servers": {
"agent-shaker": {
"type": "http",
"url": "http://localhost:8080?project_id=...&agent_id=..."
}
}
}
Note: This minimal configuration provides the essential server connection details. The server itself exposes tools, resources, and capabilities dynamically through the MCP protocol once connected. You can extend this configuration with additional fields like $schema, capabilities, tools, etc., if your Visual Studio 2026 setup requires explicit definitions.
Additional Files
.vscode/settings.json- VS Code environment variables.vscode/mcp.json- VS Code MCP server configuration.github/copilot-instructions.md- Copilot instructionsscripts/mcp-agent.ps1- PowerShell helperscripts/mcp-agent.sh- Bash helper
Usage
Option 1: Download as ZIP
import { downloadAllMcpFiles } from '@/composables/useMcpSetup'
// In your component
downloadAllMcpFiles(mcpConfig, agentName)
// Downloads: mcp-setup-{agent-name}.zip
Option 2: Copy Directly to Project
import { copyMcpFilesToProject } from '@/composables/useMcpSetup'
// In your component
const result = await copyMcpFilesToProject(mcpConfig, projectId)
if (result.success) {
console.log('Files created:', result.files)
} else {
console.error('Error:', result.message)
}
Implementation in Components
Using the Composable
<script setup>
import { computed } from 'vue'
import { useMcpSetup } from '@/composables/useMcpSetup'
const mcpApiUrl = computed(() => {
return `${window.location.protocol}//${window.location.host}/api`
})
const {
mcpSettingsJson,
mcpCopilotInstructions,
mcpPowerShellScript,
mcpBashScript,
mcpVSCodeJson,
mcpVS2026Json, // New: VS 2026 configuration
mcpConfig,
downloadFile,
downloadAllMcpFiles,
copyMcpFilesToProject // New: Direct copy function
} = useMcpSetup(mcpSetupAgent, project, mcpApiUrl)
</script>
Download All Files Button
<button @click="downloadAll">
📥 Download All MCP Files
</button>
<script>
const downloadAll = async () => {
await downloadAllMcpFiles(mcpConfig, agentName)
}
</script>
Direct Copy Button
<button @click="copyToProject">
📁 Apply to Project Directory
</button>
<script>
const copyToProject = async () => {
const result = await copyMcpFilesToProject(mcpConfig, projectId)
if (result.success) {
showSuccess(`✅ ${result.message}`)
} else {
showError(`❌ ${result.message}`)
}
}
</script>
Visual Studio 2026 Setup Flow
-
Generate Configuration
- User selects agent and project
- System generates
.mcp.json
-
Two Options for Installation
- Option A: Download ZIP and extract to project root
- Option B: Click "Apply to Project" button for direct copy
-
Auto-Recognition
- VS 2026 automatically detects
.mcp.json - Loads MCP server configuration
- Establishes connection to Agent Shaker
- VS 2026 automatically detects
-
Ready to Use
- Copilot features enabled
- Agent identity assigned
- Task management active
- Context sharing available
Configuration Structure
VS 2026 Config Includes
✓ Server metadata and schema
✓ HTTP connection details
✓ Project information
✓ Agent identity and capabilities
✓ 10+ task management tools
✓ Resources and API endpoints
✓ Security configuration
✓ Logging setup
✓ Auto-reconnect behavior
✓ Health check configuration
API Endpoint Required
For copyMcpFilesToProject() to work, backend should implement:
POST /api/projects/{projectId}/mcp-files
Request Body:
{
"files": {
".mcp.json": "...",
".vscode/settings.json": "...",
".vscode/mcp.json": "...",
...
}
}
Response:
{
"success": true,
"files": [...]
}
Benefits
✨ No Manual Configuration - Automatic setup 🚀 IDE Native - Works with VS 2026 natively 📦 Complete Setup - All files generated automatically 🔄 Flexible Deployment - Download or direct copy options 🛡️ Secure - Includes security and logging config 📝 Well Documented - Comprehensive comments and JSDoc ✅ Error Handling - Proper error messages and recovery 🔌 Future Proof - Extensible architecture
Version Info
- Composable Version: 2.0.0
- VS 2026 Support: ✅ Full
- VS Code Support: ✅ Full
- CLI Support: ✅ Full
Related Files
- useMcpSetup.js - Main composable
- ProjectDetail.vue - Component usage
- MCP_SETUP_QUICK_REFERENCE.md - Quick guide
- QUICKSTART.md - Getting started
Troubleshooting
Files not appearing in VS 2026
- Restart Visual Studio 2026 after file creation
- Check if
.mcp.jsonis in project root - Verify project has MCP server feature enabled
Direct copy fails
- Check API endpoint availability
- Verify project permissions
- Check network connectivity
- Review browser console for errors
Configuration not applied
- Clear VS 2026 cache
- Restart IDE
- Verify
.mcp.jsonfile is valid JSON - Check MCP server status
Support
For issues or questions:
- Check MCP_SETUP_QUICK_REFERENCE.md
- Review error messages in browser console
- Verify API endpoint is accessible
- Check project permissions and configuration