McpEssentials.Core 1.0.0-preview.4

McpEssentials.Core

Authenticated MCP task stores and shared primitives for generic Model Context Protocol servers built on the C# SDK.

The SDK ships InMemoryMcpTaskStore, which is process-wide: any caller who knows a task id can get, update, or cancel it. InMemoryMcpTaskStorePlus is our own in-memory store. It records the user who created each task, isolates later manipulation to that user, and never wraps the SDK store.

Install

dotnet add package McpEssentials.Core

Usage

builder.Services.AddHttpContextAccessor();

builder.Services.AddMcpServer()
    .WithHttpTransport()
    .WithTools<MyTools>()
    .WithTasksPlus(
        sp => sp.GetRequiredService<IHttpContextAccessor>().HttpContext?.User,
        o => o.DefaultTimeToLive = TimeSpan.FromMinutes(5));

Local / stdio: .WithTasksPlus("local-user"). Tests: new InMemoryMcpTaskStorePlus("user-1") or store.CreateTaskAsync(principal).

HTTP hosts call AddHttpContextAccessor() and pass a factory that resolves IHttpContextAccessor from the built provider.

Form elicitation

var result = await server.ElicitAsync(
    FormElicitation.Create($"How should we query {entitySet}?")
        .String("filter").Title("$filter")
        .Integer("top").Title("$top").Min(1).Max(1000).Default(20),
    cancellationToken);

var typed = await server.ElicitAsync(
    FormElicitation.From<ProductQuery>("Query products").Exclude(x => x.Skip),
    cancellationToken);

Keep the builder and add a field per name when the shape comes from metadata. From<T>() seeds a CLR type. Both work inside an MCP task: the SDK interceptor parks the form on the task when the tool awaits ElicitAsync. To park yourself: store.SetInputRequestsAsync(taskId, form).

IMcpTaskStorePlus extends IMcpTaskStore with ClaimsPrincipal overloads. McpTaskStoreBase takes a current-user callback and wires InputResponseReceived. CreateTaskAsync stamps the current user (NameIdentifier → sub → UPN → Name). tasks/get, tasks/update, and tasks/cancel return "not found" for another user's task. Server-side completion (SetCompletedAsync / SetFailedAsync / SetInputRequestsAsync) uses the owner recorded at create, because those calls run on a background DI scope after the original request is gone.

Durable stores

Core is the in-memory, single-process store. McpEssentials.EntityFrameworkCore and McpEssentials.Redis are the durable providers in this repo. Other packages (PostgreSQL, Cosmos, …) subclass McpTaskStoreBase the same way. See Authenticated Task Stores.

Documentation

• Docs: https://easyaf.dev/mcpessentials
• Source: https://github.com/CloudNimble/McpEssentials

License

MIT © CloudNimble, Inc.