Claude Code
Connect workiq-proxy to Claude Code so Claude can search your M365 emails, docs, chats, and meetings while you work.
One-line setup
Section titled “One-line setup”The fastest path. Pick project-level to share the config with your team via git, or user-level to enable it everywhere on your machine.
Project-level (shared via git)
Section titled “Project-level (shared via git)”claude mcp add --transport stdio workiq --scope project -- npx -y @stuffbucket/workiq-proxyThis writes to .mcp.json in your current directory.
User-level (all projects)
Section titled “User-level (all projects)”claude mcp add --transport stdio workiq --scope user -- npx -y @stuffbucket/workiq-proxyShortcut:
workiq-proxy install claudedoes the same thing — it detects Claude Code and registers the server for you.
Manual configuration
Section titled “Manual configuration”If you prefer to edit the config file directly, add to .mcp.json:
{ "mcpServers": { "workiq": { "type": "stdio", "command": "npx", "args": ["-y", "@stuffbucket/workiq-proxy"] } }}With a globally installed Work IQ CLI
Section titled “With a globally installed Work IQ CLI”If you’ve installed @microsoft/workiq globally and want to skip the npx download on each launch:
{ "mcpServers": { "workiq": { "type": "stdio", "command": "npx", "args": ["-y", "@stuffbucket/workiq-proxy", "--workiq-cmd", "workiq"] } }}Verify
Section titled “Verify”Run /mcp inside Claude Code. You should see workiq listed as a connected server with 9 tools:
accept_eulaask_work_iqsearch_emailssearch_documentssearch_chatssearch_channelssearch_meetingssearch_peoplesearch_external
Try asking Claude: “Search my emails from last week about the budget review” — it will call the right tool automatically.