Agents-Core
Related Servers
Alternatives to Agents-Core
- AlicenseNot gradedqualityBmaintenanceLocal-first MCP server providing persistent markdown memory with persona engine and fast search, designed to unify AI assistant memory across Claude Code, Cowork, and Dispatch.238 npm5MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceLocal MCP server for Claude Code providing persistent memory, task planning, and agent coordination with full transparency and no network calls.2MIT
- AlicenseAqualityDmaintenanceMCP server that spawns autonomous Claude Code agents in GitHub repos, enabling task delegation with persistent state, multi-step workflows, and job monitoring.4776 npm2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceUnified knowledge management and agent orchestration MCP server for Claude Code that remembers project patterns, assigns specialist agents, loads relevant knowledge into prompts, and tracks work across sessions to save time and reduce costs.1GPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables external MCP clients like Claude Desktop, Claude Code, Cursor and Zed to hand work to a local crew of AI agents that plan, write, check and fix code in a folder, while also acting as an MCP client that can use their tools. Runs locally with user-supplied keys, approval-gated commands, diffable and undoable runs.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceLocal MCP server that gives AI agents a project constitution (LAWS.md), a code graph (Compass), and a spec-driven workflow — all 100% local with no LLM or cloud.59 npm3MIT
- AlicenseNot gradedqualityAmaintenanceProvides a provider-agnostic MCP server that coordinates structured multi-agent workflows, owning task claims, action logs, handoffs, and server-side health gates for coding agents. It enables tracked specs, tasks, reviews, and verified completion across Claude Code, Codex CLI, Cursor, Grok Build, and OpenCode.29 npmMIT
TDQS
Scored across 48 tools
The set has many distinct domains, but several tools overlap in purpose: get_agent_context, route_and_load, refresh_persona_context, and load_implants all concern persona/agent activation; similarly, get_subagent_context and local_context_create both produce context-like packages. Descriptions are detailed and clarify boundaries, but the sheer number of activation/context/cooperation tools makes misselection plausible.
All names use snake_case and generally follow domain-prefixed patterns (local_, artifact_, cooperation_, flow, user_rule), which is predictable. Minor deviations exist in verb placement, such as local_generate versus local_generation_result and noun-first names like local_inference_status, but overall the convention is readable and consistent.
48 tools is far above the reasonable range for agent selection, even accounting for the server's broad platform scope. The surface is split into many subsystems, but the total count creates a high cognitive load and increases the chance of wrong tool selection.
The server covers a wide range of lifecycles: local inference, contexts, artifacts and manifests, cooperation, user rules, flows, agents, subagents, history, and repo summaries. Some minor gaps exist, such as no explicit cooperation unregister/release or local-context listing, but most workflows have complete create/read/update/delete coverage.