Setting Up the MCP Server

This guide shows you how to connect the Paquet Builder MCP server to your preferred AI coding assistant.

The MCP server is a free add-on for all Paquet Builder editions (Freeware, Trial, Pro, and Ultimate).

1. Install Paquet Builder (GUI) on the target computer.

2. Download the MCP server — In Paquet Builder, go to Help → Check for Updates & Addons to download the MCP server installer. You can also download it directly from the MCP Server download page.

3. Run the MCP server installer. It will install PBMCPServer.exe into the Paquet Builder installation folder.

The MCP server is now ready to use by AI clients.

{
  "mcpServers": {
    "pbmcpserver": {
      "type": "stdio",
      "command": "C:\\Program Files\\Paquet Builder\\PBMCPServer.exe",
      "args": []
    }
  }
}

{
  "mcpServers": {
    "paquet-builder": {
      "command": "C:\\Program Files\\Paquet Builder\\PBMCPServer.exe",
      "args": []
    }
  }
}

{
  "mcpServers": {
    "paquet-builder": {
      "command": "C:\\Program Files\\Paquet Builder\\PBMCPServer.exe",
      "args": []
    }
  }
}

Once configured, your AI client should be able to list the available Paquet Builder tools. Try asking:

“List the available Paquet Builder tools”

Or open a project:

“Open the project at C:\MyProject\installer.pbpx”

If the MCP server is correctly configured, the AI will use the open_project tool and report the project details.

A typical MCP session follows this pattern:

1. Open a project — open_project with the path to a .pbpx file

2. Query current state — get_project_info, get_setting, collection_query

3. Make modifications — set_setting, collection_mutate, custom_actions_mutate

4. Compile — compile, then get_build_log to check results

5. Close — close_project

Here’s an example conversation with Claude Code using the MCP server:

You: Open my project at D:\Projects\myapp.pbpx and show me its current settings

Claude Code: Uses open_project and get_project_info — Your project “My Application” targets x64, uses LZMA2 compression with ultra level. Output: D:\Output\Setup.exe. 3 components, 142 files. Not signed.

You: Enable code signing with SHA-256 and sign the uninstaller too

Claude Code: Uses set_setting for digitalsign, signmethod, and csignuninst — Done. Digital signing is now enabled with SHA-256. The uninstaller will also be signed.

You: Now compile it and check for errors

Claude Code: Uses compile then get_build_log — Build completed successfully. Output: D:\Output\Setup.exe (12.4 MB). No errors, 0 warnings.

• Verify that PBMCPServer.exe exists at the configured path
• Check that the path uses double backslashes in JSON: C:\\Program Files\\...
• Ensure Paquet Builder is installed in the same directory as PBMCPServer.exe. The MCP server works with all editions — if no license is found, it runs in Trial mode

• The MCP server loads the full Paquet Builder engine on startup, which may take a few seconds
• Check that no other instance of PBMCPServer.exe is already running

• Use get_build_log after compile to see detailed error messages
• Ensure all source files referenced by the project are accessible from the build machine