unplugin-mcp

- 🚀 Cross-Platform MCP Integration: Creates and manages an MCP server seamlessly across multiple build tools.
- 🧩 Bi-directional AI Integration: Not only provides context to AI assistants about your codebase, but also enables AI to actively modify and control your build process.
- 🧰 Rich built-in tools: Collection of built-in tools for analyzing module dependencies, inspecting build configuration, debugging error messages, and so on.
- 🛠️ Extensible Tool Framework: Create custom MCP tools with the simple UnpluginMcpTool interface to expose project-specific information or functionality.
- 🔍 Build Process Integration: Seamlessly integrates at any point in the plugin chain and hooks of your build tools like Rollup.
- 🔄 Persistent Server: Keeps running even after build completion in watch mode, enabling continuous AI interaction.
- 🌐 Standard Transport Layer: Uses HTTP and Server-Sent Events (SSE) for broad compatibility with AI assistants implementing the MCP protocol.

Here is an example of how to use the plugin with Rollup. The server will be started automatically when you run rollup in watch mode (rollup -w).

// rollup.config.js
import { defineConfig } from 'rollup';
import { rollupPlugin as mcp } from 'unplugin-mcp';
// import some built-in tools

import { ModuleTool, BuildConfigTool, BuildErrorTool } from 'unplugin-mcp/tools';
export default defineConfig({

  plugins: [

    // other plugins...

    mcp({

      provideUnpluginMcpTools: () => [

        new ModuleTool(),

        new BuildConfigTool(),

        new BuildErrorTool()

      ]

    }),

    // other plugins...

  ]

});

🚧 Usage on other bundlers is on the way.

> Notes: Currently, implementation of built-in tools is relatively simple and may not cover all edge cases.

| Tool | Description | Rollup | Webpack |
| ----------------- | --------------------------------------- | :----: | :-----: |
| ModuleTool | Analyze module dependencies and imports | ✅ | ❌ |
| BuildConfigTool | Inspect build configuration | ✅ | ✅ |
| BuildErrorTool | Debug build errors | ✅ | ✅ |
| BundleSizeTool | Inspect size of bundle and its modules | ✅ | ❌ |

- ✅ = Supported
- ❌ = Not yet implemented

You can extend the plugin with custom tools implementing the UnpluginMcpTool interface:

import { InputOptions } from "rollup";
import { UnpluginMcpTool, UnpluginMcpToolSetupOptions } from "unplugin-mcp";
import DeferredCtor, { Deferred } from 'promise-deferred';
import { UnpluginOptions } from "unplugin";
export class BuildConfigTool implements UnpluginMcpTool {

  private buildConfig: Deferred<InputOptions>;
affectsBuildProcess: boolean = false;
constructor() {

    this.buildConfig = new DeferredCtor<InputOptions>();

  }
setupMcpServer(mcpServer: any, options?: any) {

    mcpServer.tool(

      get-build-config,

      "Get build configuration",

      {},

      async () => {

        const cfg = await this.buildConfig.promise;
return {

          content: [

            {

              type: 'text',

              text: Build configuration: ${JSON.stringify(cfg)}

            }

          ]

        };

      }

    );
return mcpServer;

  }
registerPlugins(options?: UnpluginMcpToolSetupOptions): UnpluginOptions {

    let self = this;
return {

      name: 'build-config-tool',
rollup: {

        options(config) {

          self.buildConfig.resolve(config);

        }

      }

    }

  }

}

And then register it in the plugin options, for example, in the Rollup config:

// rollup.config.js
// ... 
plugins: [
  mcp({
    provideUnpluginMcpTools: () => [
      new BuildConfigTool()
    ]
  })
]
// ...