Nall.Hangfire.Mcp
Remote MCP server for Hangfire that exposes background jobs as dynamic MCP tools, allowing clients like VS Code to inspect, trigger, and manage jobs in-process.
README
Nall.Hangfire.Mcp
Remote MCP server for Hangfire — exposes background jobs as MCP tools, in-process with the Hangfire server.
📖 Documentation: https://nikiforovall.github.io/hangfire-mcp-dotnet/
Design
- In-process. Runs inside the ASP.NET host that runs Hangfire. No out-of-process assembly loading.
- Remote. Streamable HTTP endpoint at
/mcp. Any MCP client (VS Code, Claude Desktop, custom agents) can connect. - Zero ceremony. No attributes, no shim interfaces — discovery reads what you already register with Hangfire.
- Schema from
MethodInfo. JSON Schema generated per method. Required vs. optional respects both C# defaults and nullable annotations (int?,string?).
Getting started
Install:
dotnet add package Nall.Hangfire.Mcp
Minimum host setup — three lines on top of an existing Hangfire app:
builder.Services.AddHangfireMcp(); // registers MCP server + JobCatalog
var app = builder.Build();
app.MapHangfireMcp("/mcp"); // streamable HTTP endpoint
Full minimal example:
using Hangfire;
using Nall.Hangfire.Mcp;
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddHangfire(cfg => cfg.UsePostgreSqlStorage(...));
builder.Services.AddHangfireServer();
builder.Services.AddHangfireMcp();
var app = builder.Build();
app.MapHangfireDashboard();
app.MapHangfireMcp("/mcp");
app.Services.GetRequiredService<IRecurringJobManager>()
.AddOrUpdate<IReportJob>("report.daily", j => j.GenerateAsync(2026, "pdf", null), Cron.Daily);
app.Run();
Every recurring job is now an MCP tool: Run_report.daily with a JSON Schema derived from GenerateAsync's parameters.
VS Code MCP config:
{
"servers": {
"hangfire": { "url": "https://your-host/mcp" }
}
}
Discovery sources
| Source | What it sees | When to use |
|---|---|---|
RecurringStorage (default) |
RecurringJobDto.Job from Hangfire storage. |
Every recurring job is a tool. |
StaticManifest |
Compile-time scan of AddOrUpdate / Enqueue / Schedule call sites via the optional Nall.Hangfire.Mcp.Generator source generator. |
Expose helper methods you only ever one-shot enqueue, or jobs not yet registered as recurring. |
All |
Union of both, deduped by (DeclaringType, MethodInfo). |
Most apps. |
Configure via AddHangfireMcp:
builder.Services.AddHangfireMcp(o =>
{
o.Sources = JobDiscoverySources.All; // default: RecurringStorage
o.Filter = rj => rj.Id.StartsWith("public."); // optional storage filter
});
To populate the manifest, install the generator package in each project that contains Hangfire registration calls:
dotnet add package Nall.Hangfire.Mcp.Generator
Built-in maintenance tools
Every MCP server hosted by AddHangfireMcp() also exposes a fixed set of hangfire_* tools for inspecting and managing jobs alongside the dynamic Run_* tools:
| Tool | Purpose |
|---|---|
hangfire_get_statistics |
Global counters: Enqueued/Failed/Processing/Scheduled/Succeeded/Deleted/Recurring/Retries/Servers. |
hangfire_list_jobs |
Page jobs by state with optional filter. Use this to discover ids before bulk ops. |
hangfire_get_job |
Full details + state history for one id. |
hangfire_delete_job |
Move one job to Deleted. |
hangfire_requeue_job |
Requeue one job (covers retry of Failed). |
hangfire_delete_jobs |
Bulk delete by ids or filter (exactly one). |
hangfire_requeue_jobs |
Bulk requeue by ids or filter. |
Filter shape (used by list_jobs, delete_jobs, requeue_jobs):
{
"state": "Failed",
"queue": "default",
"jobType": "ReportJob",
"method": "Generate",
"messageContains": "timeout",
"exceptionContains": "SqlException"
}
jobType and method are case-insensitive substring matches. messageContains / exceptionContains are most useful for Failed.
Parameter binding
For each tool call:
- C# default → used when the argument is omitted.
- Nullable type (
T?value or annotated reference) and no default → bound tonullwhen omitted. - Otherwise required; missing argument returns an MCP error.
Authentication
MapHangfireMcp returns IEndpointConventionBuilder — the library is auth-agnostic. Chain any ASP.NET Core auth scheme:
app.MapHangfireMcp("/mcp")
.RequireAuthorization(p => p.RequireAuthenticatedUser()
.AddAuthenticationSchemes(McpAuthenticationDefaults.AuthenticationScheme));
- OAuth 2.1 / OIDC —
samples/Webwires Keycloak + JwtBearer +AddMcp()fromModelContextProtocol.AspNetCore.Authenticationto advertise RFC 9728 protected-resource-metadata. End-to-end flow, standards, and gotchas: docs/authentication.md. - API keys / custom schemes — nothing MCP-specific required. Implement an
AuthenticationHandler<T>, register it, and pass its scheme toRequireAuthorizationabove. TheRun_*andhangfire_*tools work the same regardless of how the principal got there.
Sample
samples/Web exercises overloads, complex objects, enums, collections, defaults, nullable optionals, and manifest-only one-shot jobs. GET /jobs lists the discovered catalog.
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。