diff --git a/docs/VS2026_COMPLETION_SUMMARY.md b/docs/VS2026_COMPLETION_SUMMARY.md
index 8382c1e..58f78bd 100644
--- a/docs/VS2026_COMPLETION_SUMMARY.md
+++ b/docs/VS2026_COMPLETION_SUMMARY.md
@@ -3,20 +3,17 @@
 ## ✅ What Was Added
 
 ### 1. **Enhanced useMcpSetup.js Composable**
-- **New Property**: `mcpVS2026Json` - Full Visual Studio 2026 configuration
+- **New Property**: `mcpVS2026Json` - Visual Studio 2026 MCP configuration
 - **New Function**: `copyMcpFilesToProject()` - Direct file creation API
 - **Updated Bundle**: `mcpConfig` now includes VS 2026 configuration
-- **Total Size**: 552 lines (enhanced from 325 lines)
+- **Total Size**: 662 lines (enhanced from 325 lines)
 
 ### 2. **VS 2026 Configuration Features**
-✨ Full MCP server configuration with:
-- Schema reference for validation (`$schema`: `https://aka.ms/mcp-server-schema`)
-- 10+ tool definitions (tasks, context, agents, dashboard)
-- Complete resource endpoints mapping
-- Security configuration (CORS, rate limiting)
-- Logging configuration (info level, JSON format, timestamps)
-- Auto-reconnect behavior (3 retries, 30s timeout)
-- Health check monitoring (60s interval)
+✨ Minimal MCP server configuration with:
+- Server type and URL with project/agent context
+- Ready for VS 2026 auto-detection
+- Extensible structure for adding capabilities, tools, and resources
+- Server dynamically exposes tools and capabilities through MCP protocol
 
 ### 3. **File Generation System**
 Generates 6 configuration files:
@@ -48,11 +45,11 @@ scripts/mcp-agent.sh           (Bash helpers)
 - No manual configuration required
 - Works on startup and after restart
 
-### Comprehensive Configuration
-- Full tool definitions with descriptions and endpoints
-- API endpoint mappings for all operations
-- Security settings for production readiness
-- Logging and monitoring configuration
+### Minimal Configuration
+- Essential server connection details (type and URL)
+- Project and agent context passed via URL parameters
+- Tools, resources, and capabilities exposed dynamically by the server
+- Extensible structure for future enhancements
 
 ### Developer Experience
 - Simple API: `copyMcpFilesToProject(config, projectId)`
@@ -97,25 +94,17 @@ scripts/mcp-agent.sh           (Bash helpers)
 ### Configuration Structure
 ```json
 {
-  "$schema": "https://aka.ms/mcp-server-schema",
-  "version": "1.0.0",
   "servers": {
     "agent-shaker": {
       "type": "http",
-      "url": "...",
-      "capabilities": ["resources", "tools", "prompts", "context-sharing"],
-      "project": { ... },
-      "agent": { ... },
-      "resources": { ... },
-      "tools": [ ... 10 items ],
-      "behavior": { ... },
-      "security": { ... },
-      "logging": { ... }
+      "url": "http://localhost:8080?project_id=...&agent_id=..."
     }
   }
 }
 ```
 
+**Note**: This minimal configuration provides essential server connection details. The server dynamically exposes tools, resources, and capabilities through the MCP protocol once connected. The configuration can be extended with additional fields such as `$schema`, `version`, `capabilities`, `tools`, `resources`, `security`, and `logging` if your setup requires explicit definitions.
+
 ## 🚀 Usage
 
 ### In Vue Components
@@ -170,10 +159,10 @@ Response:
 - ✅ Multiple deployment options
 
 ### Production Readiness
-- ✅ Security configuration included
-- ✅ Logging and monitoring built-in
-- ✅ Auto-reconnect and health checks
-- ✅ Schema validation support
+- ✅ Clean, minimal configuration
+- ✅ Extensible structure for future features
+- ✅ Server-side capability negotiation
+- ✅ Dynamic tool and resource discovery
 
 ## 📚 Documentation Files
 
@@ -205,9 +194,9 @@ Response:
 
 ### For DevOps/Admin
 - 📦 Complete file generation
-- 🔐 Security configuration included
-- 📊 Logging and monitoring
-- 🔄 Auto-reconnect capability
+- 🔐 Clean configuration structure
+- 📊 Server handles logging and monitoring
+- 🔄 Connection managed by IDE
 
 ## 🔄 Integration Path
 
@@ -293,7 +282,7 @@ await downloadAllMcpFiles(mcpConfig, 'agent-name')
 ## ✅ Status
 
 - **Composable**: ✅ Complete and tested
-- **VS 2026 Config**: ✅ Full schema support
+- **VS 2026 Config**: ✅ Minimal, extensible configuration
 - **Direct Copy API**: ✅ Ready for implementation
 - **Documentation**: ✅ Comprehensive guides created
 - **Error Handling**: ✅ Implemented
diff --git a/docs/VS2026_FEATURE_SUMMARY.md b/docs/VS2026_FEATURE_SUMMARY.md
index 0f54aad..d5de82b 100644
--- a/docs/VS2026_FEATURE_SUMMARY.md
+++ b/docs/VS2026_FEATURE_SUMMARY.md
@@ -9,10 +9,10 @@
 
 Enhanced Composable ✅
 └─ mcpVS2026Json (NEW)
-   ├─ Full schema-aware configuration
-   ├─ 10+ integrated tools
-   ├─ Complete API endpoint mapping
-   └─ Production-ready settings
+   ├─ Minimal, focused configuration
+   ├─ Server type and URL with context
+   ├─ Dynamic tool/resource discovery
+   └─ Production-ready, extensible
 
 Deployment Options ✅
 ├─ Option A: Download ZIP
@@ -58,32 +58,17 @@ const {
 ### 2. Visual Studio 2026 Configuration
 ```json
 {
-  "$schema": "https://aka.ms/mcp-server-schema",
-  "version": "1.0.0",
   "servers": {
     "agent-shaker": {
       "type": "http",
-      "url": "http://localhost:8080?project_id=X&agent_id=Y",
-      "capabilities": [
-        "resources",
-        "tools", 
-        "prompts",
-        "context-sharing"
-      ],
-      "tools": [
-        { "name": "get_my_tasks", ... },
-        { "name": "update_task_status", ... },
-        { "name": "create_task", ... },
-        // 7 more tools...
-      ],
-      "resources": { ... },
-      "security": { ... },
-      "logging": { ... }
+      "url": "http://localhost:8080?project_id=X&agent_id=Y"
     }
   }
 }
 ```
 
+**Note**: This minimal configuration connects to the MCP server. Tools, resources, and capabilities are discovered dynamically through the MCP protocol. You can extend this with additional fields like `$schema`, `capabilities`, `tools`, `resources`, `security`, and `logging` if needed.
+
 ### 3. Two Deployment Methods
 
 #### Method 1: Download ZIP
@@ -124,12 +109,13 @@ Project Root
 └── .mcp.json ← Automatically detected by VS 2026
     ├── No manual configuration needed
     ├── Loads on startup
-    └── Establishes MCP connection
+    ├── Establishes MCP connection
+    └── Tools/resources discovered dynamically
 ```
 
-### Comprehensive Tool Support
+### Server-Side Tool Discovery
 ```
-10 Built-in Tools:
+MCP Server provides tools dynamically:
 ✓ get_my_identity      - Get agent info
 ✓ get_my_project       - Get project details
 ✓ get_my_tasks         - List assigned tasks
@@ -141,11 +127,14 @@ Project Root
 ✓ add_context          - Add documentation
 ✓ get_project_agents   - See team members
 ✓ get_dashboard_stats  - View project metrics
+
+Note: Tools are exposed by the server through the MCP protocol,
+not defined in the client configuration file.
 ```
 
 ### Complete API Integration
 ```
-Endpoints Mapped:
+Endpoints Available Through MCP:
 /health              - Health check
 /projects            - Project listing
 /agents              - Agent management
@@ -154,6 +143,9 @@ Endpoints Mapped:
 /dashboard           - Metrics & stats
 /agents/{id}/tasks   - Agent's tasks
 /projects/{id}/...   - Project resources
+
+Note: Endpoints are accessed through the MCP server connection,
+not defined in the client configuration.
 ```
 
 ## 📋 Implementation Checklist
@@ -164,6 +156,7 @@ Endpoints Mapped:
 - [x] Implemented `copyMcpFilesToProject()` function
 - [x] Updated ZIP download to include `.mcp.json`
 - [x] Comprehensive error handling
+- [x] Minimal, focused configuration structure
 
 ### Backend (To Do)
 - [ ] Create endpoint: `POST /api/projects/{projectId}/mcp-files`
@@ -223,15 +216,15 @@ func CreateMcpFiles(w http.ResponseWriter, r *http.Request) {
 
 ### Composable Size
 - **Original**: 325 lines
-- **Enhanced**: 552 lines
-- **Increase**: +227 lines (+70%)
-- **New Features**: 2 major additions
+- **Enhanced**: 662 lines
+- **Increase**: +337 lines (+104%)
+- **New Features**: 2 major additions (mcpVS2026Json, copyMcpFilesToProject)
 - **Zero Breaking Changes**: ✅
 
 ### Generated Configuration Size
-- **mcpVSCodeJson**: ~1.2 KB (simplified)
-- **mcpVS2026Json**: ~4.5 KB (full-featured)
-- **Total Package**: ~20 KB (with all files and ZIP)
+- **mcpVSCodeJson**: ~200 bytes (minimal)
+- **mcpVS2026Json**: ~150 bytes (minimal)
+- **Total Package**: ~15 KB (with all files and ZIP)
 
 ### Performance
 - **Configuration Generation**: < 1ms
@@ -349,9 +342,9 @@ const applyConfig = async () => {
 
 ### 🏢 For Organizations
 - 📦 Complete setup package
-- 🔐 Security configured
-- 📊 Monitoring enabled
-- 🔄 Auto-recovery built-in
+- 🔐 Clean, minimal configuration
+- 📊 Dynamic capability discovery
+- 🔄 Standards-compliant MCP protocol
 
 ## 🚀 Next Steps
 
@@ -389,7 +382,7 @@ const applyConfig = async () => {
 Your MCP configuration system is now ready for Visual Studio 2026! 
 
 ✅ **Composable**: Fully enhanced with VS 2026 support  
-✅ **Configuration**: Complete with schema and all tools  
+✅ **Configuration**: Minimal, extensible MCP config  
 ✅ **Deployment**: Two flexible options (download/copy)  
 ✅ **Documentation**: Comprehensive guides provided  
 ✅ **Ready to Deploy**: Just needs backend implementation  
diff --git a/docs/VS2026_IMPLEMENTATION_GUIDE.md b/docs/VS2026_IMPLEMENTATION_GUIDE.md
index 2e2e6b5..881cc29 100644
--- a/docs/VS2026_IMPLEMENTATION_GUIDE.md
+++ b/docs/VS2026_IMPLEMENTATION_GUIDE.md
@@ -14,7 +14,7 @@ const mcpApiUrl = computed(() => {
 })
 
 const {
-  mcpVS2026Json,      // New: Full VS 2026 configuration
+  mcpVS2026Json,      // New: VS 2026 MCP configuration
   mcpConfig,          // Bundle of all configs
   downloadAllMcpFiles,
   copyMcpFilesToProject // New: Direct copy to project
@@ -76,18 +76,15 @@ project-root/
 ## What Gets Generated
 
 ### `.mcp.json` (VS 2026)
-- Full MCP server configuration
-- Schema reference for validation
-- 10+ tool definitions
-- API endpoint mappings
-- Security and logging configuration
-- Auto-reconnect settings
-- Health check configuration
+- Minimal MCP server configuration
+- Server type and URL with project/agent context
+- Tools and capabilities exposed dynamically by server
+- Extensible structure for future enhancements
 
 ### `.vscode/mcp.json` (VS Code)
-- Simplified VS Code format
+- Minimal VS Code format
 - Server URL with project/agent context
-- Same tools and capabilities
+- Tools discovered dynamically through MCP protocol
 
 ### `.vscode/settings.json`
 - Environment variables for terminal
@@ -109,11 +106,11 @@ Choose between:
 - **ZIP Download**: For local setup or sharing
 - **Direct Copy**: One-click project integration
 
-### 🛡️ Secure Configuration
-- No authentication required for demo
-- CORS enabled for localhost
-- Rate limiting (disabled for dev, enabled for production)
-- Logging with timestamps
+### 🛡️ Clean Configuration
+- No hardcoded tools or capabilities in config
+- Dynamic discovery through MCP protocol
+- Minimal configuration for easy maintenance
+- Extensible structure for custom needs
 
 ### 📦 Complete Setup
 All necessary files included:
@@ -268,9 +265,9 @@ After setup, verify everything works:
    - Try Copilot prompts
 
 2. **Customize Configuration**
-   - Edit tool definitions
-   - Add custom endpoints
-   - Adjust logging levels
+   - Extend with additional fields if needed
+   - Add explicit tool definitions (optional)
+   - Configure custom capabilities (optional)
 
 3. **Share with Team**
    - Download ZIP and share
diff --git a/docs/VS2026_MCP_SETUP.md b/docs/VS2026_MCP_SETUP.md
index b5c499e..377d01a 100644
--- a/docs/VS2026_MCP_SETUP.md
+++ b/docs/VS2026_MCP_SETUP.md
@@ -7,10 +7,10 @@ Enhanced MCP setup composable with dedicated Visual Studio 2026 support, includi
 ## Features
 
 ### 1. **VS 2026 Dedicated Configuration** (`mcpVS2026Json`)
-- Full-featured MCP server configuration optimized for Visual Studio 2026
-- Includes schema reference for VS 2026 compatibility
-- Comprehensive tool definitions and endpoints
-- Enhanced security and logging configuration
+- 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.json` file for project root
@@ -36,23 +36,17 @@ Generates configuration for:
 ### `.mcp.json` (Visual Studio 2026 - Root Directory)
 ```json
 {
-  "$schema": "https://aka.ms/mcp-server-schema",
-  "version": "1.0.0",
   "servers": {
     "agent-shaker": {
       "type": "http",
-      "url": "http://localhost:8080?project_id=...&agent_id=...",
-      "name": "Agent Shaker MCP Server",
-      "capabilities": ["resources", "tools", "prompts", "context-sharing"],
-      "tools": [...],
-      "resources": {...},
-      "security": {...},
-      "logging": {...}
+      "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