Magento 2 MCP Server

Created By
dzmitry-vasileuskia year ago
Overview

what is Magento 2 MCP Server?

Magento 2 MCP Server is a Model Context Protocol (MCP) server implementation for Magento 2, allowing AI assistants to interact with your Magento store through a standardized interface.

how to use Magento 2 MCP Server?

To use the Magento 2 MCP Server, install it via npm, start the server with your Magento URL and admin API token, and configure your MCP client to connect to it.

key features of Magento 2 MCP Server?

  • REST API integration with Magento 2
  • Secure authentication handling
  • Resource and tool handlers for common Magento operations
  • TypeScript implementation for type safety
  • Built on the official MCP SDK

use cases of Magento 2 MCP Server?

  1. Enabling AI assistants to manage Magento store operations.
  2. Facilitating automated order processing through REST API calls.
  3. Integrating with various tools for enhanced eCommerce functionalities.

FAQ from Magento 2 MCP Server?

  • What are the prerequisites for using Magento 2 MCP Server?

You need Node.js (v18 or higher), npm (v8 or higher), a Magento 2 instance with REST API access, and an admin API access token.

  • Is there a license for Magento 2 MCP Server?

Yes, it is licensed under the MIT License.

  • How can I contribute to the development?

You can clone the repository, install dependencies, and follow the development instructions provided in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dzmitry-vasileuski
Star
1
Language
JavaScript
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago