AI Compatibility

Aspose.BarCode Cloud is built to work well with AI coding assistants and agents. There are two ways to bring barcode generation and recognition into an AI workflow:

  • AI Agent Skills shipped inside every SDK, so a coding agent follows the correct repository workflow and SDK-specific API patterns while writing code.
  • The Aspose.BarCode Cloud MCP Server, which lets an AI assistant generate, recognize, and scan barcodes directly through the Model Context Protocol without writing any code.

AI Agent Skills in the SDKs

Every Aspose.BarCode Cloud SDK repository ships an AI-agent skill — a SKILL.md file located under a skills/ folder. Point your coding agent (such as Claude Code, Cursor, or another agentic assistant) to this file when working with the SDK so that it follows the repo workflow and the SDK-specific API patterns for generating and scanning barcodes.

Each skill lives at skills/generate-and-scan-barcode-<language>/SKILL.md in its respective repository:

SDK Repository Skill path
.NET aspose-barcode-cloud-dotnet skills/generate-and-scan-barcode-dotnet/SKILL.md
Java aspose-barcode-cloud-java skills/generate-and-scan-barcode-java/SKILL.md
PHP aspose-barcode-cloud-php skills/generate-and-scan-barcode-php/SKILL.md
Python aspose-barcode-cloud-python skills/generate-and-scan-barcode-python/SKILL.md
Node.js aspose-barcode-cloud-node skills/generate-and-scan-barcode-node/SKILL.md
Go aspose-barcode-cloud-go skills/generate-and-scan-barcode-go/SKILL.md
Dart aspose-barcode-cloud-dart skills/generate-and-scan-barcode-dart/SKILL.md

How to use a skill

  1. Clone or open the SDK repository for your language.
  2. Point your coding agent to the SKILL.md file for that SDK (for example, by adding it to the agent’s context or referencing it in your prompt).
  3. Ask the agent to generate or scan barcodes. It will follow the repository workflow and the correct SDK API patterns described in the skill.

MCP Server

The Aspose.BarCode Cloud MCP Server is a Model Context Protocol server that lets AI assistants generate, recognize, and scan barcodes through the Aspose.BarCode Cloud API. It supports 60+ barcode symbologies, including QR, Code128, DataMatrix, EAN, PDF417, Aztec, and more.

Prerequisites

Available tools

Tool Description
generate_barcode Creates a barcode image from text with a customizable symbology, format (PNG, JPEG, SVG, GIF, TIFF), colors, resolution, rotation, and dimensions.
recognize_barcode Detects and reads specific barcode types from an image with configurable recognition modes (Fast, Normal, Excellent) and image source hints.
scan_barcode Auto-detects and reads the most commonly used barcodes without specifying a type.
list_barcode_types Lists all supported barcode symbologies for generation and recognition.

Docker build

Use this path when you want your MCP client to launch the server in a container. Clone the Aspose.BarCode Cloud MCP Server repository, then build the Docker image from the repository root:

docker build -t aspose-barcode-cloud-mcp .

The Docker client settings below run this image and mount a local data directory at /mnt/data inside the container. To test the image manually, run:

export ASPOSE_CLOUD_CLIENT_ID="your-client-id"
export ASPOSE_CLOUD_CLIENT_SECRET="your-client-secret"
docker run -i --rm \
  -e ASPOSE_CLOUD_CLIENT_ID \
  -e ASPOSE_CLOUD_CLIENT_SECRET \
  -v "/path/to/barcode-data:/mnt/data" \
  aspose-barcode-cloud-mcp

Local Go build

Use this path when you want your MCP client to launch a local Go binary instead of Docker. Clone the Aspose.BarCode Cloud MCP Server repository, then build the binary from the repository root:

go build -o Aspose.BarCode-Cloud-MCP .

You can also install the published module without cloning the repository:

go install github.com/aspose-barcode-cloud/Aspose.BarCode-Cloud-MCP@v0.2606.0

go install places the Aspose.BarCode-Cloud-MCP binary in your Go bin directory ($(go env GOPATH)/bin, usually ~/go/bin). Make sure that directory is on your PATH, or use the absolute binary path in the client settings.

To test the binary manually, set your credentials and point --mount-path at a local directory used to exchange barcode images:

Authentication

The server reads your credentials from two environment variables:

  • ASPOSE_CLOUD_CLIENT_ID — your application Client Id.
  • ASPOSE_CLOUD_CLIENT_SECRET — your application Client Secret.

Client configuration

The MCP server communicates over stdio, so the MCP client launches either the Docker command or the local Go binary directly. Pick one runtime and use the matching settings below.

Docker settings

Use these settings after building the aspose-barcode-cloud-mcp Docker image.

Local Go settings

Use these settings after building the local binary with go build, or after installing it with go install. If the binary is not on PATH, set command to its absolute path.

Once configured, restart your MCP client and ask it to generate, recognize, or scan barcodes. The assistant will call the tools above through the Aspose.BarCode Cloud API.

Overview