A
licenseNot graded
qualityB
maintenanceRemote-first, model-independent Windows execution MCP for ChatGPT, Claude, Gemini, and other MCP-compatible AI clients.
MIT
Agent Gateway MCP
by Kvxw1105
Related Servers
Alternatives to Agent Gateway MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceA Windows-first, dual-mode MCP bridge that delegates bounded work to Hermes Agent and a local Qwen model via an OpenAI-compatible endpoint, providing restricted batch or trusted full execution modes.9MIT
- FlicenseNot gradedqualityCmaintenanceSecure localhost MCP gateway that exposes project-scoped file/Git/search tools and controlled CLI agent adapters (Codex, Claude) with fixed argv for safe Windows-native agent work.-
- AlicenseNot gradedqualityDmaintenanceA general-purpose MCP gateway that exposes your local CLI skills to any AI assistant.16 npm1MIT
- AlicenseNot gradedqualityBmaintenanceProvides a Windows-first local AI-agent gateway with configurable tools for files, Git, processes, Windows automation, WSL, browser control, durable agent runs, memory, verification, and intelligent routing, while exposing a secure MCP endpoint for ChatGPT Web and a local web UI.17 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI clients to connect to a Windows machine for file operations, PowerShell execution, Git inspection, task management, memory, and skills.-
TDQS
A4/5.0
Scored across 11 tools
Disambiguation5/5
Each tool has a clear, distinct purpose. The generic agents_* tools manage asynchronous tasks, while kimi_* tools are specific to Kimi Code sessions; even similar operations like agents_resume and kimi_resume are differentiated by target system and description.
Naming Consistency5/5
All tools follow a consistent snake_case pattern with clear domain prefixes: agents_* for generic agent management and kimi_* for Kimi-specific operations. The pattern is predictable and uniform.
Tool Count5/5
With 11 tools, the server is well-scoped for its purpose of managing local CLI agents and Kimi sessions. The count falls within the ideal range and each tool serves a distinct function.
Completeness4/5
The generic agent lifecycle (spawn, resume, status, wait, logs, cancel) is complete, and Kimi-specific tools cover status, run, resume, and listing. Minor gaps exist, such as no explicit kimi_cancel, but the generic cancel may cover it, so core workflows are supported.
Maintenance
ActivitySlowing
ResponsivenessNo issues