agent-kernel-mcp
Related Servers
Alternatives to agent-kernel-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables an AI agent to run local tools on the user's own machine via stdio, including command execution, workspace file read/write, and system status checks.52MIT
- AlicenseNot gradedqualityAmaintenanceEnables compatible agents to call registered local tools and read resources through one stdio server, including harness preparation, knowledge search and document management, memory retention/recall, correction proposals, advisory decisions, tool/skill discovery, and log/source inspection.2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to use an approved session to inspect capabilities, manage projects and memories, perform bounded reads, and make journaled changes through a stdio interface.29 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude Desktop or Claude Code to drive the local daemon through stdio, listing agents and sessions, running agents, and reporting costs.-
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code, Cursor, OpenCode/LunaCode, and other MCP clients to invoke the harness's shell, file, code, scheduling, and device-control tools over stdio.MIT

Consail MCPofficial
FlicenseNot gradedqualityCmaintenanceConnects agents to Consail over local stdio, providing read-only, allowlisted tools to inspect environments, catalogs, datasets, actions, and validate pipelines without exposing database credentials or secret APIs.-
TDQS
Scored across 12 tools
Most tools clearly target distinct resources and actions, such as projects, assignments, runs, and health. The only mild ambiguity is between ak_nudge and ak_scheduler_tick, since both can trigger executor work, but their descriptions clarify the difference.
All tools share a consistent ak_ prefix and snake_case style, which helps readability. However, the set mixes verb_noun names like ak_list_projects with noun-only names like ak_health, ak_attention, and ak_me, so the pattern is not fully uniform.
12 tools is well within the ideal range and each tool serves a distinct operational area of the agent-kernel domain. The count feels appropriately scoped without redundancy or obvious bloat.
The surface covers listing and reading projects, assignments, and runs, plus scheduler and executor actions. Notable gaps include no way to update executor settings, cancel or retry runs, or get a single assignment by id, which limits full control-plane coverage.