RestClient.Net

MCP开发工具

提供方 MelbourneDeveloper · 包名 restclient.net

开发工具 stdio · 本地进程 未标注 社区 / 第三方 Claude DesktopCursorClineClaude Code
查看接入方式

The safest way to make REST calls in C# with an MCP Generator

一句话选型结论

按资料字段整理

RestClient.Net 属于开发工具类 MCP 服务器,stdio · 本地进程,鉴权方式未标注,可直接接入 Claude Desktop、Cursor、Cline 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

csharp json rest-client web-api

支持客户端

适用场景

csharpjsonrest-client

安装与配置

stdio · 本地进程 未标注
客户端在本机拉起子进程,数据不出本机
git clone https://github.com/MelbourneDeveloper/RestClient.Net && cd restclient.net

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Cross-platform,再按安装命令拉取依赖。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

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

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Cursor、Cline,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
RestClient.Net当前 未标注 stdio · 本地进程 本地部署 有 2026-04-19
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

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

详细介绍

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

RestClient.Net

The safest way to make REST calls in C#

New! Generate MCP servers from OpenAPI specs!!!

Built from the ground up with functional programming, type safety, and modern .NET patterns. Successor to the original RestClient.Net.

What Makes It Different

This library is uncompromising in its approach to type safety and functional design:
- HttpClient extensions - Works with HttpClient lifecycle management via IHttpClientFactory.CreateClient()
- Result types - Explicit error handling without exceptions
- Exhaustiveness checking - Compile-time guarantees via Exhaustion
- Functional composition - Pure functions with no interfaces

Features

  • Generate an MCP Server and client code from an OpenAPI 3.x spec.
  • Result Types - Returns Result> with closed hierarchy types for compile-time safety (Outcome package)
  • Zero Exceptions - No exception throwing for predictable error handling
  • Progress Reporting - Built-in download/upload progress tracking
  • Polly Integration - Support for convention-based retry policies and resilience patterns
  • Async/Await Only - Modern async patterns throughout
  • HttpClient Extensions - Works with IHttpClientFactory.CreateClient() for proper pooled connections and DNS behavior handling
  • Exhaustiveness Checking - Uses Exhaustion for compile-time completeness guarantees (stopgap until C# adds discriminated unions)

The design focuses on discriminated unions for results, and adding the Exhaustion analyzer package gives you exhaustive pattern matching on type in C#. RestClient.Net is well ahead of the game. You can use discriminated unions with exhaustiveness checks in C# right now.

Installation

Install the core package:```bash
dotnet add package RestClient.Net


RestClient.Net installs the Exhaustion analyzer. Is is a Roslyn analyzer that provides compile-time exhaustiveness checking for pattern matching. Without it, you lose one of RestClient.Net's core safety guarantees.

## Usage

### Basic GET Request

A complete example making a GET request to JSONPlaceholder:```csharp
using System.Text.Json;
using RestClient.Net;
using Urls;

// Define models
internal sealed record Post(int UserId, int Id, string Title, string Body);
internal sealed record ErrorResponse(string Message);

// Create HttpClient (use IHttpClientFactory in production)
using var httpClient = new HttpClient();

// Make the GET call
var result = await httpClient
    .GetAsync(
        url: "https://jsonplaceholder.typicode.com/posts/1".ToAbsoluteUrl(),
        deserializeSuccess: DeserializePost,
        deserializeError: DeserializeError
    )
    .ConfigureAwait(false);

// Pattern match on the result - MUST handle all cases
var output = result switch
{
    OkPost(var post) =>
        $"Success: {post.Title} by user {post.UserId}",
    ErrorPost(ResponseErrorPost(var errorBody, var statusCode, _)) =>
        $"Error {statusCode}: {errorBody.Message}",
    ErrorPost(ExceptionErrorPost(var exception)) =>
        $"Exception: {exception.Message}",
};

Console.WriteLine(output);

async Task<Post?> DeserializePost(HttpResponseMessage response, CancellationToken ct) =>
    await JsonSerializer
        .DeserializeAsync<Post>(
            await response.Content.ReadAsStreamAsync(ct).ConfigureAwait(false),
            new JsonSerializerOptions { PropertyNameCaseInsensitive = true },
            cancellationToken: ct
        )
        .ConfigureAwait(false);

async Task<ErrorResponse?> DeserializeError(HttpResponseMessage response, CancellationToken ct) =>
    await JsonSerializer
        .DeserializeAsync<ErrorResponse>(
            await response.Content.ReadAsStreamAsync(ct).ConfigureAwait(false),
            new JsonSerializerOptions { PropertyNameCaseInsensitive = true },
            cancellationToken: ct
        )
        .ConfigureAwait(false);

Result Type and Type Aliases

C# doesn't officially support discriminated unions, but you can achieve closed type hierarchies with the sealed modifier. The Outcome package gives you a set of Result types designed for exhaustiveness checks. Until C# gains full discriminated union support, you need to add type aliases like this:```cs
// Type aliases for concise pattern matching (usually in GlobalUsings.cs)
global using OkPost = Outcome.Result<Post, Outcome.HttpError<ErrorResponse>>.Ok<Post, Outcome.HttpError<ErrorResponse>>;
global using ErrorPost = Outcome.Result<Post, Outcome.HttpError<ErrorResponse>>.Error<Post, Outcome.HttpError<ErrorResponse>>;
global using ResponseErrorPost = Outcome.HttpError<ErrorResponse>.ErrorResponseError;
global using ExceptionErrorPost = Outcome.HttpError<ErrorResponse>.ExceptionError;


If you use the OpenAPI generator, it will generate these type aliases for you automatically.

## OpenAPI Client and MCP Code Generation

Generate type-safe C# clients and MCP servers from OpenAPI specs.

### Client Generation```bash
dotnet add package RestClient.Net.OpenApiGenerator

Generate extension methods from OpenAPI 3.x specs:```csharp
// Generated code usage
using YourApi.Generated;

var httpClient = factory.CreateClient();

// All HTTP methods supported with Result types
var user = await httpClient.GetUserById("123", ct);
var created = await httpClient.CreateUser(newUser, ct);
var updated = await httpClient.UpdateUser((Params: "123", Body: user), ct);
var deleted = await httpClient.DeleteUser("123", ct);

// Pattern match on results
switch (user)
{
case OkUser(var success):
Console.WriteLine($"User: {success.Name}");
break;
case ErrorUser(var error):
Console.WriteLine($"Error: {error.StatusCode}");
break;
}


The generator creates extension methods on `HttpClient`, model classes from schemas, and result type aliases for pattern matching.

### MCP Server Generation

Generate Model Context Protocol servers for Claude Code from OpenAPI specs:```bash
# Generate API client first
dotnet run --project RestClient.Net.OpenApiGenerator.Cli -- \
  -u api.yaml \
  -o Generated \
  -n YourApi.Generated

# Generate MCP tools from the same spec
dotnet run --project RestClient.Net.McpGenerator.Cli -- \
  --openapi-url api.yaml \
  --output-file Generated/McpTools.g.cs \
  --namespace YourApi.Mcp \
  --server-name YourApi \
  --ext-namespace YourApi.Generated \
  --tags &quot;Search,Resources&quot;

The MCP generator wraps the generated extension methods as MCP tools that Claude Code can invoke.

Complete example: See Samples/NucliaDbClient.McpServer for a working MCP server built from the NucliaDB OpenAPI spec. The example includes:
- Generated client code (Samples/NucliaDbClient/Generated)
- Generated MCP tools (NucliaDbMcpTools.g.cs)
- MCP server host project (NucliaDbClient.McpServer)
- Docker Compose setup for NucliaDB
- Claude Code integration script (run-for-claude.sh)

Exhaustiveness Checking with Exhaustion

Exhaustion is integral to RestClient.Net's safety guarantees. It's a Roslyn analyzer that ensures you handle every possible case when pattern matching on Result types.

What Happens Without Exhaustion

If you remove a switch arm and don't have Exhaustion installed, the code compiles but may crash at runtime:```csharp
// DANGEROUS - compiles but may throw at runtime
var output = result switch
{
OkPost(var post) => $"Success: {post.Title}",
ErrorPost(ResponseErrorPost(var errorBody, var statusCode, _)) =>
$"Error {statusCode}: {errorBody.Message}",
// Missing ExceptionErrorPost case - will throw at runtime if an exception occurs!
};


### What Happens With Exhaustion

With Exhaustion installed, the compiler **catches this at build time**:```
error EXHAUSTION001: Switch on Result is not exhaustive;
Matched: Ok&lt;Post, HttpError&lt;ErrorResponse&gt;&gt;, Error&lt;Post, HttpError&lt;ErrorResponse&gt;&gt; with ErrorResponseError&lt;ErrorResponse&gt;
Missing: Error&lt;Post, HttpError&lt;ErrorResponse&gt;&gt; with ExceptionError&lt;ErrorResponse&gt;

Your build fails until you handle all cases. This is the difference between runtime crashes and compile-time safety.

Installing Exhaustion Without RestClient.Net

Add it to your project:```bash
dotnet add package Exhaustion


Exhaustion works by analyzing sealed type hierarchies in switch expressions and statements. When you match on a `Result&gt;`, it knows there are exactly three possible cases:
- `Ok&gt;` - Success case
- `Error&gt;` with `ErrorResponseError` - HTTP error response
- `Error&gt;` with `ExceptionError` - Exception during request

If you don&#x27;t handle all three, your code won&#x27;t compile.

### Progress Reporting

You can track upload progress with `ProgressReportingHttpContent`. This example writes to the console when there is a progress report.```csharp
var fileBytes = await File.ReadAllBytesAsync(&quot;document.pdf&quot;);

using var content = new ProgressReportingHttpContent(
    fileBytes,
    progress: (current, total) =&gt;
        Console.WriteLine($&quot;Progress: {current}/{total} bytes ({current * 100 / total}%)&quot;)
);

var httpClient = httpClientFactory.CreateClient();
var result = await httpClient.PostAsync&lt;UploadResponse, string&gt;(
    url: &quot;https://api.example.com/upload&quot;.ToAbsoluteUrl(),
    requestBody: content,
    deserializeSuccess: (r, ct) =&gt; r.Content.ReadFromJsonAsync&lt;UploadResponse&gt;(ct),
    deserializeError: (r, ct) =&gt; r.Content.ReadAsStringAsync(ct)
);

Mocking with Delegating Handlers for Tests

Mock HTTP calls by inheriting from DelegatingHandler and overriding SendAsync (see Microsoft docs):```csharp
class MockHandler : DelegatingHandler
{
protected override Task<HttpResponseMessage> SendAsync(
HttpRequestMessage request, CancellationToken cancellationToken)
{
var response = (request.Method.Method, request.RequestUri?.PathAndQuery) switch
{
("GET", "/posts/1") => new HttpResponseMessage(HttpStatusCode.OK)
{
Content = JsonContent.Create(new Post(1, 1, "Title", "Body"))
},
("POST", "/posts") => new HttpResponseMessage(HttpStatusCode.Created)
{
Content = JsonContent.Create(new { Id = 101 })
},
_ => new HttpResponseMessage(HttpStatusCode.NotFound)
};

    return Task.FromResult(response);
}

}

// Create HttpClient with mock handler
var httpClient = new HttpClient(new MockHandler());

// Make calls - they hit the mock handler
var result = await httpClient.GetAsync(
url: "https://api.example.com/posts/1".ToAbsoluteUrl(),
deserializeSuccess: DeserializePost,
deserializeError: DeserializeError
);

// Result contains mocked data
result switch
{
OkPost(var post) => Console.WriteLine($"Got mocked post: {post.Title}"),
ErrorPost(var error) => Console.WriteLine($"Error: {error.StatusCode}")
};


## Upgrading from RestClient.Net 6.x

You can continue to use the V6 `IClient` interface with RestClient .Net 7. RestClient.Net 7 is a complete rewrite with a functional architecture. For existing v6 users, **RestClient.Net.Original** provides a polyfill that implements the v6 `IClient` interface using v7 under the hood.

### Using the Polyfill

Install both packages:```bash
dotnet add package RestClient.Net.Original
dotnet add package RestClient.Net.Abstractions --version 6.0.0

Use Client to maintain v6 compatibility while benefiting from v7's improvements:```csharp
using RestClient.Net;

var client = new Client(
httpClientFactory,
baseUrl: "https://api.example.com".ToAbsoluteUrl(),
defaultRequestHeaders: new HeadersCollection(),
throwExceptionOnFailure: true
);

// Continue using your existing v6 IClient extension methods
var user = await client.GetAsync<User>("users/123");
var created = await client.PostAsync<User, CreateUserRequest>(newUser, "users");
var updated = await client.PutAsync<User, UpdateUserRequest>(updateUser, "users/123");
var deleted = await client.DeleteAsync("users/123");
```

This approach allows gradual migration. You can keep your existing implementations working while incrementally adopting v7's functional patterns.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
RestClient.Net 怎么安装?

在客户端按下面的安装命令接入:git clone https://github.com/MelbourneDeveloper/RestClient.Net && cd restclient.net。对应的包名是 restclient.net。装完在客户端配置里引用同一个包或端点。

RestClient.Net 怎么在 Claude Desktop、Cursor、Cline 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

RestClient.Net 收费吗?

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

RestClient.Net 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

RestClient.Net 支持哪些客户端?

资料标注支持 Claude Desktop、Cursor、Cline、Claude Code;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

RestClient.Net 能提供哪些能力?

资料显示能力标签包括 csharp、json、rest-client、web-api。具体工具清单以官方文档为准。

RestClient.Net 需要什么运行环境?

运行时为 Cross-platform;属于本地进程,需要在本机装好运行环境。

RestClient.Net 是本地还是远程?

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

热门专题

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

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