Failing to connect to MCP server 'workiq' MCP error -32000: Connection closed
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1k
- Forks
- 132
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 6
Description
When using the Copilot CLI it will not connect to the workiq MCP server and continues to fail. The plugin is installed but the connection with the MCP server is failing. Trying to use Copilot to fix the issue never succeeds. I am running in a DevBox.
Here is the contents of the ~/.copilot/installed-plugins/copilot-plugins/workiq/.mcp.json file:
{
"mcpServers": {
"workiq": {
"command": "npx",
"args": [
"-y",
"@microsoft/workiq",
"mcp"
],
"tools": [
"*"
]
}
}
}
The /mcp command for the workiq shows:
MCP Server: workiq
Type: local
Command: npx
Status: ✗ Failed
Error: MCP error -32000: Connection closed
Tools: Server failed to connect
/plugin list shows the following:
● Installed Plugins:
• workiq@copilot-plugins v1.0.0
I am running GitHub Copilot v0.0.417
PowerShell 7 is being used
npm version: 10.8.2
node version: v20.17.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with ~/.copilot/installed-plugins/copilot-plugins/workiq/.mcp.json and reproduce the failure using the /mcp command in Copilot CLI. Check the listed PowerShell, npm, Node.js, and Copilot versions while investigating why the local workiq server closes its connection. Done means /mcp reports workiq as connected and its tools are available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, powershell
- Domain
- backend, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100