Training course · Model Context Protocol (MCP) · C# & .NET

Model Context Protocol (MCP) for C# and .NET Developers

Build and connect MCP servers securely: tools, resources and prompts for Claude Code, Cursor, Copilot and your own AI agents.

Duration
2 days (14 hrs)
Format
Online or on-site
Language
German or English
Participants
open dates or exclusive for your team
Certificate
Certificate of attendance

Overview

“Model Context Protocol (MCP) for C# and .NET Developers” is designed for roles such as C# developers working with ASP.NET Core, Blazor or WPF, Teams migrating applications from .NET Framework to modern .NET and Software architects for .NET and Azure solutions and shows step by step how to use Model Context Protocol (MCP) productively, safely and transparently in C# & .NET – from the fundamentals to advanced workflows.

The Model Context Protocol is an open standard that gives AI applications a uniform way to access external tools, data sources and workflows. Instead of building separate integrations for every assistant, you implement an MCP server once and use it in Claude Code, Claude Desktop, Cursor, GitHub Copilot, VS Code and your own agents. In this two-day course you learn the host, client and server architecture, the three core primitives of tools, resources and prompts, and the stdio and Streamable HTTP transports, applying each of them directly in your own code.

On day one you use the official TypeScript or Python SDK to build an MCP server that exposes internal APIs, databases or files to AI assistants in a controlled way, and you test it with the MCP Inspector. Day two covers remote servers, OAuth-based authorisation, security risks such as prompt injection and tool poisoning, and operations, logging and governance in an enterprise setting. You learn to write tool descriptions that models use reliably, and you leave knowing how to integrate MCP servers safely into your development and agent landscape.

C# and .NET are firmly established in many organisations: ASP.NET Core APIs, Blazor and WPF front ends, Azure services and line-of-business applications dating back to the .NET Framework era. Migrating from the classic .NET Framework to modern cross-platform .NET in particular ties up significant capacity. AI coding assistants and agents take over much of the mechanical work here: converting project files to SDK style, identifying WCF or Web Forms dependencies, writing xUnit or NUnit tests, optimising Entity Framework Core queries and introducing nullable reference types. To do this well, they need context on solution structure, analyser rules and architectural guidelines. This course shows you how to use agents in Visual Studio, VS Code or Rider and on the command line.

The course is delivered live – either online in a virtual classroom or on-site in our training rooms in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart and Kaiserslautern. We can also run it exclusively for your team.

Who is this course for?

  • C# developers working with ASP.NET Core, Blazor or WPF
  • Teams migrating applications from .NET Framework to modern .NET
  • Software architects for .NET and Azure solutions
  • Developers of line-of-business applications in industry and SMEs

Typical challenges we address

  • Costly migration of .NET Framework applications built on WCF, Web Forms or ageing NuGet packages
  • Large solutions with many projects, circular dependencies and little test coverage
  • Performance issues caused by inefficient Entity Framework queries
  • Inconsistent handling of nullability, async/await and dependency injection

What you will be able to do

  • You explain the MCP architecture and choose between tools, resources and prompts for each use case.
  • You develop your own MCP server in TypeScript or Python and test it systematically.
  • You connect MCP servers to Claude Code, Cursor, Copilot and custom agents.
  • You run remote servers using Streamable HTTP and OAuth-based authorisation.
  • Use AI agents for .NET migrations, refactorings and test generation across large solutions.
  • Optimise Entity Framework Core data access and ASP.NET Core APIs with AI support.
  • Define analyser rules, conventions and review criteria that generated C# code meets reliably.

Course outline

Day 1

Module 1 Architecture and core concepts
  • Roles of host, client and server and the lifecycle of a connection
  • JSON-RPC messages, capability negotiation and notifications
  • Tools, resources and prompts: choosing the right primitive
  • Client features such as sampling, roots and elicitation at a glance
Module 2 Building your own MCP server
  • Setting up a server with the official TypeScript or Python SDK
  • Defining tools cleanly with JSON Schema for inputs and outputs
  • Exposing resources and resource templates for documents, records and configuration
  • Testing and debugging with the MCP Inspector and meaningful error messages
Module 3 Connecting to Claude Code, Cursor, Copilot and agents
  • Configuring local stdio servers and remote servers in clients
  • Project-level and user-level configuration, approvals and permissions
  • Writing tool descriptions that models reliably select correctly
  • Integrating MCP servers into custom agents built with the Claude Agent SDK or OpenAI Agents SDK
Module 4 Transport, authorisation and operations
  • Streamable HTTP, session management and stateless servers
  • OAuth-based authorisation, token validation and integration with existing identity providers
  • Deploying as containers, on serverless platforms or behind a gateway
  • Logging, monitoring, rate limiting and versioning tool interfaces

Day 2

Module 5 Security and governance
  • Threats: prompt injection via tool results, tool poisoning, confused deputy
  • Least privilege, confirmation requirements and sandboxing
  • Reviewing and approving third-party servers within the organisation
  • Data protection, logging of personal data and requirements under GDPR and the EU AI Act
Module 6 Practice lab: C# & .NET
  • Migrating to modern .NET
  • Writing xUnit and NUnit tests
  • Optimising Entity Framework Core
  • Introducing nullable reference types
  • Building ASP.NET Core APIs
  • Code analysis and refactoring
Module 7 Data protection, quality & transfer to daily work
  • Clarify whether source code may be sent to cloud models and which tenant or region settings apply, and keep connection strings and secrets from User Secrets or Key Vault out of prompts. New NuGet packages should be checked for licence, provenance and vulnerabilities – not least in view of the obligations under the Cyber Resilience Act.
  • Ground rules for safe AI use in your team
  • Checking results: facts, sources, tests and the four-eyes principle
  • Personal action plan for the next 30 days
  • Open questions, outlook and resources for further learning

Practical scenarios from your field

Migrating to modern .NET

The agent analyses projects using the upgrade tooling and compiler output, converts csproj files to SDK style, replaces incompatible APIs and proposes alternatives to WCF or System.Web until the solution builds and tests pass.

Writing xUnit and NUnit tests

Services, controllers and domain logic get unit tests with Moq or NSubstitute plus integration tests using WebApplicationFactory. The AI covers edge cases and sticks to your existing test conventions.

Optimising Entity Framework Core

The AI analyses generated SQL, spots N+1 problems, missing AsNoTracking calls or awkward Includes, and creates migrations and projections for faster queries. Every change is backed by the resulting SQL.

Introducing nullable reference types

Nullable is enabled project by project while the AI works through compiler warnings, adds guard clauses and annotations and makes implicit assumptions in the code explicit.

Building ASP.NET Core APIs

Specifications become minimal APIs or controllers with validation, ProblemDetails error handling, authentication and OpenAPI documentation, consistent with your existing layered architecture. Integration tests safeguard each new endpoint.

Code analysis and refactoring

Roslyn analyser findings are fixed systematically, oversized classes split, async anti-patterns such as .Result removed and dependency injection registrations made consistent. Build, analysers and existing tests confirm that behaviour is unchanged.

Possible hands-on projects

Minimal API service

An ASP.NET Core service using minimal APIs, EF Core, health checks, structured logging and integration tests, built end to end by an AI agent from a specification.

Migration inventory

A console tool that scans a solution, lists target frameworks, NuGet packages and incompatible APIs, and produces a prioritised migration plan.

Blazor admin UI

A small Blazor application for managing master data, with form validation, filterable tables and integration with an existing REST API.

Prerequisites

Solid programming skills in TypeScript/JavaScript or Python and a basic understanding of HTTP APIs and JSON. Some experience using AI assistants in day-to-day development is helpful. Good C# skills, experience with ASP.NET Core or .NET desktop development, and familiarity with Visual Studio, Rider or VS Code and Git.

Technical requirements

A laptop with Node.js or Python, Git and a code editor, plus access to at least one MCP-capable client such as Claude Code, Claude Desktop, Cursor or VS Code with Copilot.

Data protection & compliance

Clarify whether source code may be sent to cloud models and which tenant or region settings apply, and keep connection strings and secrets from User Secrets or Key Vault out of prompts. New NuGet packages should be checked for licence, provenance and vulnerabilities – not least in view of the obligations under the Cyber Resilience Act.

Suggested dates

All dates are suggestions – your preferred date is always possible.

  • Wed, 25 November 2026 – Thu, 26 November 2026 Online Request
  • Thu, 10 December 2026 – Fri, 11 December 2026 Salzburg Request
  • Mon, 14 December 2026 – Tue, 15 December 2026 Online Request
  • Tue, 19 January 2027 – Wed, 20 January 2027 Bremen Request
  • Mon, 25 January 2027 – Tue, 26 January 2027 Online Request
  • Mon, 8 February 2027 – Tue, 9 February 2027 Augsburg Request

Frequently asked questions

Why would I need my own MCP server?

Whenever AI assistants need access to internal systems such as ticketing tools, databases, documentation or line-of-business applications. Your own server defines precisely which actions and data are available and can then be reused across several clients. That avoids isolated one-off integrations and keeps access firmly under your control.

Which programming language does the course use?

You can choose between TypeScript and Python, both of which have official SDKs. The concepts are identical and all exercises are available in both versions. Developers working in other languages still benefit, because the protocol is language-agnostic and SDKs for other languages follow a similar structure.

How secure is MCP for enterprise use?

The protocol provides mechanisms for authorisation and permissions, but real-world security depends on implementation and operations. Risks such as prompt injection through tool results or over-privileged servers are genuine. We cover concrete countermeasures, approval processes for third-party servers and how to handle personal data.

Does AI really help with migrating from .NET Framework?

Yes, especially with the mechanical work: converting project files, finding incompatible APIs, suggesting replacement libraries and fixing build errors iteratively. Fundamental architecture decisions, such as replacing WCF with gRPC or REST, remain with the team. On the course you practise breaking such migrations into small, verifiable steps.

Do AI agents work with Visual Studio?

Many AI assistants integrate directly with Visual Studio, VS Code or Rider, while others run in the terminal alongside the dotnet CLI. The methods taught are tool-neutral: you learn to provide context, scope tasks and safeguard results through builds, analysers and tests, regardless of your IDE.

How much does “Model Context Protocol (MCP) for C# and .NET Developers” cost?

The course costs a flat €949 plus VAT per participant – whether online or on-site. This includes 2 training day(s) with a live trainer, course materials, a lab environment and a certificate of attendance.

Can I suggest my own date?

Yes. Our suggested dates are just a guide. In the request form you can always describe your preferred date or period in free text – we check availability and confirm within one working day.

Is the course online or on-site?

Both are possible: live online in a virtual classroom or on-site in Munich, Salzburg, Berlin, Augsburg, Hanover, Bremen, Stuttgart or Kaiserslautern. We can also run the course exclusively for your team.

More courses for C# and .NET Developers

More Model Context Protocol (MCP) courses

All 29 Model Context Protocol (MCP) courses

Model Context Protocol (MCP) · MunichModel Context Protocol (MCP) · SalzburgModel Context Protocol (MCP) · BerlinModel Context Protocol (MCP) · AugsburgModel Context Protocol (MCP) · HanoverModel Context Protocol (MCP) · BremenModel Context Protocol (MCP) · StuttgartModel Context Protocol (MCP) · KaiserslauternModel Context Protocol (MCP) · Online