Install
$ agentstack add mcp-nikiforovall-hangfire-mcp ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Hangfire MCP [](https://github.com/NikiforovAll/hangfire-mcp/actions/workflows/build.yml)
Enqueue background jobs using Hangfire MCP server.
Motivation
Interaction with Hangfire using Hangfire MCP Server allows you to enqueue jobs from any client that supports MCP protocol. For example, you can use Hangfire MCP directly from VS Code in Agent Mode and enqueue jobs. It makes possible to execute any kind of code without writing additional code.
Here is MCP Server configuration for VS Code:
{
"servers": {
"hangfire-mcp": {
"url": "http://localhost:3001"
}
}
}
Code Example
Here is how it works:
sequenceDiagram
participant User as User
participant MCPHangfire as MCP Hangfire
participant IBackgroundJobClient as IBackgroundJobClient
participant Database as Database
participant HangfireServer as Hangfire Server
User->>MCPHangfire: Enqueue Job
MCPHangfire->>IBackgroundJobClient: Send Job Message
IBackgroundJobClient->>Database: Store Job Message
HangfireServer->>Database: Fetch Job Message
HangfireServer->>HangfireServer: Process Job
Standalone Mode
It is a regular MCP packaged as .NET global tool. Here is how to setup it as an MCP server in VSCode.
dotnet tool install --global --add-source Nall.HangfireMCP
Configuration:
{
"servers": {
"hangfire-mcp-standalone": {
"type": "stdio",
"command": "HangfireMCP",
"args": [
"--stdio"
],
"env": {
"HANGFIRE_JOBS_ASSEMBLY": "path/to/Jobs.dll",
"HANGFIRE_JOBS_MATCH_EXPRESSION": "[?IsInterface && contains(Name, 'Job')]",
"HANGFIRE_CONNECTION_STRING": "Host=localhost;Port=5432;Username=postgres;Password=postgres;Database=hangfire"
}
}
}
}
Aspire
var builder = DistributedApplication.CreateBuilder(args);
var postgresServer = builder
.AddPostgres("postgres-server")
.WithDataVolume()
.WithLifetime(ContainerLifetime.Persistent);
var postgresDatabase = postgresServer.AddDatabase("hangfire");
builder.AddProject("server")
.WithReference(postgresDatabase)
.WaitFor(postgresDatabase);
var mcp = builder
.AddProject("hangfire-mcp")
.WithEnvironment("HANGFIRE_JOBS_ASSEMBLY", "path/to/Jobs.dll")
.WithEnvironment("HANGFIRE_JOBS_MATCH_EXPRESSION", "[?IsInterface && contains(Name, 'Job')]")
.WithReference(postgresDatabase)
.WaitFor(postgresDatabase);
builder
.AddMCPInspector()
.WithSSE(mcp)
.WaitFor(mcp);
builder.Build().Run();
As result, the jobs are dynamically loaded from the specified assembly and can be enqueued using MCP protocol. The rules for matching job names can be specified using HANGFIRE_JOBS_MATCH_EXPRESSION environment variable. For example, the expression [?IsInterface && contains(Name, 'Job')] will match all interfaces that contain "Job" in their name. It is a JMESPath expression, so you can define how to match job names according to your needs.
Custom Setup (as Code) Mode
You can create your own MCP server and use this project as starting point. You can extend it with your own tools and features. Here is an example of how to set up Hangfire MCP server in a custom project.
Aspire
var builder = DistributedApplication.CreateBuilder(args);
var postgresServer = builder
.AddPostgres("postgres-server")
.WithDataVolume()
.WithLifetime(ContainerLifetime.Persistent);
var postgresDatabase = postgresServer.AddDatabase("hangfire");
builder.AddProject("server")
.WithReference(postgresDatabase)
.WaitFor(postgresDatabase);
var mcp = builder
.AddProject("hangfire-mcp")
.WithReference(postgresDatabase)
.WaitFor(postgresDatabase);
builder
.AddMCPInspector()
.WithSSE(mcp)
.WaitFor(mcp);
builder.Build().Run();
MCP Server
var builder = WebApplication.CreateBuilder(args);
builder.WithMcpServer(args).WithToolsFromAssembly();
builder.Services.AddHangfire(cfg => cfg.UsePostgreSqlStorage(options =>
options.UseNpgsqlConnection(builder.Configuration.GetConnectionString("hangfire")))
);
builder.Services.AddHangfireMcp();
builder.Services.AddTransient();
var app = builder.Build();
app.MapMcpServer(args);
app.Run();
Here is an example of the Hangfire tool:
[McpServerToolType]
public class HangfireTool(IHangfireDynamicScheduler scheduler)
{
[McpServerTool(Name = "RunJob")]
public string Run(
[Required] string jobName,
[Required] string methodName,
Dictionary? parameters = null
)
{
var descriptor = new JobDescriptor(jobName, methodName, parameters);
return scheduler.Enqueue(descriptor, typeof(ITimeJob).Assembly);
}
}
Tools
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: NikiforovAll
- Source: NikiforovAll/hangfire-mcp
- License: MIT
- Homepage: https://www.nuget.org/packages/Nall.HangfireMCP
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.