MCP server is accessing repo but not the Copilot spaces #178956
Replies: 3 comments
-
|
Hi 👋 Here’s what’s happening and what you can do: 🧠 1️⃣ Why it happens GitHub Copilot and Claude 4.5 Sonnet use different API ecosystems. When Claude says “the tool is not added to its toolset yet,” it simply means that its runtime environment can’t invoke MCP-compatible tools — it’s not an error in your VS Code setup. 🧩 2️⃣ How to verify your MCP connection In VS Code: Open the Output panel → select GitHub Copilot in the dropdown. Look for a log line like: MCP: Connected to server at port 63342 That confirms the MCP server is working on the Copilot side. If you don’t see it, restart VS Code or update the GitHub Copilot Nightly or Chat extensions to the latest version — support for MCP is still being rolled out gradually. 🚀 3️⃣ What you can do next Keep your Copilot Chat and VS Code Insiders versions up to date — new MCP endpoints and model integrations are being added frequently. If you’re testing Claude in the same workspace, it won’t yet share the same tool context as Copilot until Anthropic adds MCP compatibility. You can follow GitHub’s Copilot changelog So in short: your setup is fine — the message just means Claude doesn’t yet support that MCP toolset, but Copilot itself is working correctly. (If this clears things up, please mark this as the accepted answer so others understand the situation too!) |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Thanks for the clarification @Aqib121201 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Copilot Feature Area
General
Body
The MCP server is called in VSCode but my Copilot space is not being accessed, Claude 4.5 Sonnet is saying, "It's very new so the tool is not added to its toolset yet"
Beta Was this translation helpful? Give feedback.
All reactions