microsoft / microsoft/work-iq

ask_work_iq doesn't work in MCP version 0.4.0

Open
#64 6 comments 4 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

ask_work_iq tool always returns error in MCP version 0.4.0

{"response":null,"conversationId":null,"error":"An error occurred while processing your request."}

Oddly, it works fine when using the CLI.

However, on older version 0.2.8 it works fine i.e. both CLI and MCP work fine there but for 0.4.0 only CLI works and MCP tool doesn't.

Logs

2026-03-12 12:37:45.341 [warning] Failed to parse message: "dbug: Microsoft.WorkIQ.Auth.InteractiveAuthProvider[0]\r\n"
2026-03-12 12:37:45.341 [warning] Failed to parse message: " Starting authentication flow\r\n"
2026-03-12 12:37:45.342 [warning] Failed to parse message: "dbug: Microsoft.WorkIQ.Auth.InteractiveAuthProvider[0]\r\n"
2026-03-12 12:37:45.342 [warning] Failed to parse message: " Scopes requested: https://graph.microsoft.com/.default\r\n"
2026-03-12 12:37:45.342 [warning] Failed to parse message: "dbug: Microsoft.WorkIQ.Auth.InteractiveAuthProvider[0]\r\n"
2026-03-12 12:37:45.342 [warning] Failed to parse message: " Account identifier provided: True\r\n"
2026-03-12 12:37:45.343 [warning] Failed to parse message: "dbug: Microsoft.WorkIQ.Auth.AccountManager[0]\r\n"
2026-03-12 12:37:45.343 [warning] Failed to parse message: " Retrieving accounts from cache\r\n"
2026-03-12 12:37:45.344 [warning] Failed to parse message: "dbug: Microsoft.WorkIQ.Auth.AccountManager[0]\r\n"
2026-03-12 12:37:45.344 [warning] Failed to parse message: " Found 1 cached account(s)\r\n"
2026-03-12 12:37:45.344 [warning] Failed to parse message: "dbug: Microsoft.WorkIQ.Auth.AccountManager[0]\r\n"
2026-03-12 12:37:45.345 [warning] Failed to parse message: " Looking for specific account in cache\r\n"
2026-03-12 12:37:45.345 [warning] Failed to parse message: "dbug: Microsoft.WorkIQ.Auth.AccountManager[0]\r\n"
2026-03-12 12:37:45.345 [warning] Failed to parse message: " Found matching account in cache\r\n"
2026-03-12 12:37:45.345 [warning] Failed to parse message: "dbug: Microsoft.WorkIQ.Auth.InteractiveAuthProvider[0]\r\n"
2026-03-12 12:37:45.346 [warning] Failed to parse message: " Attempting silent token acquisition with determined account\r\n"
2026-03-12 12:37:45.390 [warning] Failed to parse message: "dbug: Microsoft.WorkIQ.Auth.InteractiveAuthProvider[0]\r\n"
2026-03-12 12:37:45.391 [warning] Failed to parse message: " Silent authentication failed with MsalUiRequiredException: Could not find a WAM account for the selected user. Error: Status: AccountNotFound\r\n"
2026-03-12 12:37:45.391 [warning] Failed to parse message: " Context: Account with id '(pii)' not found\r\n"
2026-03-12 12:37:45.392 [warning] Failed to parse message: " Tag: 0x1f553780\r\n"
2026-03-12 12:37:45.392 [warning] Failed to parse message: "dbug: Microsoft.WorkIQ.Auth.InteractiveAuthProvider[0]\r\n"
2026-03-12 12:37:45.392 [warning] Failed to parse message: " Launching interactive authentication flow\r\n"


note: interactive auth never launches here, and ideally silent should've worked in the first place

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 by reproducing ask_work_iq through the MCP interface on version 0.4.0, then compare it with the CLI and version 0.2.8. Trace the authentication flow around the logged silent-token failure and missing interactive launch. Done means MCP requests authenticate and return a response without the parsing errors shown in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
api, authentication
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.