// Explain what Fusion MCP is and guide users through setting it up when they need Fusion-aware MCP capabilities in Copilot workflows.
Guides consumption and understanding of Fusion backend services, APIs, and patterns for frontend/client developers, integrators, and architects. Shows reference implementations, explains architectural decisions, and clarifies contracts. USE FOR: understanding Fusion backend APIs, learning implementation patterns, exploring reference code, choosing the right integration point, and understanding authorization/validation/async patterns. DO NOT USE FOR: modifying backend services, creating new endpoints, database changes, or backend-specific development (use fusion-services-develop or backend service repo instead).
Use Fusion DevTools CLI (fdev) for API testing, token acquisition, service discovery, and person lookup during development. USE FOR: calling Fusion REST APIs, getting access tokens as JSON, discovering services and environments, resolving persons, PIM role activation. DO NOT USE FOR: modifying backend service code, deploying services, infrastructure changes, CI/CD pipeline configuration, or Service Bus operations.
Guides integrations across Fusion Core service APIs from a single installable skill. USE FOR: service discovery across apps, people, context, roles, notifications, reports, tasks, and other Fusion Core APIs; cross-service integration planning; choosing the right endpoint/model guidance for a workflow. DO NOT USE FOR: modifying Fusion backend source code, non-Fusion APIs, or generic cloud architecture work without a Fusion service integration target.
Review dependency PRs with structured research, existing-PR-discussion capture, multi-lens analysis (security, code quality, impact), and a repeatable verdict template. USE FOR: dependency update PRs, Renovate/Dependabot PRs, library upgrade reviews, "review this dependency PR", "should we merge this update". DO NOT USE FOR: feature PRs, application code reviews, dependency automation/bot configuration, or unattended merge without confirmation.
Resolves unresolved GitHub PR review threads end-to-end: evaluates whether each review comment is correct, applies a targeted fix when valid, replies with rationale when not, commits, and resolves the thread. USE FOR: unresolved review threads, PR review feedback, changes requested PRs, PR review URLs (#pullrequestreview-...), fix the review comments, close the open threads, address PR feedback. DO NOT USE FOR: summarizing feedback without code changes, creating new PRs, or read-only branches.
Handles GitHub issue resolution end-to-end for prompts like "solve #123", "lets solve #123", "work on #123", "work on https://github.com/owner/repo/issues/123", or by pasting a direct GitHub issue URL as the request. USE FOR: solve #123, continue work on issue #123, work on https://github.com/owner/repo/issues/123, paste a GitHub issue URL for implementation work. DO NOT USE FOR: issue drafting only, PR review only, or non-implementation research.
| name | fusion-mcp |
| description | Explain what Fusion MCP is and guide users through setting it up when they need Fusion-aware MCP capabilities in Copilot workflows. |
| license | MIT |
| metadata | {"version":"1.0.1","status":"experimental","owner":"@equinor/fusion-core","tags":["fusion","mcp","setup"],"mcp":{"suggested":["github"]}} |
Use when a user asks:
Typical triggers:
fusion-research for thatCollect before proposing setup steps:
If details are missing, ask concise follow-up questions first.
search, search_framework, search_docs, search_eds, search_indexes, search_backend_codereferences/vscode-mcp-config.md)"type": "http" and server URL (see references/vscode-mcp-config.md)initialize and confirm successful responsetools/list and confirm at least one tool returnedtools/call against an available toolcontent or structuredContent contains data)oauth.clientId in config and that VS Code is signed in with an Equinor account401 Unauthorized → re-authenticate via VS Code account settings; ensure Equinor Entra account is activetools/list returns empty or tool call fails → verify MCP server entry is selected/enabled in VS Code and retry after reloadingassets/bug-report-template.md.
equinor/fusion-mcpReturn:
initialize (expect success response), run tools/list (expect at least one tool), run one tools/call (expect non-empty content or structuredContent)assets/bug-report-template.md with default target equinor/fusion-mcpNever:
Always: