A
licenseA
qualityB
maintenanceEnables 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.
5
2
MIT
agent-kernel-mcp
by fr4iser90
Related Servers
Alternatives to agent-kernel-mcp
No user-submitted related servers found.
Related Servers
- 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 gradedqualityBmaintenanceExposes ReadyAgents' local workflow engine and built-in tools over MCP stdio, enabling MCP clients to define, run, inspect, and approve YAML/JSON agent workflows.1,138 PyPIApache 2.0
- FlicenseAqualityDmaintenanceBridges Hermes Agent to the Hermes Intelligence Platform API, enabling tools to read/write learning loop data (context, feedback, signals, memory, etc.) via stdio.12-
- FlicenseNot gradedqualityCmaintenanceProvides safe repository operations, skill reading, command execution, and test detection for coding agents over stdio.-
- AlicenseBqualityAmaintenanceOperates a local Hermes Agent install from any MCP client over stdio, enabling task delegation, cron management, config changes, gateway restarts, health checks, and skill or session inspection without exposing the agent to the network.16MIT
TDQS
B3.4/5.0
Scored across 12 tools
Disambiguation4/5
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.
Naming Consistency3/5
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.
Tool Count5/5
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.
Completeness3/5
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues