github-copilot-cli-mcp-server
Wraps GitHub Copilot CLI as an MCP server, enabling MCP clients to run Copilot conversations for code tasks with support for session resumption and permission modes.
README
github-copilot-cli-mcp-server
⚠️ ALPHA VERSION — This project is experimental and in early development. Testing across different environments is limited. Use at your own risk and expect breaking changes.
A Node.js/TypeScript project that wraps GitHub Copilot CLI as a Model Context Protocol (MCP) server.
Use Copilot CLI as a tool from any MCP-compatible client (VSCode, OpenClaw, Claude Desktop, etc.).
Features
- Complete Copilot conversations in a single MCP call: Send a prompt → receive results in one tool call
- Session resumption: Continue previous conversations using session IDs
- Permission mode selection: Interactive (user confirmation) / Autonomous (auto-approve)
- Model selection: Use any model supported by Copilot
- Working directory specification: Set cwd for tasks that require file access
Prerequisites
- Node.js 20.0.0 or higher
- GitHub Copilot CLI installed and authenticated
npm install -g @github/copilot-cli - GitHub Copilot subscription (Individual, Business, or Enterprise)
Installation
From source
git clone https://github.com/slcwahn/github-copilot-cli-mcp-server.git
cd github-copilot-cli-mcp-server
npm install
npm run build
Quick start
npm run dev
MCP Tools
run_copilot_conversation
Runs a Copilot CLI conversation with a prompt.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
prompt |
string | ✅ | Prompt to send to Copilot |
model |
string | AI model (e.g., claude-sonnet-4, gpt-4.1) |
|
cwd |
string | Working directory | |
allow_tools |
string[] | List of tools to allow | |
add_dirs |
string[] | Additional directories to grant access | |
timeout_ms |
number | Timeout (default: 300000ms = 5 minutes) | |
permission_mode |
string | Permission mode: "autonomous" (default) or "interactive" |
Example:
{
"name": "run_copilot_conversation",
"arguments": {
"prompt": "Fix the bug in src/main.ts",
"cwd": "/path/to/project",
"model": "claude-sonnet-4"
}
}
resume_copilot_session
Resumes a previous session to continue the conversation.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
session_id |
string | ✅ | Session ID (UUID) |
prompt |
string | ✅ | Follow-up prompt |
model |
string | AI model | |
cwd |
string | Working directory | |
timeout_ms |
number | Timeout |
Example:
{
"name": "resume_copilot_session",
"arguments": {
"session_id": "abc12345-1234-5678-9abc-def012345678",
"prompt": "Now add tests for those changes"
}
}
list_copilot_sessions
Lists resumable Copilot CLI sessions.
respond_to_copilot
Responds to Copilot's permission prompts in Interactive mode.
Parameters:
| Name | Type | Required | Description |
|---|---|---|---|
session_id |
string | ✅ | Pending session ID |
response |
string | ✅ | Response ("yes", "no", or free text) |
Configuration
VSCode
Add the following to your .vscode/mcp.json file:
{
"servers": {
"github-copilot-cli": {
"type": "stdio",
"command": "node",
"args": ["/path/to/github-copilot-cli-mcp-server/dist/index.js"],
"env": {
"COPILOT_PERMISSION_MODE": "interactive"
}
}
}
}
Or use the Command Palette: MCP: Add Server → stdio → enter the configuration above.
Tip: Use
${workspaceFolder}to specify relative paths based on your workspace.
For global configuration, use the Command Palette: MCP: Open User Configuration to add it to your user profile.
OpenClaw (mcporter)
OpenClaw supports MCP servers through the mcporter skill.
Register via mcporter CLI
# Register the server
mcporter config add github-copilot-cli \
--command node \
--arg /path/to/github-copilot-cli-mcp-server/dist/index.js \
--env COPILOT_PERMISSION_MODE=autonomous
# Verify registration
mcporter list
# Check tool schema
mcporter list github-copilot-cli --schema
# Call a tool directly
mcporter call github-copilot-cli.run_copilot_conversation prompt="Fix the bug in main.ts"
Edit mcporter config file directly
~/.mcporter/mcporter.json or project-level config/mcporter.json:
{
"servers": {
"github-copilot-cli": {
"transport": "stdio",
"command": "node",
"args": ["/path/to/github-copilot-cli-mcp-server/dist/index.js"],
"env": {
"COPILOT_PERMISSION_MODE": "autonomous"
}
}
}
}
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"github-copilot-cli": {
"command": "node",
"args": ["/path/to/github-copilot-cli-mcp-server/dist/index.js"]
}
}
}
Environment Variables
| Variable | Default | Description |
|---|---|---|
COPILOT_CLI_PATH |
(auto-detect) | Path to Copilot CLI binary |
COPILOT_PERMISSION_MODE |
autonomous |
Permission mode: autonomous or interactive |
Permission Handling
Copilot CLI may request user approval for file modifications, shell command execution, and other actions. This MCP server supports two permission modes:
Autonomous Mode (default)
COPILOT_PERMISSION_MODE=autonomous
- Runs Copilot CLI with
--allow-all-tools --no-ask-userflags - Auto-approves all permissions and completes without user prompts
- Best for: Trusted tasks, automation pipelines, CI/CD
Interactive Mode
COPILOT_PERMISSION_MODE=interactive
- Runs Copilot CLI with PTY for interactive I/O
- Returns
needsInput: truein the MCP response when a permission prompt is detected - The MCP client (user or agent) responds via the
respond_to_copilottool
Interactive Mode Flow:
MCP Client MCP Server Copilot CLI
│ │ │
│ run_copilot_conversation │ │
├─────────────────────────────►│ spawn (PTY) │
│ ├───────────────────────────►│
│ │ │
│ │ "Modify this file?" │
│ │◄───────────────────────────┤
│ { needsInput: true, │ │
│ question: "Modify..." } │ │
│◄─────────────────────────────┤ │
│ │ │
│ respond_to_copilot("yes") │ │
├─────────────────────────────►│ write "yes\n" │
│ ├───────────────────────────►│
│ │ │
│ │ (complete) │
│ │◄───────────────────────────┤
│ { output: "..." } │ │
│◄─────────────────────────────┤ │
Note: Interactive mode requires
node-pty(optional dependency). If not installed, it automatically falls back to autonomous mode.
Architecture
MCP Client (VSCode / OpenClaw / Claude Desktop)
│
│ stdio (JSON-RPC)
▼
┌──────────────────────────────────────────────┐
│ github-copilot-cli-mcp-server │
│ │
│ ┌────────────────────────────────────────┐ │
│ │ MCP Server (stdio) │ │
│ │ - run_copilot_conversation │ │
│ │ - resume_copilot_session │ │
│ │ - list_copilot_sessions │ │
│ │ - respond_to_copilot │ │
│ └──────────────┬─────────────────────────┘ │
│ │ │
│ ┌──────────────▼─────────────────────────┐ │
│ │ Permission Handler │ │
│ │ (autonomous / interactive) │ │
│ └──────────────┬─────────────────────────┘ │
│ │ │
│ ┌──────────────▼─────────────────────────┐ │
│ │ Copilot Runner │ │
│ │ (spawn / PTY) │ │
│ └──────────────┬─────────────────────────┘ │
│ │ │
│ ┌──────────────▼─────────────────────────┐ │
│ │ Session Manager │ │
│ │ (session metadata + pending input) │ │
│ └────────────────────────────────────────┘ │
└──────────────────────────────────────────────┘
│
│ spawn / PTY
▼
copilot -p "prompt" -s [--allow-all-tools | interactive]
Development
# Development mode
npm run dev
# Build
npm run build
# Type check
npm run typecheck
# Test
npm test
How It Works
- The MCP client calls the
run_copilot_conversationtool - Depending on the permission mode:
- Autonomous: Runs
copilot -p "<prompt>" -s --allow-all-tools --no-ask-user - Interactive: Runs with PTY, forwarding permission prompts to the MCP client
- Autonomous: Runs
- Copilot CLI performs the task (code generation, modification, analysis, etc.)
- Returns the output as an MCP response upon completion
- If a session ID is available, the session can be resumed via
resume_copilot_session
Copilot CLI Options Used
| Flag | Purpose |
|---|---|
-p <prompt> |
Run prompt in non-interactive mode |
-s |
Silent mode (response only, no stats) |
--allow-all-tools |
Auto-approve all tools (autonomous mode) |
--no-ask-user |
Autonomous operation without prompts (autonomous mode) |
--no-custom-instructions |
Ignore AGENTS.md and similar files |
--no-color |
Disable ANSI colors |
--no-alt-screen |
Disable terminal alternate screen |
--resume <id> |
Resume a session |
--model <model> |
Select a model |
--add-dir <dir> |
Grant access to additional directories |
License
MIT
References
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。