Installing Sheetize MCP Server via NuGet

How to install via NuGet Package Manager Console

If you are using Visual Studio Community 2026

• Open your project

  • Launch Visual Studio Community 2026 and open your .NET application.

• Create an mcp.json file in the solution folder with the following content

  • Replace path\to\license.lic with the path to your licence file, or delete the line if you are using the free version.

  {
    "inputs": [],
    "servers": {
      "sheetize-mcp-server": {
        "type": "stdio",
        "command": "dnx",
        "args": [
          "SheetizeMCPServer",
          "--prerelease",
          "--yes",
          "--licensePath",
          "path\\to\\license.lic"
        ],
        "env": {}
      }
    }
  }

• Check that the package installed correctly

  • Go to View > GitHub Copilot Chat.
  • Open Select tools and skills – you should see the custom MCP server listed under the Added section.

If you are using Visual Studio Code

• Open your project

  • Launch Visual Studio Code.

• In the root folder of the project create the folder and file .vscode/mcp.json with the following content

  • Replace path\to\license.lic with the path to your licence file, or remove the line for the free version.

  {
    "servers": {
      "sheetize-mcp-server": {
        "type": "stdio",
        "command": "dnx",
        "args": [
          "SheetizeMCPServer",
          "--prerelease",
          "--yes",
          "--licensePath",
          "path\\to\\license.lic"
        ]
      }
    }
  }

• Verify the installation

  • Choose View > Chat.
  • Then go to Settings > MCP Servers – the custom MCP server should appear under the Workspace section.

Pros of using NuGet

• Automatic dependency management – NuGet resolves and installs all required libraries for you, keeping everything up to date.
• Simplified updates – Updating a package is a matter of a few clicks in the GUI or a single command in the console.
• Integrated with Visual Studio – The package manager is built into Visual Studio, offering a familiar, user‑friendly interface.
• Versioning control – You can pin specific versions, roll back to previous releases, or test newer prereleases with ease.

Cons of using NuGet

• Primarily tied to Visual Studio – While it works from the command line, the deepest integration is with Visual Studio; other IDEs get a more limited experience.
• Potential version conflicts – Large solutions with many dependencies can occasionally run into clashes that need manual resolution.
• Requires an internet connection – Packages are fetched from nuget.org, so you need connectivity unless you maintain a local cache.
• Complexity in very large projects – Big codebases may benefit from additional tooling (e.g., paket, custom scripts) to keep NuGet management tidy.