Model Context Protocol
What is MCP?
Model Context Protocol (MCP) is an open standard that allows AI models to use external tools and services through a unified interface. Parcel provides an MCP server that enables AI assistants like GitHub Copilot, Claude, and Cursor to directly interact with Parcel's packaging tools, making it easier to set up and manage your Avalonia application builds.
Prerequisites
Before setting up the MCP server, ensure you have:
- Parcel .NET tool installed - Follow the Getting Started guide
- Valid license key - Set
PARCEL_LICENSE_KEY
environment variable to a valid license key from the portal
Parcel MCP is only available with a full Accelerate license.
Supported AI Assistants
Parcel's MCP server works with various AI coding assistants:
- VSCode with GitHub Copilot (used in examples below)
- Visual Studio with Copilot - Supports similar
mcp.json
file formats - Claude Code
- Cursor
Setting Up the MCP Server
Parcel provides an STDIO type MCP server, available by running the parcel mcp
command.
Adding MCP Server in VSCode
-
Open the command palette and run "MCP: Add Server"
-
Select "stdio" server type
-
Set the command to run as:
parcel mcp
-
Set server name to "parcel"
-
Choose to install the server locally or globally
VSCode will generate a .vscode/mcp.json
file:
{
"servers": {
"parcel": {
"type": "stdio",
"command": "parcel",
"args": [
"mcp"
]
}
},
"inputs": []
}
Adding MCP Server in Claude Desktop
- Open Claude's Setting -> Developer page, you will find "Edit Config" button
- This button opens "claude_desktop_config.json" manifest file.
- Edit this file to include Parcel MCP server:
{
"mcpServers": {
"parcel": {
"command": "parcel",
"args": [
"mcp"
],
"env": {
"PARCEL_LICENSE_KEY": "YOUR_ACCELERATE_LICENSE_KEY"
}
}
}
}
- You will also likely need standard FileSystem MCP server in addition to Parcel MCP. Claude Desktop doesn't have it enabled by default.
Unlike VSCode, in our testing, Claude Desktop didn't pass system-wide env variable to the MCP servers. Which is why this config has PARCEL_LICENSE_KEY
defined explicitly.
Capabilities
Once the MCP server is configured, your AI assistant can help with:
Project Configuration
- Create parcel configurations from existing .NET projects
- Configure application properties like package name, display name, icons, and bundle identifiers
- Set up build targets for multiple platforms and architectures
Code Signing Setup
- Windows Azure Trusted Signing - Configure certificates and signing parameters
- macOS Code Signing - Set up P12 certificates and provisioning profiles
- macOS Notarization - Configure Apple ID and app-specific passwords
Building and Packaging
- Build and package applications for multiple platforms (Windows, macOS, Linux)
- Generate installers in various formats (DMG, DEB, NSIS, ZIP, etc.)
- Cross-platform packaging with runtime-specific outputs
Usage Examples
Simply describe what you want to accomplish in natural language. The AI assistant will use the MCP server to execute the appropriate Parcel commands:
Project Setup:
"Create a packaging config for my Avalonia project and set up macOS signing"
Packaging:
"Package my app for macOS as a DMG with code signing enabled"
Configuration Management:
"Update my app's display name and icon, then rebuild the Windows installer"
The AI assistant will guide you through the process, execute commands, and help resolve any configuration issues that arise.