@adobe-commerce/commerce-extensibility-tools
Advanced tools
MCP server providing Temp Commerce Extensibility Tooling for deployment and management
A Model Context Protocol (MCP) server that provides Adobe I/O CLI tools for deployment and management of Adobe Developer App Builder applications, specifically designed for Adobe Commerce extensibility development.
# Clone the repository
git clone <repository-url>
cd commerce-extensibility-tools
# Install dependencies
npm install
# Install globally for Cursor integration
npm install -g .
Option A: One-Click Installation (Recommended)
Option B: Manual Configuration
Create or update your .cursor/mcp.json file:
{
"mcpServers": {
"adobe-io-tools": {
"command": "commerce-extensibility-tools-mcp-server"
}
}
}
Option C: Manual Configuration with Environment Variables
If you need to configure environment variables (e.g., for the documentation search tool), create or update your .cursor/mcp.json file:
{
"mcpServers": {
"adobe-io-tools": {
"command": "commerce-extensibility-tools-mcp-server",
"env": {
"CLOUDFLARE_WORKER_URL": "https://your-custom-worker.workers.dev"
}
}
}
}
Note: The CLOUDFLARE_WORKER_URL environment variable is optional. If not set, the documentation search tool will use the default worker URL: https://commerce-documentation-rag-service.apimesh-adobe-test.workers.dev
After configuration, restart Cursor IDE to load the new MCP server.
# Check if the command is available
which commerce-extensibility-tools-mcp-server
# Test the server directly
commerce-extensibility-tools-mcp-server
This MCP server enables integration with Adobe I/O CLI tools through Cursor IDE, specifically designed for Adobe Commerce extensibility development. It provides:
aio-app-dev to start local developmentaio-dev-invoke to call runtime actions locallyaio-app-deploy to deploy to productiononboard to set up event providers and Commerce integrationaio-where and other tools to manage configurationaio) installed globallynpm install -g @adobe/aio-cli
The MCP Inspector is an interactive developer tool for testing and debugging MCP servers. You can use it to:
# Run the inspector with your server
npm test
# Direct inspector command
npx @modelcontextprotocol/inspector node index.js
# With custom arguments
npx @modelcontextprotocol/inspector node index.js --verbose
npm testFor more information about the MCP Inspector, visit: MCP Inspector Documentation
aio) installed globallynpm install -g @adobe/aio-cli
aio login
aio console ws select
/ to access MCP toolsOnce configured, you can use these tools directly in Cursor:
/aio-app-deploy - Deploy your Adobe I/O application/aio-app-dev - Start local development server/aio-login - Authenticate with Adobe I/O/aio-where - Check current configuration/onboard - Configure event providers/aio-dev-invoke - Test runtime actions locally/search-commerce-app-builder-docs - Search Commerce App Builder documentationFor development and testing:
# Start the server directly
node index.js
# Or use npm
npm start
# Test with MCP Inspector
npm test
The search-commerce-app-builder-docs tool provides intelligent search capabilities for Commerce App Builder Extension documentation, helping developers find relevant information for coding decisions and implementation details.
# Search for general App Builder information
/search-commerce-app-builder-docs "What is App Builder?"
# Search for specific implementation details
/search-commerce-app-builder-docs "How to create custom actions in App Builder?"
# Search for configuration and setup information
/search-commerce-app-builder-docs "How to configure authentication in App Builder?"
The tool uses the following environment variables:
CLOUDFLARE_WORKER_URL: URL of the Cloudflare Worker for document retrieval
https://commerce-documentation-rag-service.apimesh-adobe-test.workers.dev{
"success": true,
"query": "What is App Builder?",
"resultsCount": 3,
"documents": [
{
"rank": 1,
"source": "src/pages/intro_and_overview/faq.md",
"content": "App Builder is a complete design, application, and runtime framework...",
"contentPreview": "App Builder is a complete design, application, and runtime framework...",
"metadata": {
"repository": "https://github.com/AdobeDocs/app-builder",
"source": "src/pages/intro_and_overview/faq.md"
}
}
],
"timestamp": "2025-08-21T13:12:19.214Z"
}
# Check if the command is available
which commerce-extensibility-tools-mcp-server
# If not found, reinstall globally
npm install -g .
# Verify the bin field in package.json
cat package.json | grep -A 5 '"bin"'
# Make sure the index.js file has execute permissions
chmod +x index.js
# Check if npm global bin is in your PATH
npm config get prefix
echo $PATH
.cursor/mcp.json is properly formattedaio loginaio where to check current configurationbin field is properly configured in package.jsonTo verify the MCP server is properly installed:
# Check if the command is available
which commerce-extensibility-tools-mcp-server
# Test the server directly
commerce-extensibility-tools-mcp-server
Enable verbose output for debugging:
# Set verbose flag when calling tools
# The server will show detailed command execution
commerce-extensibility-tools/
├── index.js # Main entry point
├── package.json # Dependencies and scripts
├── LICENSE # Apache 2.0 License
├── README.md # This file
├── .github/
│ └── workflows/
│ └── publish.yml # NPM publishing workflow
├── rules/ # AI Assistant Rules
│ ├── Cursor/ # Cursor IDE rules for Adobe Commerce
│ │ ├── README.md # Rules documentation
│ │ ├── main-orchestrator.mdc
│ │ ├── adobe-commerce-basics.mdc
│ │ ├── app-builder-technical-guide.mdc
│ │ ├── commerce-scope-guardrails.mdc
│ │ ├── deployment-and-cleanup.mdc
│ │ ├── developer-tools-integration.mdc
│ │ ├── development-workflow.mdc
│ │ ├── dos-and-donts.mdc
│ │ ├── events-and-webhooks-guide.mdc
│ │ ├── phase-control.mdc # NEW: Mandatory phase control protocol
│ │ ├── requirements-documentation.mdc
│ │ └── security-and-coding-standards.mdc
│ ├── Claude/ # Claude AI assistant rules
│ ├── Copilot/ # GitHub Copilot rules
│ └── Gemini/ # Google Gemini rules
└── src/
├── server.js # MCP server implementation
├── tools/ # Tool implementations
│ ├── index.js # Tool registry
│ ├── aio-app-deploy.js
│ ├── aio-app-dev.js
│ ├── aio-dev-invoke.js
│ ├── aio-login.js
│ ├── aio-where.js
│ ├── aio-app-use.js
│ ├── aio-configure-global.js
│ ├── onboard.js
│ ├── commerce-event-subscribe.js
│ └── search-commerce-app-builder-docs.js
├── schemas/ # JSON schema definitions
│ ├── aio-app-deploy.json
│ ├── aio-app-dev.json
│ ├── aio-login.json
│ ├── aio-where.json
│ ├── aio-app-use.json
│ ├── aio-dev-invoke.json
│ ├── aio-configure-global.json
│ ├── onboard.json
│ ├── commerce-event-subscribe.json
│ └── search-commerce-app-builder-docs.json
└── utils/ # Utility functions
├── sdk-schema-manager.js # SDK-aware schema management with Zod
├── command-executor.js
└── project-validator.js
src/tools/src/schemas/src/tools/index.jsimport { executeCommand } from '../utils/command-executor.js';
export default async function handleMyTool(args) {
const { param1, param2 } = args;
const command = 'my-command';
const cmdArgs = [param1, param2];
const result = await executeCommand(command, cmdArgs);
if (result.success) {
return {
content: [
{
type: 'text',
text: `✅ Success: ${result.output}`
}
]
};
} else {
return {
content: [
{
type: 'text',
text: `❌ Error: ${result.error}`
}
]
};
}
}
{
"name": "my-tool",
"description": "Description of what this tool does",
"inputSchema": {
"type": "object",
"properties": {
"param1": {
"type": "string",
"description": "Description of parameter 1"
},
"param2": {
"type": "boolean",
"description": "Description of parameter 2",
"default": false
}
},
"required": ["param1"]
}
}
This project includes comprehensive AI assistant rules for Adobe Commerce development:
Located in rules/Cursor/, these rules transform the AI assistant into an Adobe Commerce Solutions Architect with:
The AI assistant now enforces mandatory stopping points between development phases:
Required confirmation messages:
rules/Cursor/ directory to your project's .cursor/rules/ directoryWhen you request Adobe Commerce extension development, the AI will:
For issues related to:
Contributions are welcomed! Please read the Contributing Guide for more information.
This project is licensed under the Apache License, Version 2.0. See LICENSE for more information.
Version: 1.0.0
Last Updated: December 2024
Compatibility: Adobe Commerce PaaS & SaaS, App Builder Framework, Node.js 18+
FAQs
MCP server providing Temp Commerce Extensibility Tooling for deployment and management
We found that @adobe-commerce/commerce-extensibility-tools demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 5 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.
Security News
AGENTS.md is a fast-growing open format giving AI coding agents a shared, predictable way to understand project setup, style, and workflows.
Security News
/Research
Malicious npm package impersonates Nodemailer and drains wallets by hijacking crypto transactions across multiple blockchains.