⚠️

重要前提

安装AI Skills的关键前提是：必须科学上网，且开启TUN模式，这一点至关重要，直接决定安装能否顺利完成，在此郑重提醒三遍：科学上网，科学上网，科学上网。查看完整安装教程 →

Fusion MCP 设置指南：安装、配置与故障排除完整教程

fusion-mcp by equinor/fusion-skills

61 周安装量

GitHub

安装命令

npx skills add https://github.com/equinor/fusion-skills --skill fusion-mcp

开发 VSCode Docker

🇨🇳中文介绍

Fusion MCP 设置指南

使用时机

当用户询问以下问题时使用此技能：

Fusion MCP 是什么
它能做什么
如何安装/配置它
如何验证它是否正常工作
如何排查 Fusion MCP 设置失败的问题

典型触发词：

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

避免使用的情况

以下情况请勿使用此技能：

实现与 MCP 设置无关的产品功能
未经用户确认进行破坏性的环境更改
假设无法查看的私有仓库详细信息
回答关于 Fusion Framework API、EDS 组件或技能目录的、需要源码支持的问题——一旦 MCP 运行，请使用 fusion-research 来处理这类问题

必要输入

在提出设置步骤前收集：

用户环境（操作系统、Shell、编辑器/运行时）
运行 MCP 的目标客户端（例如 VS Code MCP 配置或终端）
用户是希望使用发布的镜像（GHCR）还是从源码本地构建
传输模式（stdio 用于编辑器客户端配置，或 HTTP 端点用于本地检查）
所需访问权限是否已就绪（Docker、用于 GHCR 的 GitHub 认证、API 密钥）

如果缺少详细信息，请先提出简洁的后续问题。

操作说明

解释此 MCP 服务器提供的内容：

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

🇺🇸English

Fusion MCP Setup Guide

When to use

Use this skill when a user asks:

what Fusion MCP is
what it can do
how to install/configure it
how to verify that 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

Do not use this skill for:

implementing product features unrelated to MCP setup
making destructive environment changes without user confirmation
assuming private repository details that are 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, shell, editor/runtime)
target client where MCP will run (for example VS Code MCP config or terminal)
whether the user wants released image (GHCR) or local build from source
transport mode (stdio for editor client config or HTTP endpoint for local checks)
whether required access is ready (Docker, GitHub auth for GHCR, API keys)

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
- tool surface may evolve over time as the server is a PoC
- examples today may include retrieval, index guidance, metadata summaries, and skill discovery
- retrieval tools: search_framework, search_docs, search_eds, search_skills, search_indexes
- skill advisory: skills, skills_index_status
Use the official README quick start as source of truth, then present a minimal 2-step setup path:
- choose image source: GHCR release image or local build
- configure VS Code MCP using Docker stdio only (scope for this iteration)

Expected output

Return:

short explanation of Fusion MCP and when to use it
setup path tailored to the user environment (GHCR/local, stdio/HTTP)
minimal validation checklist with concrete pass criteria
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-poc-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
provide least-privilege, minimal-change setup guidance first
separate confirmed facts from assumptions
keep guidance scoped to VS Code + Docker for this iteration

Weekly Installs

Repository

equinor/fusion-skills

First Seen

Mar 2, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykWarn

Installed on

github-copilot61

opencode57

gemini-cli57

codex57

kimi-cli57

cursor57

React 组合模式指南：Vercel 组件架构最佳实践，提升代码可维护性

123,700 周安装

For GHCR image setup, include auth prerequisites before pull/run:

gh auth login -h github.com -w
gh auth refresh -h github.com -s read:packages
gh auth token | docker login ghcr.io -u <github-username> --password-stdin

For local build setup, use the documented sequence so the API is built, started, and validated:

cp .env.example .env
docker compose up -d --build api
then follow the health-check step in references/local-http-quickstart.md to confirm the API is healthy

Provide required configuration categories without exposing secret values:

Azure Search keys (AzureSearch__*)
Foundry keys/settings (Foundry__*)
optional runtime vars (ASPNETCORE_ENVIRONMENT, HOST_PORT)

Provide a lightweight MCP smell test:

run initialize and confirm a successful response
run tools/list and confirm at least one tool is returned
run one non-destructive tools/call against an available tool
pass criteria: call response is non-empty (content or structuredContent contains data)
note: do not hard-code a fixed tool list; tool inventory can change between versions

Troubleshoot in documented order:

GHCR unauthorized/403 -> refresh GH auth and Docker login
Apple Silicon manifest mismatch -> add Docker arg --platform linux/amd64
tools/list returns empty or basic query fails -> re-check API key env mapping and MCP server selection in VS Code
startup looks healthy but tool behavior is partial -> re-check env/config/auth alignment and restart MCP server

When MCP setup fails, MCP behavior is incorrect, or the user asks to file a bug, produce a bug report draft from assets/bug-report-template.md.

default target repository: equinor/fusion-poc-mcp
include concrete repro steps, expected vs actual behavior, and troubleshooting already attempted
include non-sensitive environment details (OS, VS Code version, Docker version, image tag, transport mode)
never include secrets, API keys, or raw token values

For uncertainty or repo-private constraints, state assumptions explicitly and link to authoritative docs instead of guessing.