Skip to main content
Glama
github-copilot-cli-mcp-server

github-copilot-cli-mcp-server

by slcwahn

Related Servers

Alternatives to github-copilot-cli-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      MCP server for GitHub Copilot that allows querying any Copilot model programmatically using existing Copilot CLI credentials, with support for file attachments and model discovery.
      2
      26 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Code to delegate tasks to persistent GitHub Copilot CLI sessions via MCP, inspect pending tool requests, and approve each operation once or deny it while continuing multi-turn context. It bridges ACP runtime sessions locally over stdio without a public service or background daemon.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Wraps the local Qoder CLI into an MCP server, enabling any MCP client to delegate coding tasks to a local Qoder agent with session management, sandboxed permissions, and model selection.
      3
      65 npm
      MIT

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: run starts a new one-shot conversation, list shows available sessions, resume continues an existing session by ID, and respond answers permission prompts. No two tools overlap in purpose, and the descriptions reinforce the boundaries.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: resume_copilot_session, run_copilot_conversation, list_copilot_sessions, respond_to_copilot. The pattern makes the action and target of each tool immediately predictable.

    Tool Count5/5

    Four tools is well-scoped for a thin MCP server wrapping GitHub Copilot CLI. Each tool covers a necessary part of the session workflow—start, list, resume, and respond—without redundant or filler tools.

    Completeness4/5

    The core session lifecycle is covered: starting, listing, resuming, and handling permission input. Minor gaps exist, such as no explicit way to terminate a session or fetch full session transcripts, but these are not critical for the server's apparent purpose.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data