msbuild-server

Guide for using MSBuild Server to improve CLI build performance. Only activate in MSBuild/.NET build context. Activate when developers report slow incremental builds from the command line, or when CLI builds are noticeably slower than IDE builds. Covers MSBUILDUSESERVER=1 environment variable for persistent server-based caching. Do not activate for IDE-based builds (Visual Studio already uses a long-lived process).

dotnet/skills|Updated May 23, 2026

Works with

Claude CodeCursorCline

Installation Guide

Select your AI agent

How to use msbuild-server on Cursor

AI-first code editor with Composer

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

›Cursor installed and configured on your machine
›Node.js 16+ with npm — verify with node --version
›Active project directory where you want to add msbuild-server

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/dotnet/skills --skill msbuild-server

Fetches msbuild-server from dotnet/skills and configures it for Cursor.

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?

│

│ ── Universal (.agents/skills) ────────────────

│ · Cline · Codex · Goose · Windsurf

│ ●Cursor(selected)

│ · Cursor · Aider · Continue

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/msbuild-server

Restart Cursor to activate msbuild-server. Access via /msbuild-server in your agent's command palette.

⚠

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

›View source on GitHub ›Skills CLI docs ›About Cursor ›What are agent skills?

Documentation

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

✓

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

✓

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

✓

Improve work quality by 30-40% with less effort

Input

Required

Description

Shell context

The shell where the environment variable will be set (bash, PowerShell, or Windows persistent)

Workflow

Step 1: Confirm CLI context

Verify the developer is building from the command line (dotnet build), not from Visual Studio or another IDE. The MSBuild Server provides no benefit inside an IDE.

Step 2: Set the environment variable

# Bash / CI export MSBUILDUSESERVER=1 # PowerShell $env:MSBUILDUSESERVER = "1" # Windows (persistent) setx MSBUILDUSESERVER 1

Step 3: Validate improvement

Run two sequential builds of the same project and compare times:

First build (cold): dotnet build -- server starts, no cache benefit

Second build (warm): dotnet build -- should be noticeably faster

The most noticeable improvement is in repos with many projects or complex Directory.Build.props chains.

Common Pitfalls

Pitfall	Solution
Expecting improvement in Visual Studio	VS already uses long-lived MSBuild nodes; the server adds no benefit
Build correctness issues after enabling	Run `dotnet build-server shutdown` to reset; if issues persist, disable the server
Server process using unexpected memory	The server persists in background; shut down with `dotnet build-server shutdown` when idle

name	msbuild-server
description	"Guide for using MSBuild Server to improve CLI build performance. Only activate in MSBuild/.NET build context. Activate when developers report slow incremental builds from the command line, or when CLI builds are noticeably slower than IDE builds. Covers MSBUILDUSESERVER=1 environment variable for persistent server-based caching. Do not activate for IDE-based builds (Visual Studio already uses a long-lived process)."
license	MIT

msbuild-server

Installation Guide

How to use msbuild-server on Cursor

Prerequisites

Run the install command

Select Cursor when prompted

Verify installation

Security Notice

Documentation

List & Monetize Your Skill

Use Cases

Task Automation & Efficiency

Knowledge Enhancement

Quality Improvement

Install Skill

MSBuild Server for CLI Caching

When to Use

When Not to Use

Inputs

Workflow

Step 1: Confirm CLI context

Step 2: Set the environment variable

Step 3: Validate improvement

Validation

Common Pitfalls

Implementation Guide

Best Practices

When to Use This

Learning Path

Related Skills

analyzing-dotnet-performance

optimizing-ef-core-queries

run-tests

code-testing-agent

migrate-dotnet9-to-dotnet10

dotnet-webapi

Reviews

Discussion