---
title: "workflow-core vs awesome-mcp-servers"
type: "comparison"
canonical_url: "https://www.graphcanon.com/compare/danielgerlag-workflow-core-vs-punkpeye-awesome-mcp-servers"
tools: ["danielgerlag-workflow-core", "punkpeye-awesome-mcp-servers"]
---

# workflow-core vs awesome-mcp-servers

*GraphCanon updated Jul 15, 2026*

## Verdict

Pick workflow-core when tags unique to workflow-core: c#, hacktoberfest, saga, saga-transactions; pick awesome-mcp-servers when tags unique to awesome-mcp-servers: ai, mcp, server-resources.

[workflow-core](https://github.com/danielgerlag/workflow-core) reports 5.9k GitHub stars, 1.3k forks, and 219 open issues, last pushed May 18, 2026. [awesome-mcp-servers](https://glama.ai/mcp/servers) has 91k stars, 13k forks, and 2.6k open issues, last pushed Jul 4, 2026. Figures are from public GitHub metadata via [workflow-core's repository](https://github.com/danielgerlag/workflow-core) and [awesome-mcp-servers's repository](https://github.com/punkpeye/awesome-mcp-servers).

| | [workflow-core](/tools/danielgerlag-workflow-core.md) | [awesome-mcp-servers](/tools/punkpeye-awesome-mcp-servers.md) |
| --- | --- | --- |
| Tagline | Lightweight workflow engine for .NET Standard | A collection of MCP servers |
| Stars | 5,899 | 90,602 |
| Forks | 1,264 | 12,821 |
| Open issues | 219 | 2,557 |
| Language | C# | - |
| Adopt for | - | awesome-mcp-servers is a collection focused specifically on MCP servers with an emphasis on AI integration. |
| Persona | - | - |
| Runtime | - | - |
| License | MIT | MIT |
| Categories | Developer Tools | Developer Tools |

## Trust and health

_Sourced signals - not a safety guarantee. No winner column._

| | [workflow-core](/tools/danielgerlag-workflow-core.md) | [awesome-mcp-servers](/tools/punkpeye-awesome-mcp-servers.md) |
| --- | --- | --- |
| Maintenance | Steady (60%) | Very active (96%) |
| Days since push | 57d | 6d |
| Open issues (now) | 219 | 2.6k |
| Full report | [trust report](/tools/danielgerlag-workflow-core/trust.md) | [trust report](/tools/punkpeye-awesome-mcp-servers/trust.md) |

## Decision facts: awesome-mcp-servers

- **Adopt for:** awesome-mcp-servers is a collection focused specifically on MCP servers with an emphasis on AI integration.

## Choose when

### Choose workflow-core if…

- Tags unique to workflow-core: c#, hacktoberfest, saga, saga-transactions.
- Leaner open-issue backlog (219).

### Choose awesome-mcp-servers if…

- Tags unique to awesome-mcp-servers: ai, mcp, server-resources.
- If your project requires detailed resources and tools around MCP server capabilities for AI projects, awesome-mcp-servers is well-suited as it focuses solely on this niche area of technology.
- More GitHub stars (91k vs 5.9k) - visibility, not fit.

## When NOT to use workflow-core

- Developer Tools: A gateway is overkill when you're pinned to a single provider and model.

## When NOT to use awesome-mcp-servers

- Avoid using awesome-mcp-servers if your project does not involve utilizing or exploring the specific functionalities of MCP servers in relation to AI applications.

## Common questions

### What is the difference between workflow-core and awesome-mcp-servers?

workflow-core: Lightweight workflow engine for .NET Standard. awesome-mcp-servers: A collection of MCP servers. See the comparison table for live GitHub stats and shared categories.

### When should I choose workflow-core over awesome-mcp-servers?

Choose workflow-core over awesome-mcp-servers when Tags unique to workflow-core: c#, hacktoberfest, saga, saga-transactions; Leaner open-issue backlog (219).

### When should I choose awesome-mcp-servers over workflow-core?

Choose awesome-mcp-servers over workflow-core when Tags unique to awesome-mcp-servers: ai, mcp, server-resources; If your project requires detailed resources and tools around MCP server capabilities for AI projects, awesome-mcp-servers is well-suited as it focuses solely on this niche area of technology; More GitHub stars (91k vs 5.9k) - visibility, not fit.

### When should I avoid workflow-core?

Developer Tools: A gateway is overkill when you're pinned to a single provider and model.

### When should I avoid awesome-mcp-servers?

Avoid using awesome-mcp-servers if your project does not involve utilizing or exploring the specific functionalities of MCP servers in relation to AI applications.

### Is workflow-core or awesome-mcp-servers more popular on GitHub?

awesome-mcp-servers has more GitHub stars (90,602 vs 5,899). Stars measure visibility, not whether either tool fits your constraints.

### Are workflow-core and awesome-mcp-servers open source?

Yes - both are open-source projects on GitHub (workflow-core: MIT, awesome-mcp-servers: MIT).

### Where can I find alternatives to workflow-core or awesome-mcp-servers?

GraphCanon lists graph-backed alternatives at [workflow-core alternatives](/tools/danielgerlag-workflow-core/alternatives) and [awesome-mcp-servers alternatives](/tools/punkpeye-awesome-mcp-servers/alternatives) ([workflow-core markdown twin](/tools/danielgerlag-workflow-core/alternatives.md), [awesome-mcp-servers markdown twin](/tools/punkpeye-awesome-mcp-servers/alternatives.md)), ranked by typed relationship edges rather than popularity votes.

### Is there a machine-readable version of this comparison?

Yes. The markdown twin at [this comparison](/compare/danielgerlag-workflow-core-vs-punkpeye-awesome-mcp-servers.md) mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.

### Which is better maintained, workflow-core or awesome-mcp-servers?

workflow-core: Steady. awesome-mcp-servers: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.

### Where are the full trust reports for workflow-core and awesome-mcp-servers?

GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: [workflow-core trust report](/tools/danielgerlag-workflow-core/trust); [awesome-mcp-servers trust report](/tools/punkpeye-awesome-mcp-servers/trust).

---

**Machine-readable endpoints**

- JSON: [`/api/graphcanon/graph?tool=danielgerlag-workflow-core`](/api/graphcanon/graph?tool=danielgerlag-workflow-core)
- LLM index: [/llms.txt](/llms.txt)
- Full corpus: [/llms-full.txt](/llms-full.txt)

_GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_
