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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.