Skip to content

feat(work-iq): add Microsoft Work IQ MCP as an authoring-time developer tool - #232

Open
harsheetjain wants to merge 1 commit into
microsoft:mainfrom
harsheetjain:harsheetjain/work-iq-mcp
Open

feat(work-iq): add Microsoft Work IQ MCP as an authoring-time developer tool#232
harsheetjain wants to merge 1 commit into
microsoft:mainfrom
harsheetjain:harsheetjain/work-iq-mcp

Conversation

@harsheetjain

Copy link
Copy Markdown
Contributor

Summary

Adds Microsoft Work IQ (@microsoft/workiq) as an authoring-time developer MCP server, configured alongside the existing Dataverse MCP server. Work IQ lets the maker's Copilot resolve a person to their Entra (AAD) object id from a username/UPN while authoring.

What's included

  • .vscode/mcp.json (/setup) — a static, no-credential workiq stdio entry (
    px -y @microsoft/workiq@latest mcp) is now written next to Dataverse during onboarding (src/skills/onboarding/step1.md).
  • src/reference/work-iq-mcp.md (new) — config snippet, the AAD-id-from-username recipe (fetch /users/{upn}results[0].data.id; fetch /me/people?\={name} for fuzzy lookup), consent/EULA notes, and boundaries.
  • .github/copilot-instructions.md — new Developer Tools (authoring-time) section describing Work IQ and its primary use (resolve a person to their Entra/AAD object id).
  • README.md — Work IQ MCP developer-tool section + Node.js noted as an optional prerequisite (only for npx).

Boundaries

Work IQ is authoring-time only — it runs on the maker's machine under the maker's own Entra sign-in, is never a connection reference / extension pack / flow, and is never deployed to Copilot Studio. For the signed-in employee's identity at runtime, the ESS agent uses user-context topics / System.User.*, not Work IQ.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

…er tool

Wire the off-the-shelf @microsoft/workiq MCP server into the kit so any maker
can resolve people to their Entra (AAD) object id from their own account while
authoring (fetch /users/{upn} -> results[0].data.id). It ships to every user via
/setup - the workiq entry is fully static (no tenant values/secrets), so it lands
in each maker's generated .vscode/mcp.json rather than being committed (that file
holds tenant URLs and stays machine-local).

- onboarding/step1.md: /setup now writes the workiq server alongside Dataverse
- src/reference/work-iq-mcp.md: config, AAD-id recipe, 10-tool overview,
  consent/EULA notes, and the guardrail that Work IQ is authoring-time only -
  never an ESS-agent connection reference/extension pack/flow, never deployed
- copilot-instructions.md: new "Developer Tools (authoring-time)" section, kept
  separate from Connector Guidance so it is not mistaken for an agent integration
- README: Work IQ MCP subsection + optional Node.js prerequisite

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 16ef8282-5b14-4d3f-b590-743013e0e692
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant