A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://www.npmjs.com/package/@microsoft/devbox-mcp below:

@microsoft/devbox-mcp - npm

This is a Model Context Protocol (MCP) server for Microsoft Dev Box, providing seamless integration between AI agents and Microsoft Dev Box services. This server enables natural language interactions for developer-focused operations like managing Dev Boxes, configurations, and pools.

  1. Node.js 18 or newer

  2. Azure Resources

  3. MCP Client

Dev Box MCP Server can be installed on any MCP clients, such as Visual Studio or Visual Studio Code (VS Code). Below are the detailed steps for installing on Visual Studio Code.

For installation steps on Visual Studio, see here

✨ One-Click Install on VS Code

Click one of these buttons to install the Dev Box MCP Server for VS Code or VS Code Insiders.

Just one click, and you're ready to go! 🎉

🔧 Manual Install on VS Code

For a step-by-step installation, follow one of the following instructions:

  1. Add .vscode/mcp.json to your workspace:
{
    "servers": {
        "DevBox": {
            "command": "npx",
            "args": ["-y", "@microsoft/devbox-mcp@latest"]
        }
    }
}
  1. Alternatively, add to your user settings.json:
{
    "mcp": {
        "servers": {
            "DevBox": {
                "command": "npx",
                "args": ["-y", "@microsoft/devbox-mcp@latest"]
            }
        }
    }
}
  1. You can also add Dev Box MCP programmatically using VS Code CLI:
# For VS Code
code --add-mcp '{"name":"DevBox","command":"npx","args":["-y","@microsoft/devbox-mcp@latest"]}'

For detailed MCP installation steps on VS Code, see here.

Tool call failed with 'Tool xxx does not have an implementation registered' or 'I apologize for the technical issue'

If you encounter this error, it's likely due to an invalid tool cache issue in GitHub Copilot Agent mode. To resolve the issue:

  1. Press Ctrl+Shift+P to open the command palette
  2. Run MCP: Reset cached tools
  3. Restart the MCP server

For more details, see GitHub issue #177

Error: Cannot find module '../build/Release/keytar.node'

If you encounter this error, try running npx clear-npx-cache.

If you encounter other errors when starting the MCP server, you may also try the command above.

🛠️ Currently Supported Tools

The Dev Box MCP provides tools for interacting with the following Microsoft Dev Box resources:

The Dev Box MCP Server uses DefaultAzureCredential and WAM (Web Account Manager) based brokered authentication for seamless Azure integration.

Authentication follows this credential chain order:

  1. Environment Variables (EnvironmentCredential)
  2. Managed Identity (ManagedIdentityCredential)
  3. Visual Studio Code (VisualStudioCredential)
  4. Azure CLI (AzureCliCredential)
  5. Azure PowerShell (AzurePowerShellCredential)
  6. Azure Developer CLI (AzureDeveloperCliCredential)
  7. Windows SSO (Single Sign-On) (WAM - Web Account Manager)

The credential chain will attempt each method in order until a successful authentication is achieved. WAM provides seamless single sign-on experience on Windows platforms, automatically using your existing Windows credentials when available.

If you encounter authentication errors, try:

  1. Make sure you're logged in to Windows SSO (Single Sign-On) or Azure CLI
  2. Verify you have the necessary permissions in your Azure subscription
  3. Check if you need to specify a specific tenant using az login --tenant <tenant-id>

Copyright (c) Microsoft Corporation. All rights reserved.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4