mcp-server-factory

MCP运维云端

提供方 diomonogatari

运维云端 stdio · 本地进程 会话登录 社区 / 第三方

McpServerFactory is an in-memory integration test harness for .NET Model Context Protocol (MCP) servers, enabling real client-server communication via in-memory pipes within a single process for dependency substitution and debugging.

一句话选型结论

按资料字段整理

mcp-server-factory 属于运维云端类 MCP 服务器,stdio · 本地进程,会话登录,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式stdio · 本地进程 鉴权会话登录 部署方式本地部署
GitHub 星标 1 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

Local Deployment In-memory Testing Dependency Injection C# Unit Testing MCP Protocol .NET Tool

适用场景

Local DeploymentIn-memory TestingDependency Injection

安装与配置

stdio · 本地进程 会话登录
客户端在本机拉起子进程,数据不出本机
  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 基础信息齐全,可以先按官方文档接入试跑。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
mcp-server-factory当前 未标注 stdio · 本地进程 本地部署 无 2026-06-05
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方diomonogatari上游标注的维护方 diomonogatari
分类运维云端本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-06-05上游最后核验时间

详细介绍

11.8 KB
来自项目仓库与上游目录的原文,未做删改

McpServerFactory

In-memory integration test harness for .NET Model Context Protocol (MCP) servers.

Your MCP server's real contract isn't with your code — it's with the model. The tool names
and JSON schemas, the descriptions the agent reads, the error text it sees, the sampling
round-trips it triggers. McpServerFactory boots your server in-process and connects a real
McpClient over in-memory pipes, so you can assert on that contract in a plain unit test:
breakpoints on both sides, dependencies swapped for fakes, no subprocess, no ports, no Docker,
no live model.

Think WebApplicationFactory — but for MCP.```csharp
// one process: a real client ⇄ your real server, over in-memory pipes
McpTestClient client = await factory.CreateTestClientAsync();

Assert.Equal("hello", await client.CallToolForTextAsync(
"echo", new Dictionary<string, object?> { ["message"] = "hello" }));


## What you can actually verify

- A tool **exists**, and its input schema/description are what you think (`GetToolAsync`, `McpAssert.ToolExistsAsync`).
- A tool returns the right **text** or **typed JSON** (`CallToolForTextAsync`, `CallToolForJsonAsync`).
- A tool **fails the way you intend** — `IsError` results throw instead of quietly passing a test (`CallToolExpectingErrorAsync`).
- **Server-initiated sampling** does the right thing, answered by a fake model you control (`FakeSamplingHandler`).
- The expected **notifications** fire — logging, progress, list-changed (`NotificationRecorder`).
- Your **real DI graph** wires up, with the slow/external bits mocked (`configureServices` / `ConfigureHost`).

&gt; **Scope:** by default the factory hosts the **tool/resource/prompt classes you register**
&gt; over an in-memory transport. It does not auto-run your server&#x27;s `Program.cs`. To exercise
&gt; your real composition root (configuration, options, hosted services), use the
&gt; `ConfigureHost` hook.

## Installation```bash
dotnet add package McpServerFactory

Template-based scaffolding

Install the template pack to bootstrap an MCP integration test project:```bash
dotnet new install McpServerFactory.Templates
dotnet new mcp-itest -n MyServer.Tests


The `mcp-itest` template accepts `--McpServerFactoryVersion` to override the
`McpServerFactory` package version; the default tracks the version of the
template pack you installed.

## Quick start```csharp
using McpServerFactory.Testing;
using Microsoft.Extensions.DependencyInjection;
using ModelContextProtocol.Server;
using Xunit;

[McpServerToolType]
public sealed class EchoTools
{
    [McpServerTool(Name = &quot;echo&quot;)]
    public string Echo(string message) =&gt; message;
}

public class EchoTests
{
    [Fact]
    public async Task Echo_ReturnsInput()
    {
        await using McpServerIntegrationFactory factory = new(
            configureMcpServer: builder =&gt; builder.WithTools&lt;EchoTools&gt;());

        // The factory owns the client; you do not dispose it yourself.
        McpTestClient client = await factory.CreateTestClientAsync();

        string text = await client.CallToolForTextAsync(
            &quot;echo&quot;,
            new Dictionary&lt;string, object?&gt; { [&quot;message&quot;] = &quot;hello&quot; });

        Assert.Equal(&quot;hello&quot;, text);
    }
}

Using xUnit? The companion McpServerFactory.Xunit package
boots the server once per test class via IClassFixture.

Why use this library

  • Fast and in-process — no subprocess, ports, Docker, or stdio plumbing.
  • Real protocol flow — a real McpClient over a real (in-memory) transport: tools/list,
    tools/call, resources, prompts, and server-initiated sampling all run end-to-end.
  • Easy dependency overrides — substitute services via configureServices.
  • Debuggable — set breakpoints on both sides; it's all one process.
  • Framework-agnostic core — works with xUnit, NUnit, and MSTest.

How it compares

Approach Speed No process/port Breakpoints both sides DI substitution Exercises real Program.cs
McpServerFactory fast ✅ ✅ ✅ via ConfigureHost
stdio subprocess + McpClient slow ❌ server only ❌ ✅
raw pipes + StreamClientTransport fast ✅ ✅ ✅ (manual) ❌
MCP Inspector (manual) n/a ❌ ❌ ❌ ✅

Use it when you want fast, automated, in-process tests of your tools/resources/prompts and
handlers with dependency substitution. Reach for a stdio subprocess instead when you must
validate the actual published binary, its real transport configuration, or process-level startup.

Used in the wild

stash-mcp — a 40-tool MCP server for Bitbucket
Server — tests its tools with McpServerFactory. It subclasses the factory, registers its real tool
assembly, and swaps the live Bitbucket client, cache, and resilience services for fakes, so the
whole tool surface is exercised in-process without ever touching a Bitbucket instance:```csharp
public sealed class StashMcpTestFactory(Action<StashMcpTestFactory>? configureMocks = null)
: McpServerFactory.Testing.McpServerFactory
{
public IBitbucketClient BitbucketClient { get; } = Substitute.For<IBitbucketClient>();

protected override void ConfigureMcpServer(IMcpServerBuilder builder) =&gt;
    builder.WithToolsFromAssembly(typeof(ProjectTools).Assembly);

protected override void ConfigureServices(IServiceCollection services) =&gt;
    services.AddSingleton(BitbucketClient); // ...plus cache, settings, resilience fakes

}


## Testing tools, resources, prompts, and structured output

`McpTestClient` wraps a real `McpClient` with test-shaped helpers (all pagination-safe):```csharp
McpTestClient client = await factory.CreateTestClientAsync();

string[] tools   = await client.GetToolNamesAsync();
string greeting  = await client.CallToolForTextAsync(&quot;greet&quot;);
MyDto result     = await client.CallToolForJsonAsync&lt;MyDto&gt;(&quot;compute&quot;, args); // structured or JSON-text
string contents  = await client.ReadResourceTextAsync(&quot;resource://config&quot;);
string[] prompts = await client.GetPromptNamesAsync();

Tool failures (IsError) no longer pass silently: CallToolForTextAsync throws
McpToolCallException, and CallToolExpectingErrorAsync asserts the negative path. The
framework-agnostic McpAssert helpers (ToolExistsAsync, Succeeded, IsError, TextEquals)
work under any test framework.

Testing server-initiated sampling

If your server calls the model (server-initiated sampling), wire a deterministic fake so tests
never need a real LLM:```csharp
FakeSamplingHandler sampling = FakeSamplingHandler.Returning("42");

await using McpServerIntegrationFactory factory = new(
configureMcpServer: builder => builder.WithTools<AskTools>(),
options: new McpServerFactoryOptions
{
ConfigureClient = client => client.UseSamplingHandler(sampling),
});

McpTestClient client = await factory.CreateTestClientAsync();
string answer = await client.CallToolForTextAsync(
"ask", new Dictionary<string, object?> { ["question"] = "..." });

Assert.Single(sampling.ReceivedRequests); // assert what the server asked the model


`ConfigureClient` exposes the full `McpClientOptions`, so you can also declare elicitation, roots,
or notification handlers. Capture server-sent notifications (logging, progress, list-changed) with
`NotificationRecorder.Attach(client.Inner)` and `await recorder.WaitForMethodAsync(...)`.

## Testing your real composition root

By default the factory hosts the classes you register. To exercise the same registration your
server&#x27;s `Program.cs` uses — real configuration binding, options, and hosted services — supply
`ConfigureHost`. The factory always owns the MCP server registration and the in-memory transport,
so configure everything **except** the transport; register tools/resources/prompts via
`configureMcpServer`:```csharp
await using McpServerIntegrationFactory factory = new(
    configureMcpServer: builder =&gt; builder.WithTools&lt;MyTools&gt;(),
    options: new McpServerFactoryOptions
    {
        ConfigureHost = builder =&gt;
        {
            builder.Configuration.AddInMemoryCollection(/* test config */);
            builder.Services.AddMyDomainServices();   // your real registration, minus the transport
        },
    });

Boot once per class with xUnit

Install the companion package and derive a fixture:```bash
dotnet add package McpServerFactory.Xunit
``````csharp
using McpServerFactory.Testing.Xunit;

public sealed class EchoFixture : McpServerFixture
{
protected override void ConfigureMcpServer(IMcpServerBuilder builder) => builder.WithTools<EchoTools>();
}

public sealed class EchoTests(EchoFixture fixture) : IClassFixture<EchoFixture>
{
[Fact]
public async Task Echoes() =>
Assert.Equal("hi", await fixture.TestClient.CallToolForTextAsync(
"echo", new Dictionary<string, object?> { ["message"] = "hi" }));
}


## Behavioral guarantees

- `CreateClientAsync` / `CreateTestClientAsync` are thread-safe and idempotent per factory instance.
- Concurrent calls return the same connected client; **the factory owns and disposes it** — you do
  not need to dispose the returned client yourself.
- Startup failures do not leak the temporary host instance or its pipes.
- `DisposeAsync` is safe to call multiple times and is bounded by `ShutdownTimeout` (it will not hang
  teardown).
- `CreateClientAsync` throws `ObjectDisposedException` after disposal.
- Need independent server instances (isolation)? Create multiple factory instances — each owns its
  own host. A single factory exposes one in-memory session.

## Compatibility and support

- Target frameworks: `net8.0`, `net9.0`, `net10.0`.
- MCP SDK dependency: `ModelContextProtocol` `1.4.0`.
- Compatibility promise: each package release is validated against the pinned MCP SDK version on all
  target frameworks.
- Upgrade policy: MCP SDK bumps are explicit and called out in CHANGELOG.md. Now that
  the MCP SDK is stable, `McpServerFactory` follows Semantic Versioning: an MCP
  SDK change that breaks this library&#x27;s public surface ships as a new major version.

| McpServerFactory | MCP SDK | Target frameworks |
| --- | --- | --- |
| 1.0.x | 1.4.0 | net8.0, net9.0, net10.0 |
| 0.2.x | 0.4.0-preview.3 | net8.0, net9.0, net10.0 |
| 0.1.x | 0.4.0-preview.3 | net10.0 |

## API overview

- `McpServerFactory` / `McpServerIntegrationFactory`
  - Start an in-process server host; create a connected client via `CreateClientAsync()` or a
    factory-owned wrapper via `CreateTestClientAsync()`.
  - Expose `Services` for DI validation after startup.
- `McpServerFactoryOptions`
  - Configure server identity, timeouts, instructions, logging, the client (`ConfigureClient`), and
    the host composition root (`ConfigureHost`).
- `McpTestClient`
  - Wrapper with tool, resource, prompt, structured-output, and server-metadata helpers.
- `FakeSamplingHandler` / `NotificationRecorder` / `McpAssert`
  - Deterministic sampling, notification capture, and framework-agnostic assertions.
- `McpServerFactory.Xunit` (separate package)
  - `McpServerFixture` for `IClassFixture` boot-once-per-class.

## Logging in test output

By default, host logging providers are suppressed to keep test output clean.
To enable custom logging during tests:```csharp
using Microsoft.Extensions.Logging;

var options = new McpServerFactoryOptions
{
    SuppressHostLogging = false,
    ConfigureLogging = logging =&gt; logging.SetMinimumLevel(LogLevel.Debug),
};

Release notes

See CHANGELOG.md for release history and upcoming changes.

Samples

  • Minimal runnable sample: samples/MinimalSmoke

Repository layout

  • src/McpServerFactory — reusable factory library (framework-agnostic core).
  • src/McpServerFactory.Xunit — xUnit fixtures (McpServerFixture).
  • tests/McpServerFactory.Tests — unit/integration-focused library tests.
  • templates/McpServerFactory.Templates — dotnet new template pack.
  • samples/MinimalSmoke — runnable sample console app.
  • docs — architecture notes and usage guidance.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
mcp-server-factory 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

mcp-server-factory 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

mcp-server-factory 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

mcp-server-factory 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

mcp-server-factory 能提供哪些能力?

资料显示能力标签包括 Local Deployment、In-memory Testing、Dependency Injection、C#、Unit Testing、MCP Protocol。具体工具清单以官方文档为准。

mcp-server-factory 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

mcp-server-factory 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-06-05。