copilot-agents-mcp
Related Servers
Alternatives to copilot-agents-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables coding agents and IDEs to request multi-model code review, architectural planning, and technical consultation over stdio, returning actionable diffs and SARIF diagnostics.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables an AI assistant to delegate coding tasks to local Codex or Claude Code CLIs, monitor their progress, read results, continue sessions, and browse the files in user-approved project workspaces. It exposes these capabilities over Streamable HTTP through a Cloudflare tunnel or locally over stdio, so a remote or cloud client can drive agents running on the user's own machine.60 npm1MIT
- AlicenseCqualityDmaintenanceConnects MCP-enabled editors to GitHub Copilot CLI for non-interactive code analysis, batch processing, and code review.1028 npm5MIT
- AlicenseNot gradedqualityFmaintenanceEnables a primary coding agent to delegate bounded implementation and repair tasks to a local OpenAI-compatible model that edits a copy of the project, runs configured checks, and returns artifacts for review. Exposes stdio tools for capability discovery, task submission, progress polling, artifact reading, and cancellation.MIT
- AlicenseAqualityBmaintenanceEnables an AI agent to perform real GitHub operations such as creating repositories, opening and closing issues, commenting, listing commits, and committing file changes through natural language via the Model Context Protocol over stdio.8MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding tools to check AI engine fleet health and status, run prompts with automatic model and engine failover, and inspect sessions through MCP tools. It runs locally over stdio with no cloud telemetry.MIT
TDQS
Scored across 3 tools
The three tools target clearly distinct actions: launching a task, reading task status, and listing available models. The only blur is that create_agent_task embeds a model-listing fallback behavior, which slightly overlaps with list_copilot_models, but an agent can still tell them apart.
All three names follow a snake_case verb_noun pattern (create_agent_task, get_agent_task, list_copilot_models), which is predictable. The minor deviation is that the noun changes between agent_task and copilot_models, and 'copilot' is redundantly embedded in one name.
Three tools is quite thin for a task-lifecycle server; launching and reading a task without any other lifecycle operations leaves little room for real workflows. The count is defensible for a narrow wrapper, but it sits at the borderline of feeling under-scoped.
The surface covers launch, single status read, and model listing, but there is no way to cancel/stop a task, list existing tasks, wait or poll for completion, or retrieve logs/artifacts. These gaps will likely force agents into dead ends during real task management.