JamJet
Related Servers
Alternatives to JamJet
- AlicenseNot gradedqualityCmaintenanceDurable memory MCP server for AI agents. Temporal knowledge graph with hybrid semantic + keyword retrieval, LLM-powered fact extraction, conflict detection, and consolidation. Backed by SQLite or PostgreSQL. 11 MCP tools, 6 LLM provider backends. Part of JamJet.Apache 2.0
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnterprise-grade asynchronous multi-agent orchestration and MCP router mesh framework, enabling DAG-based workflows, consensus-driven agent swarms, and REST/telemetry gateway.MIT
- AlicenseNot gradedqualityAmaintenanceAn agent workflow engine exposed over MCP that lets AI agents execute node-graph workflows, following per-step directives with explicit completion conditions and JSON-Schema-validated inputs and outputs to move between success, failure, and conditional branches. It can be self-hosted in a single Docker container with OAuth 2.1 authentication and a supplementary web UI for managing and visualizing workflows.128Apache 2.0
- AlicenseNot gradedqualityAmaintenanceServer-enforced workflow discipline for AI agents. An MCP server providing persistent work items, dependency graphs, quality gates, and actor attribution. Schemas define what agents must produce — the server blocks the call if they don't. Works with any MCP-compatible client.209MIT
- FlicenseCqualityAmaintenanceSelf-hosted, source-available AI workflow automation platform. Build multi-agent, RAG, and tool-using pipelines on a visual canvas and publish any workflow as an MCP server (stdio/SSE/Streamable HTTP). Also an MCP client via the agent node.21,221-
- FlicenseAqualityDmaintenanceAn agent-native workflow MCP server that enables AI agents to execute text-defined, versionable workflows with checkpointing and state management.108 npm-
- FlicenseNot gradedqualityDmaintenanceA runtime for inspectable agent workflows that provides MCP tools, bounded Python execution, session memory, and deterministic evaluation.-
TDQS
Scored across 8 tools
Each tool has a distinct purpose: running, canceling, approving, listing/getting executions, retrieving events, and discovering/listing agents. No overlaps or ambiguous boundaries; an agent can easily select the right tool based on the response need.
All tools follow the consistent pattern of 'jamjet_' prefix followed by a clear verb_noun (e.g., cancel_execution, list_agents, run_workflow). The only exception is 'jamjet_approve' which omits the noun, but it's still intuitive and doesn't break the overall pattern.
8 tools is well-scoped for a workflow execution and agent discovery server. Each tool serves a necessary function without redundancy, covering execution lifecycle and agent management adequately.
The tool set covers the full execution lifecycle (run, get, list, cancel, approve) and agent registration/discovery (discover, list). The inclusion of event logs provides detailed debugging. No obvious missing operations for the stated domain.