microsoft / microsoft/work-iq

MCP server returns error -32601 (Method not found) when Claude Code tries to fetch tools

Open
#38 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PowerShell
Stars
1k
Forks
132
Avg merge
5d 19h
Merged PRs (30d)
6

Description

Bug Report

Version: @microsoft/workiq 0.2.8.13483 (latest)
Environment: Windows 11, Claude Code VS Code extension
MCP Configuration: Configured in ~/.claude/mcp.json

Issue

The WorkIQ MCP server fails to connect to Claude Code with the following error:

{
  "error": "Failed to fetch tools: MCP error -32601: Method not found",
  "timestamp": "2026-02-06T23:01:11.839Z",
  "sessionId": "1162f4a9-753f-4f09-978e-14fdbc748b96",
  "cwd": "C:\\Users\\nandab"
}
Configuration
~/.claude/mcp.json:


{
  "servers": {
    "workiq": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@microsoft/workiq", "mcp"],
      "tools": ["**"]
    }
  }
}
Expected Behavior
WorkIQ MCP server should start successfully
Should respond to MCP protocol methods (e.g., tools/list)
Claude Code should be able to discover and use WorkIQ tools
Actual Behavior
MCP server starts but fails during tool discovery handshake
Returns JSON-RPC error -32601 (Method not found)
No WorkIQ tools are available in Claude Code
Additional Context
WorkIQ CLI works perfectly: npx -y @microsoft/workiq ask -q "test"
WorkIQ is authenticated and can query M365 data successfully via CLI
Other MCP servers (e.g., Kusto) work correctly in the same Claude Code environment
Error suggests the MCP server isn't implementing required protocol methods
Workaround
Currently using WorkIQ CLI directly via Node.js child_process instead of MCP server.

Request
Please investigate the MCP protocol implementation and ensure it correctly implements the required MCP methods for tool discovery.


``

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the npx -y @microsoft/workiq mcp entry point and reproduce the handshake using ~/.claude/mcp.json in Claude Code. Check the server's response to tools/list and related MCP protocol methods; done means Claude Code discovers and can use the WorkIQ tools without the -32601 error.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.