About

Imported from equinor/fusion-skills (skills/.experimental/fusion-mcp/SKILL.md) via skills.sh. Install upstream with npx skills add equinor/fusion-skills --skill fusion-mcp. Copyright stays with the author (MIT).

Fusion MCP Setup Guide

Name: fusion-mcp
Author: equinor

When to use

Use when a user asks:

what Fusion MCP is
what it can do
how to install/configure it
how to verify it is working
how to troubleshoot a failing Fusion MCP setup

Typical triggers:

"what is fusion mcp"
"help me set up fusion mcp"
"how do I use fusion mcp with copilot"

When not to use

Implementing product features unrelated to MCP setup
Making destructive environment changes without user confirmation
Assuming private repository details not visible
Answering source-backed questions about Fusion Framework APIs, EDS components, or the skill catalog — once MCP is running, use fusion-research for that

Required inputs

Collect before proposing setup steps:

user environment (OS, editor/runtime)
target client where MCP will run (VS Code is primary target)
whether user's Equinor Entra account is available

If details are missing, ask concise follow-up questions first.

Instructions

Explain what this MCP server provides:
- Fusion-oriented MCP capabilities for retrieval and workflow support
- hosted as a managed service — no local infrastructure required for most developers
- retrieval tools: search, search_framework, search_docs, search_eds, search_indexes, search_backend_code
- tool surface may evolve over time
Guide user to set up the hosted production server — the only recommended path:
- no Docker, no API keys, no local clone needed
- VS Code authenticates via Microsoft Entra (Equinor account)
- use the one-click install link for prod (see references/vscode-mcp-config.md)
- or manual config with "type": "http" and server URL (see references/vscode-mcp-config.md)
- don't suggest local Docker, GHCR, or self-hosted alternatives unless user has explicit operational need
Describe the authentication flow:
- on first tool invocation VS Code prompts sign in with Equinor Entra account
- tokens managed automatically; silent renewal when possible, interactive prompt when needed
- access controlled by existing Fusion role assignments
Provide a lightweight MCP smell test:
- run initialize and confirm successful response
- run tools/list and confirm at least one tool returned
- run one non-destructive tools/call against an available tool
- pass criteria: call response is non-empty (content or structuredContent contains data)
- note: don't hard-code a fixed tool list; tool inventory can change between versions
Troubleshoot in documented order:
- Entra sign-in prompt not appearing → verify oauth.clientId in config and that VS Code is signed in with an Equinor account
- 401 Unauthorized → re-authenticate via VS Code account settings; ensure Equinor Entra account is active
- tools/list returns empty or tool call fails → verify MCP server entry is selected/enabled in VS Code and retry after reloading
- partial tool behavior → check VS Code Output > Copilot for error details and restart the MCP server
When MCP setup fails or user asks to file a bug, produce a bug report draft from assets/bug-report-template.md.
- default target repository: equinor/fusion-mcp
- include concrete repro steps, expected vs actual behavior, and troubleshooting already attempted
- include non-sensitive environment details (OS, VS Code version, MCP server URL, Entra account type)
- never include secrets, tokens, or raw credential values
For uncertainty or repo-private constraints, state assumptions explicitly and link to authoritative docs instead of guessing.

Expected output

Return:

short explanation of Fusion MCP and when to use it
hosted prod setup steps tailored to the user environment
validation checklist: run initialize (expect success response), run tools/list (expect at least one tool), run one tools/call (expect non-empty content or structuredContent)
troubleshooting steps mapped to observed error symptoms
bug report draft (when setup fails/misbehaves or user requests) using assets/bug-report-template.md with default target equinor/fusion-mcp
script snippets when user asks for copy/paste automation aids
assumptions and missing information called out explicitly
links to the exact upstream docs used

References

Safety & constraints

Never:

request or expose secrets, tokens, or credentials
invent setup commands that are not supported by project documentation
claim setup succeeded without validation output
run destructive commands without explicit user confirmation

Always:

prefer official repository documentation as source of truth
guide users to the hosted production server; do not suggest local Docker or self-hosted alternatives
provide least-privilege, minimal-change setup guidance first
separate confirmed facts from assumptions

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/equinor-fusion-skills-fusion-mcp/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

equinor-fusion-skills-fusion-mcp.ocm.jsonjson

{
  "ocm": "1",
  "id": "equinor-fusion-skills-fusion-mcp",
  "kind": "skill",
  "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.",
  "publisher": "equinor",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "fusion",
      "mcp",
      "setup",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Explain what Fusion MCP is and guide users through setting it up when they need Fusion-aware MCP capabilities in Copilot workflows."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/equinor/fusion-skills",
      "path": "skills/.experimental/fusion-mcp/SKILL.md",
      "ref": "HEAD",
      "url": "https://www.skills.sh/equinor/fusion-skills/fusion-mcp",
      "key": "equinor/fusion-skills/skills/.experimental/fusion-mcp/SKILL.md"
    },
    "license": "MIT"
  },
  "instructions": "# Fusion MCP Setup Guide\n\n## When to use\n\nUse when a user asks:\n- what Fusion MCP is\n- what it can do\n- how to install/configure it\n- how to verify it is working\n- how to troubleshoot a failing Fusion MCP setup\n\nTypical triggers:\n- \"what is fusion mcp\"\n- \"help me set up fusion mcp\"\n- \"how do I use fusion mcp with copilot\"\n\n## When not to use\n\n- Implementing product features unrelated to MCP setup\n- Making destructive environment changes without user confirmation\n- Assuming private repository details not visible\n- Answering source-backed questions about Fusion Framework APIs, EDS components, or",
  "cost": {
    "context_tokens": 1241
  }
}

Fetch it by URL: GET /api/v1/registry/equinor-fusion-skills-fusion-mcp/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.