Mcpfusion MCP Server

MCP 2.0-compliant TypeScript framework for building typed, governed server architectures.

Data last scanned today · Reviewed today

38★ 256TypeScriptApache-2.0

Overview

MCP Fusion provides a TypeScript-based framework specifically architected to build MCP 2.0-native servers. It emphasizes security by routing data through a typed egress firewall and dynamically managing tool visibility based on workflow states, ensuring that raw data handling is constrained by defined architectural boundaries. The framework integrates a machine-readable architectural contract known as SKILL.md. This file allows AI coding agents to understand and generate compliant, governed server code. It offers full support for MCP 2.0 features, including stateless protocol handling, Multi Round-Trip Requests (MRTR), and HMAC-SHA256 sealed request states.

Our verdict

With a high-risk security score of 38/100, users should exercise caution when adopting this framework. The primary concerns stem from the project being community-maintained rather than vendor-official and the lack of an independent editorial review. While it boasts zero direct dependencies—which reduces the supply-chain surface—the absence of verified authentication and read-only mode protocols makes it unsuitable for production environments where strict security auditing is required.

Zero direct dependencies reduce potential supply-chain risks.
Full native compliance with MCP 2.0 protocol specifications.
Includes machine-readable SKILL.md for automated agent development.
Implements HMAC-SHA256 sealed state for request security.

Community-maintained project lacking official vendor verification.
Authentication methods have not yet undergone security review.
Read-only capabilities remain unverified by editorial analysis.
Single-contributor repository increases long-term bus-factor risk.

Setup

Claude Desktop

{
  "mcpServers": {
    "mcpfusion": {
      "args": [
        "-y",
        "@mcpfusion/dev"
      ],
      "command": "npx"
    }
  }
}

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.

No read-only mode — running this grants full read/write access.
No built-in authentication — anyone with access to this config can invoke every tool it exposes.

Compatibility

Client	Local	Docker	Remote	Read-only
Claude Desktop
Cursor
VS Code
Windsurf
ChatGPT

Frequently asked questions

›What are the core technical prerequisites for using MCP Fusion?

The framework requires TypeScript version 5.7 or higher.

›How does MCP Fusion handle security and data egress?

The framework enforces security by routing all data through a typed egress firewall and physical removal of tools from the agent's namespace when workflow state forbids them.

›Is this server compliant with the latest MCP specification?

Yes, MCP Fusion is fully compatible with MCP 2.0 protocol revision 2026-07-28.

›Does the framework support stateless operation?

Yes, it supports a stateless transport mode that uses per-request serving without requiring an initialize handshake.

›How can AI coding agents assist in building servers with this framework?

You can provide the included SKILL.md file to AI agents like Cursor or Claude Code, which instructs them to build servers that automatically inherit the framework's security, governance, and state machine patterns.

›Are older MCP features supported?

Features deprecated in MCP 2.0 remain functional during the deprecation window, which lasts until July 28, 2027, but they are marked with deprecation guidance for migration.