topmcps
Browse MCPs
Microsoft Work IQ

Microsoft Work IQ

Official

Ask natural-language questions across Microsoft 365 Copilot data.

Score 79(?)MicrosoftProprietary975Verified Top MCPs for Scheduling & Calendar →
InstallView on GitHub

Quick answer

What it does

Runs an `ask` tool for natural-language questions over Microsoft 365 Copilot data, plus entity tools — fetch, create, update, delete, do-action, get-schema, search-paths and call-function — that proxy to the remote Work IQ MCP service.

Best for

  • Natural-language search across an M365 tenant
  • Finding the thread or document behind a decision
  • Cross-surface questions spanning mail, Teams and files
  • Teams already licensed for M365 Copilot

Not for

  • Tenants without a Microsoft 365 Copilot licence
  • Simple calendar or mailbox CRUD

Source: top-mcps.com/mcp/microsoft-work-iq — verified Aug 2026

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
  "mcpServers": {
    "microsoft-work-iq": {
      "command": "npx",
      "args": [
        "-y",
        "@microsoft/workiq"
      ]
    }
  }
}

    Paste under mcpServers. Fully quit and reopen Claude after editing.

    CLI or .mcp.json
    claude mcp add microsoft-work-iq -- npx -y @microsoft/workiq

    Run from your repo. Commit .mcp.json to share with your team.

    .cursor/mcp.json
    {
  "mcpServers": {
    "microsoft-work-iq": {
      "command": "npx",
      "args": [
        "-y",
        "@microsoft/workiq"
      ]
    }
  }
}

    Global path: ~/.cursor/mcp.json. Reload window after editing.

    .vscode/mcp.json
    {
  "servers": {
    "microsoft-work-iq": {
      "command": "npx",
      "args": [
        "-y",
        "@microsoft/workiq"
      ]
    }
  }
}

    VS Code uses the "servers" key (not "mcpServers").

    ~/.codeium/windsurf/mcp_config.json
    {
  "mcpServers": {
    "microsoft-work-iq": {
      "command": "npx",
      "args": [
        "-y",
        "@microsoft/workiq"
      ]
    }
  }
}

    Open via Cascade → hammer icon → Configure.

    cline_mcp_settings.json
    {
  "mcpServers": {
    "microsoft-work-iq": {
      "command": "npx",
      "args": [
        "-y",
        "@microsoft/workiq"
      ]
    }
  }
}

    Open via the Cline sidebar → MCP Servers → Edit.

    ~/.continue/config.json
    {
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "@microsoft/workiq"
          ]
        }
      }
    ]
  }
}

    Continue uses modelContextProtocolServers with a transport block.

    ~/.codex/config.toml
    # ~/.codex/config.toml
[mcp_servers.microsoft-work-iq]
command = "npx"
args = [
  "-y",
  "@microsoft/workiq",
]

    Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

    ~/.config/zed/settings.json
    {
  "context_servers": {
    "microsoft-work-iq": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@microsoft/workiq"
        ]
      }
    }
  }
}

    Zed calls them "context_servers". Settings live-reload on save.

    ChatGPT → Apps directory

    Microsoft Work IQ doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

  2. 2

    Set required secrets

    No credentials required — this MCP runs over stdio without authentication.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. scheduling & calendar work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-scheduling-calendar
Compare Microsoft Work IQ against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare Microsoft Work IQ MCP vs [Microsoft 365 MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/microsoft-work-iq
- top-mcps.com listing for Microsoft 365
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the Microsoft Work IQ MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/microsoft-work-iq (fetch https://top-mcps.com/mcp/microsoft-work-iq.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (no secrets) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 1 update tracked.

  1. Refreshed install snippets and fact sheet; verified for 2026.

More Scheduling & Calendar MCPs

Other tools in the same category worth evaluating.

Google Calendar31

Read, create, and manage events across Google Calendar — via Google's official remote MCP or a self-hosted community server.

google-calendar, scheduling, events, productivity
10 minMedium
Calendly

Official hosted MCP for booking-link scheduling — share availability without exposing the raw calendar.

calendar, scheduling, calendly, booking
5 minLow
Apple Calendar (CalDAV)

Read and create events in Apple Calendar via CalDAV from any MCP client.

calendar, apple, caldav, icloud
10 minMedium

Compared with Microsoft Work IQ

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Microsoft Work IQvsMicrosoft 365Microsoft Work IQvsGmailMicrosoft Work IQvsGoogle CalendarMicrosoft Work IQvsCal.com

Exploring Top MCPs for Scheduling & Calendar? See all Scheduling & Calendar MCPs →