[Blazor] MCP Apps tracking issue

Open
  • Is something wrong?
#70,423 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
backend-api-design

Research direction

This is a tracking issue covering two packages and several open work items, with pull requests #70314 and #70303 linked in the description. Start by reading those pull requests and identify a specific unchecked task with a separate feature issue or API proposal. Done means completing that scoped task and validating the end-to-end Razor component display in the Blazor chat.

Written by the indexing model from the issue text.

Description

area-blazor feature-blazor-builtin-components

Description

This is the tracking issue for the ongoing work on MCP Apps support in Blazor. It covers two packages. Microsoft.AspNetCore.Components.AI.Mcp shows MCP App UI inside a Blazor chat, and Microsoft.AspNetCore.Components.Mcp serves Razor components as MCP Apps to any MCP client.

Current pull requests

Show MCP Apps in a Blazor chat (#70314)

  • Open a feature issue for #70314
  • Open an API proposal
  • Update Microsoft.Extensions.AI from 10.6.0 to 10.8.3 on main
  • Document the sandbox origin and CSP setup
  • Support WebAssembly and Auto render modes
  • Validate on Linux and macOS

Serve Razor components as MCP Apps (#70303)

  • Open a feature issue for #70303
  • Open an API proposal
  • Support streaming rendering
  • Support session and TempData in MCP App forms
  • Support navigation between MCP App pages
  • Support interactive render modes and JS interop

End to end

  • Show a Razor component served by #70303 inside the #70314 chat
Dominant language
C#
Stars
38.5k
Forks
11.6k
Avg merge
3d 1h
Merged PRs (30d)
289

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/aspnetcore

All issues in dotnet/aspnetcore

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.