fusion-mcp

Explain what Fusion MCP is and guide users through setting it up when they need Fusion-aware MCP capabilities in Copilot workflows.

1starsUpdated 7/30/2026

MCP Tools Documentation #setup #fusion #documentation #vscode #mcp #copilot

Security Assessment

Safe(95/100)

Security Score95/100

About fusion-mcp

Fusion MCP is a setup-and-explanation skill that guides users through understanding and configuring the Fusion MCP server so they can use Fusion-aware retrieval capabilities inside Copilot/VS Code workflows. It solves the onboarding problem for Equinor developers who need Fusion-specific MCP tools (search, search_framework, search_docs, search_eds, search_indexes, search_backend_code) but do not know how to install, authenticate, validate, or troubleshoot the connection.

The skill collects the user's environment (OS, editor, whether an Equinor Entra account is available), then walks them through the recommended hosted production server path, which requires no Docker, API keys, or local clone. It provides one-click install links and manual HTTP+OAuth config templates (referenced from bundled files), explains the Microsoft Entra authentication flow with automatic token renewal, and offers a lightweight validation checklist that runs initialize, tools/list, and a single non-destructive tools/call to confirm the server responds. Troubleshooting is documented in order for common symptoms like missing sign-in prompts, 401 errors, and empty tool lists. When setup fails, it drafts a sanitized bug report from a template targeting the equinor/fusion-mcp repository, explicitly excluding secrets and tokens.

It targets Equinor developers and Copilot users who need Fusion retrieval capabilities. Typical use cases include first-time MCP setup, verifying a working configuration, diagnosing authentication failures, and filing well-structured bug reports. This is a documentation and setup-guidance skill rather than an executable tool.

FAQ

What is Fusion MCP used for?

It provides Fusion-oriented MCP retrieval tools (such as search, search_framework, search_docs, search_eds, and search_backend_code) for use in Copilot/VS Code workflows; the skill itself explains and configures it rather than performing the searches.

What are the prerequisites?

An Equinor Microsoft Entra account and VS Code with GitHub Copilot. The recommended hosted production server needs no Docker, no API keys, and no local clone.

How is authentication handled?

On the first tool invocation, VS Code prompts sign-in with an Equinor Entra account; tokens are managed automatically with silent renewal when possible, and access is governed by existing Fusion role assignments.

How do I confirm the setup works?

Run a smell test: call initialize and expect a success response, call tools/list and expect at least one tool, then run one non-destructive tools/call and confirm the response content is non-empty. The tool inventory can change between versions, so it should not be hard-coded.

What if setup fails?

The skill follows a documented troubleshooting order (Entra prompt, 401, empty tool list) and can draft a sanitized bug report from a template targeting equinor/fusion-mcp, deliberately omitting any secrets, tokens, or credential values.