[Bug] GitHub MCP tools not fully activated in Copilot SDK with --enable-all-github-mcp-tools

[jimmy-grande]

Problem

When initializing the SDK and activating all GitHub MCP tools using the following configuration:

const client = new CopilotClient({
      useStdio: true,
      logLevel: "all",
      autoStart: true,
      cliArgs: [
        "--enable-all-github-mcp-tools",
      ],
    });

and sending:

await session.send({
  prompt: "I have activated all github mcp tools. List Copilot Spaces",
});

the LLM responds:

I don't have access to Copilot Spaces through the gh CLI. The MCP tools you mentioned are not available in my current toolset - I only have access to file system tools, bash, grep, and web fetch.

To list Copilot Spaces, you would need to either:

1. Use the GitHub MCP server with a client that supports it (like VS Code with the GitHub Copilot extension)
2. Use the GitHub API directly if you have the appropriate endpoint and token

Could you clarify which MCP tools you've activated and how you'd like me to access them?

FYI:
If I run copilot --enable-all-github-mcp-tools in another shell and ask the same question, it works as expected.

Expected behavior

Activating all GitHub MCP tools in the SDK client (as above) should enable access to Copilot Spaces and all other MCP tools, consistent with the behavior observed when running copilot --enable-all-github-mcp-tools in a shell.

Actual behavior

The only available tools are file system tools, bash, grep, and web fetch. Access to Copilot Spaces and other MCP tools is missing.

Steps to Reproduce

1. Initialize the CopilotClient as above with --enable-all-github-mcp-tools.
2. Send a prompt intended to access Copilot Spaces.
3. Observe LLM's response; Copilot Spaces tools are missing.

Additional Context

• The same setup works when using the CLI in a separate shell.
• SDK Version: 0.1.15
• Copilot CLI Version: 0.0.392
• Platform/OS: macOS 26.2

Is there a difference in how tool activation works between the SDK and the standalone CLI? How can I achieve MCP tool parity in the SDK?

[github-actions]

Thank you for opening this issue, @jimmy-grande!

I've labeled this as a bug for the sdk/nodejs implementation. The issue is well-documented with clear reproduction steps, versions, and expected behavior.

The discrepancy between the CLI flag behavior (copilot --enable-all-github-mcp-tools) working standalone but not when passed via the SDK's cliArgs suggests a potential issue with how the Node.js SDK forwards CLI arguments or initializes the underlying Copilot CLI process.

The team will investigate why the GitHub MCP tools aren't being activated when using the SDK wrapper.

AI generated by Issue Triage Agent

[PeterMerkert]

I can confirm experiencing the exact same behavior described in this issue.

Environment

• SDK Version: 0.1.16
• Copilot CLI Version: 0.0.392
• Platform/OS: Windows 11 Pro (Build 26200)
• Node.js: v25.2.1

[mohan00319]

your code is correct.
If --enable-all-github-mcp-tools is enabled, Copilot Spaces can't be listed via github MCP tools.
when you send that prompt.
await session.send({
prompt: "I have activated all github mcp tools. List Copilot Spaces",
});

[ctaceygreen]

I've also run into this same issue with the dotnet SDK.

Copilot CLI is happily using Github MCP tools, but the Copilot SDK doesn't see them. I've tried the same as above, passing --enable-all-github-mcp-tools in the CliArgs when creating the CopilotClient, but no change.

Environment

• SDK Version: 0.1.20
• Copilot CLI Version 0.0.400
• Platform/OS: Attempted on both MacOS and Windows 11

[shwetalodha]

Check my video about how you can consume MCP server using GitHub CoPilot SDK. You may get pointers:
https://youtu.be/sW9oUTFGlvA?si=XUuExKuwIFTx4N-P