MCP server does not register fetch_blob/upload_blob tools despite experimental=true
Open
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1k
- Forks
- 132
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 6
Description
Summary
The WorkIQ MCP server (v0.5.0-preview3, build 0.5.0.26793) does not expose fetch_blob or upload_blob as MCP tools, even though:
- The CLI binary supports both commands (
workiq fetch-blob --helpworks) experimental=trueis set in config- The plugin README and SKILL.md document them as part of the "11 MCP tools" surface
- The skill references (
fetch-blob-work-iq.md,upload-blob-work-iq.md) describe them as MCP tools
Repro
- Install workiq-preview plugin (
/plugin install workiq-preview@work-iq) - Ensure
workiq config set experimental=true - Start MCP server and send
tools/list— only 12 tools are returned:- accept_eula, ask, list_agents, delete_entity, get_debug_link, do_action, create_entity, get_schema, search_paths, call_function, fetch, update_entity
fetch_blobandupload_blobare missing
Expected
tools/list should include fetch_blob and upload_blob when experimental=true.
Workaround
Use the CLI commands directly:
npx -y @microsoft/workiq@preview fetch-blob --url "/me/drive/items/{id}/content" --output ./downloads
npx -y @microsoft/workiq@preview upload-blob --help
Environment
- OS: Windows 11 (win_x64)
- WorkIQ version: 0.5.0.26793 (@microsoft/workiq@0.5.0-preview3)
- Node: v24.13.1
- Copilot CLI
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 by reproducing the MCP tools/list response after setting experimental=true, then compare the registered tools with the plugin README, SKILL.md, and the fetch-blob-work-iq.md and upload-blob-work-iq.md references. Done means fetch_blob and upload_blob appear in tools/list under the stated configuration while the existing CLI commands remain available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, powershell
- Domain
- api, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100