by scottgl9 · MCP Server · ★ 26
Agentic workflows you can actually ship to production. Typed TypeScript pipelines · default-deny permissions · a gateway you own. Why skelm? Most agent frameworks make it easy to demo a chatbot and impossible to operate one. Tool calls leak credentials, prompts mutate at runtime, and the production story is "trust us." Visual automation tools hide everything in a node graph that can't be diffed, code-reviewed, or unit-tested. Long-running orchestration engines force you to learn a separate runtime, separate DSL, and separate operational model for every kind of work.
| Stars | 26 |
| Forks | 8 |
| Language | TypeScript |
| Category | MCP Server |
| License | MIT |
| Quality Score | 68.7397625931472/100 |
| Open Issues | 44 |
| Last Updated | 2026-06-15 |
| Created | 2026-05-03 |
| Platforms | codex, mcp, node |
| Est. Tokens | ~17k |
Explore other popular mcp server tools:
skelm is skelm - open-source flexible agentic workflow engine for secure, long-running workflows. Authoring, scheduling, and operating typed pipelines that mix code, inference, and agents under default-deny pe. It is categorized as a MCP Server with 26 GitHub stars.
skelm is primarily written in TypeScript. It covers topics such as acp, agent, agentic.
You can find installation instructions and usage details in the skelm GitHub repository at github.com/scottgl9/skelm. The project has 26 stars and 8 forks, indicating an active community.
skelm is released under the MIT license, making it free to use and modify according to the license terms.