Fusion Mcp
Connect Claude, Cursor, or VS Code to Equinor’s hosted Fusion MCP so agents can call Fusion APIs through one approved remote server.
Overview
Fusion MCP is an agent skill for the Build phase that configures agents to use Equinor’s hosted Fusion MCP server at mcp.api.fusion.equinor.com/mcp.
Install
npx skills add https://github.com/equinor/fusion-skills --skill fusion-mcpWhat is this skill?
- Promotes hosted production Fusion MCP at mcp.api.fusion.equinor.com/mcp as the only recommended path for end users
- Replaces legacy fusion-poc-mcp PoC references with the equinor/fusion-mcp production server
- Explicit three-step validation criteria instead of a vague minimal checklist
- Troubleshooting structured as numbered Check/Fix substeps
- Coverage for users without an Equinor Entra account and contradiction fixes between recommended path and self-hosted exc
- Explicit three-step validation criteria documented in skill maintenance
- Hosted production endpoint: https://mcp.api.fusion.equinor.com/mcp
Adoption & trust: 924 installs on skills.sh; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent needs Fusion context but you are still on PoC MCP images, unclear validation steps, or conflicting setup guidance.
Who is it for?
Equinor engineers wiring VS Code, Claude Code, or Cursor to the official Fusion MCP in a corporate Entra environment.
Skip if: Solo indie builders with no Fusion or Equinor access, or teams that require fully self-hosted MCP without reading the documented exception path.
When should I use this skill?
You need agents to call Fusion via MCP and want the production hosted server path with validation and troubleshooting—not the old PoC image flow.
What do I get? / Deliverables
Your editor or agent targets the production Fusion MCP endpoint with explicit validation and structured fixes when Entra or network setup blocks the connection.
- Working MCP client configuration pointing at the production Fusion URL
- Validated connection pass against the documented three-step criteria
- Resolved auth or config issues using numbered Check/Fix troubleshooting
Recommended Skills
Journey fit
MCP wiring is a build-time integration step before agents can use Fusion data and tools in day-to-day coding. Canonical shelf is integrations because the skill documents hosted MCP endpoint config, call snippets, and validation—not product ideation or ops runbooks.
How it compares
Enterprise MCP integration package for Equinor Fusion—not a generic skills.sh task generator or public SaaS deploy skill.
Common Questions / FAQ
Who is fusion-mcp for?
Developers and platform users at Equinor who use AI coding agents and need Fusion data and tools through the supported remote MCP server.
When should I use fusion-mcp?
During build integrations when you add MCP to the IDE or agent, before relying on Fusion tools in workflows, and during ship review when validating that only the production MCP URL is configured.
Is fusion-mcp safe to install?
Treat it like any corporate integration: review the Security Audits panel on this Prism page, confirm you trust equinor/fusion-skills sources, and scope Entra credentials per your org policy before enabling network and API access.
SKILL.md
READMESKILL.md - Fusion Mcp
# Changelog ## 1.0.1 - 2026-05-07 ### patch - [#170](https://github.com/equinor/fusion-skills/pull/170) [`5e43223`](https://github.com/equinor/fusion-skills/commit/5e432232917b2b1642431d80cf1698bbefe80ee8) - Apply caveman-compress prose style to SKILL.md and references. - Drop articles, filler, hedging from SKILL.md activation body - Compress mcp-call-snippets and vscode-mcp-config references - [#168](https://github.com/equinor/fusion-skills/pull/168) [`6c56986`](https://github.com/equinor/fusion-skills/commit/6c56986a322214a89bddb6e549c4cdf8622a9025) - Fix diagnostic issues in fusion-mcp SKILL.md - Resolve contradiction between "only recommended path" and exception clause for self-hosted alternatives - Replace ambiguous "minimal validation checklist" with explicit three-step validation criteria - Restructure troubleshooting from flat bullets into numbered Check/Fix substeps to reduce cognitive load - Add coverage for users without an Equinor Entra account ## 1.0.0 - 2026-05-04 ### major - [#150](https://github.com/equinor/fusion-skills/pull/150) [`7f7c2d4`](https://github.com/equinor/fusion-skills/commit/7f7c2d480b8a562ddf6e5028a877b13a90bdb11a) - Update skill to reflect the new `equinor/fusion-mcp` server - Replace all references to the old `fusion-poc-mcp` PoC server and image - Promote the hosted production server (`https://mcp.api.fusion.equinor.com/mcp`) as the only recommended setup path; remove local Docker/GHCR guidance for end users - Update VS Code config to use HTTP + OAuth (Microsoft Entra) instead of Docker `stdio` with API keys - Rewrite `references/vscode-mcp-config.md` with one-click install link and manual OAuth config template - Update tool inventory to match the new server: `search`, `search_framework`, `search_docs`, `search_backend_code`, `search_eds`, `search_indexes` - Rewrite `references/mcp-call-snippets.md` with accurate per-tool parameter tables sourced from server code - Remove `references/local-http-quickstart.md` (local setup not promoted to end users) - Update troubleshooting to cover hosted-server failure modes (Entra auth, `401`, empty tool list) Resolves equinor/fusion-skills#149 ## 0.1.3 - 2026-04-22 ### patch - [#143](https://github.com/equinor/fusion-skills/pull/143) [`3c02e1d`](https://github.com/equinor/fusion-skills/commit/3c02e1d348a4de8ee9a0fd5a088ff18c0019dc2b) Thanks [@alftore](https://github.com/alftore)! - Document backend code tools in the Fusion MCP setup guide. - Add `search_backend_code` to retrieval tool examples - Add `get_backend_symbol` and `list_backend_projects` in the available backend tooling list ## 0.1.2 - 2026-03-21 ### patch - [#107](https://github.com/equinor/fusion-skills/pull/107) [`d75d8c6`](https://github.com/equinor/fusion-skills/commit/d75d8c60f15888fbe71340b53b2698f3361ac4c8) - Document `search_skills` in the MCP server tool surface. - add explicit tool listing to the setup instructions: `search_framework`, `search_docs`, `search_eds`, `search_skills`, `search_indexes`, `skills`, `skills_index_status` Resolves equinor/fusion-core-tasks#834 - [#106](https://github.com/equinor/fusion-skills/pull/106) [`1f8a01d`](https://github.com/equinor/fusion-skills/commit/1f8a01ddcb5c9afe9119a1fcf1ded2c6980036d0) - Connect `fusion-mcp` to `fusion-research` as a next-step redirect. - add "When not to use" entry directing source-backed research questions to `fusion-research` once MCP is running ## 0.1.1 - 2026-03-05 ### patch - [#55](https://github.com/equinor/fusion-skills/pull/55) [`2d346c8`](https://github.com/equinor/fusion-skills/commit/2d346c812b4927ed1fdf17c92d51856d1fdc09c3) - Add required ownership metadata (`metadata.owner`, `metadata.status`) to all skills. Owner is set to `@equinor/fusion-core` (repository default) and status is set according to skill lifecycle (`active` for production skills, `experimental` for early-stage skills). Sponsor metadata was considered but is not required for MVP.