Download the PHP package angeo/module-mcp-server without Composer

On this page you can find all versions of the php package angeo/module-mcp-server. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package module-mcp-server

Angeo MCP Server for Magento 2

CI Packagist Version Downloads Mage-OS Directory

Give AI agents a real API to your store — instead of letting them scrape it.

angeo/module-mcp-server exposes your Magento 2 / Adobe Commerce (self-hosted) catalog to AI agents over the Model Context Protocol — the open standard created by Anthropic and adopted across the agentic-commerce ecosystem (Adobe shipped an MCP server for its cloud platform at Summit 2026; this module is the equivalent for everyone running Magento themselves).

Claude, Gemini, ChatGPT-based agents, and custom shopping assistants get live, structured, rate-limited answers — current prices, real stock, canonical URLs — instead of scraping stale HTML.

Read-only by default. The four built-in tools show what an anonymous shopper already sees, and nothing else. Writing tools come from separate, opt-in modules:

Protocol: MCP 2026-07-28 (stateless, no handshake) and every earlier revision back to 2024-11-05, on the same /mcp endpoint. See Protocol versions.

Requirements

Installation

The server is enabled read-only by default. Verify from the CLI:

…or over HTTP:

⚠️ Full-page cache bypass (read this)

/mcp must never be served from Varnish/LiteSpeed/FPC — a cached JSON-RPC response is corrupt by definition. The module sends Cache-Control: no-store, but front caches configured to ignore backend headers need an explicit rule.

Varnish (add to vcl_recv before the builtin):

LiteSpeed (.htaccess):

Tools

Tool Arguments Returns
search_products query, category_id?, price_min?, price_max?, page?, page_size?, sort? live items: sku, name, price, stock, URL, image, short description + total count
get_product sku full card: description, live price/stock, URL, image; configurable variants with per-variant option values, price, stock
list_categories parent_id?, depth? (≤4) active category tree with URLs and product counts
get_store_info — store name, currency, locale, ships-to countries, links to llms.txt and /.well-known/ucp

Prices reflect the configured customer group (default NOT LOGGED IN) — agents see exactly what an anonymous shopper sees. Disabled products, other-website products, and invisible products are indistinguishable from absent.

Configuration

Stores → Configuration → Angeo → MCP Server

Setting Default Notes
Enable MCP Server Yes per store view
Require Bearer Token No see Authentication below
Log Agent Calls Yes JSONL in var/log/angeo_mcp_agent.jsonl — timestamp, tool, user agent, duration; never payloads or tokens
Price Customer Group NOT LOGGED IN which prices agents see
Default / Max Page Size 10 / 50 hard protocol cap 100
Rate Limit (req/min) 60 per IP (+ token when present); 0 disables
Accept Customer Tokens No 2.3.0 — lets tools act for a signed-in shopper; see Authentication
Accept Storefront Customer Tokens (testing) No 2.4.0 — ordinary Magento customer tokens at /mcp; never in production
MCP Token Lifetime (min) 60 2.4.0 — account linking; 5 – 1440
Allowed Browser Origins — 2.3.0 — extra Origin values allowed; the store's own URLs always are
Strict MCP Headers Yes 2.3.0 — reject 2026-07-28 requests without the required headers
Tool List Cache Hint (s) 300 2.3.0 — ttlMs sent with tools/list and prompts/list

The call log also records the caller kind (anonymous, integration, customer) and the protocol era since 2.3.0. Never an id or a token.

CLI test as a signed-in customer (needs shell access, no token):

Getting the agent to actually use your store

A connector that works is not the same as a connector that gets picked. A model chooses between your tools and its own general product search before it calls anything, using only three things: the instructions you send on connect, the tool names, and the tool descriptions. Everything below shapes those three.

Since 1.2.0 the defaults do the right thing with no configuration:

Setting Default What it does
agent/store_label store view name The name a model matches "check Acme" against. Falls back to the website name when the store view is still called something generic.
agent/instructions (empty — generated) Built from the store name and the tools actually installed, so it stays true when you add or remove the checkout module.
agent/anchor_descriptions Yes Appends "Applies to the {store} store only." to every tool description.
agent/tool_titles Yes Generates title annotations ("Search Acme products") for the client's permission screen.

Set agent/store_label to the name customers know you by. It is the single highest-leverage field here. "Default Store View" gives a model nothing to recognise; "Acme Outdoor" gives it something a shopper will actually type.

Conversation starters

Since 1.3.0 the server also exposes MCP prompts — ready-made requests the client offers the shopper after connecting, with the store name already in them:

Prompt What the shopper gets
Browse store Categories and a sense of the range
Find something in store A live catalog search for what they type
About store Shipping, currency, policies
Buy from store Find, cart, shipping, checkout — only when the checkout module is installed

A prompt is an offer, not an action: the shopper picks it. No MCP server can start a conversation turn on its own, and clients surface prompts to the user rather than to the model, so the model will not suggest one unprompted. What this removes is the guessing — the shopper no longer has to find a phrasing that beats the client's own product search.

Register your own by implementing Angeo\McpServer\Api\PromptInterface and adding it to PromptRegistry in di.xml, exactly as with tools.

What this will and will not do

It will not win a cold, unanchored shopping request. "Find me a grey backpack", with no reference to any shop, will often still go to a general product search — and reasonably so: one store should not win a question about the whole market. Prompts that reliably reach a connector are the ones a general search cannot answer:

A good demo starts with list_categories or get_store_info and moves to products from there. Once the context is established, even a vague product request goes to the catalog.

Authentication (optional)

Public read-only mode is the default: the tools expose only storefront-visible data. To require a token for everything:

  1. System → Extensions → Integrations → Add New Integration — name it e.g. AI Agents, grant it only the MCP Server Agent Access resource.
  2. Activate it and copy the Access Token.
  3. Set Require Bearer Token = Yes.
  4. Agents send Authorization: Bearer <token>.

Revoking the integration instantly cuts agent access. Only an Integration token passes this check. Customer and admin tokens do not (fixed in 2.3.0 — see the changelog).

Signed-in customers (2.3.0)

Some tools act for one shopper: their orders, their cart. They need to know who the shopper is. Turn on Security → Accept Customer Tokens.

Setup Headers Token
Production: an MCP connector acts for the shopper Authorization: Bearer <integration token> and X-Customer-Token: amc_… MCP-only token from account linking
Testing only: Claude Code or the MCP Inspector talks to the store directly Authorization: Bearer <customer token> ordinary Magento customer token; needs Accept Storefront Customer Tokens (testing) = Yes

Why two kinds? An ordinary Magento customer token was issued for the store's REST and GraphQL APIs. It can change addresses or read every order there. The MCP specification says a server must not accept tokens that were not issued for it, and a connector should hold no more power than it needs. An amc_ token works at /mcp only, only next to the Integration token of the connector it was issued to, and stops the moment the shopper disconnects.

An X-Customer-Token that does not verify gives HTTP 401. It never falls back to anonymous.

Tools read the result through Angeo\McpServer\Api\CallerContextInterface. They never take a customer id from tool arguments.

A customer token alone does not satisfy Require Bearer Token. That setting still means "only approved agent platforms".

Account linking (2.4.0)

Customer tokens live one hour by default, and Magento has no refresh token for customers. So a connector cannot simply keep one. Account linking solves this without the connector ever seeing a password:

  1. The connector sends the shopper's browser to GET /mcp/link with redirect_uri, state, code_challenge and code_challenge_method=S256.
  2. The shopper signs in on your store (normal login page) and approves on a page that names the connector and says what it can and cannot do.
  3. The store redirects to redirect_uri?code=…&state=…. The code works once, for two minutes, and only with the PKCE verifier.
  4. The connector calls POST /mcp/link/exchange with its Integration token and {code, code_verifier, redirect_uri}. It gets a long-lived grant, a first MCP-only token (amc_…), expires_in and a masked email.
  5. When the token expires (MCP Token Lifetime, 60 minutes by default), the connector calls POST /mcp/link/token with {grant} and gets a fresh one.
  6. It sends the token as X-Customer-Token next to its Integration token.
Endpoint Body Answer
POST /mcp/link/exchange code, code_verifier, redirect_uri grant, customer_token (amc_…), expires_in, customer_label
POST /mcp/link/token grant customer_token (amc_…), expires_in
POST /mcp/link/revoke grant {"ok": true} (always)

All three need Authorization: Bearer <integration token>. Errors are invalid_client (401), invalid_request / invalid_grant (400) and slow_down (429). They never say which check failed.

What protects the shopper:

Set it up under Account Linking: enable it, paste the connector's redirect URI (for mcp.angeo.dev: https://mcp.angeo.dev/authorize/linked) and the name shoppers should see. Accept Customer Tokens must be on too.

Browser origins

Browsers send an Origin header. Unknown origins get HTTP 403. This protects against DNS rebinding, as the MCP transport requires. The store's own URLs are always allowed. AI platforms connect server-to-server without Origin, so they are not affected. To use a browser tool such as the MCP Inspector, add its origin under Security → Allowed Browser Origins (e.g. http://localhost:6274).

Connecting an agent

Claude Desktop / Claude Code (.mcp.json):

Any MCP client works the same way, old or new. See below.

Protocol versions

Revision How the version is chosen
2026-07-28 No handshake. Each request names its version in _meta and in the MCP-Protocol-Version header. server/discover returns versions, capabilities and instructions.
2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05 initialize handshake, as before.

What 2026-07-28 changes on the wire, and what this server does:

Older clients see no change.

Extending: add your own tools

Implement Angeo\McpServer\Api\ToolInterface and register it in the pool:

Contract details (schemas, error handling, PII rules) are documented on the interface.

Roadmap

Cart and checkout tools, once planned here as 1.1, shipped as angeo/module-mcp-checkout.

The Angeo agentic stack

This module is part of an open-source suite that makes a Magento store legible to AI systems end-to-end: module-llms-txt (discovery files), module-ucp (UCP profile), module-rich-data (structured data), this server (live agent access), and the opt-in module-mcp-checkout and module-mcp-reorder tools.

Is your store actually visible to AI shopping agents? Run the free scan: https://angeo.dev/scan · Implementation and audits: [email protected]

"Add to Claude" button

A Magento widget that lets a shopper connect this store to Claude in one click. Place it from Content → Widgets into the footer, a sidebar or any CMS page — no template edits.

Set the connector first, in Stores → Configuration → Angeo → MCP Server → Claude Connector:

Field Meaning
Connector URL The HTTPS MCP endpoint shoppers connect to, issued by your MCP provider — e.g. https://mcp.example.com/t/your-store/mcp
Connector Name Shown in Claude's connector list. Defaults to the store name

This is not your store's own /mcp path. That endpoint has no OAuth and cannot be added to Claude directly. The URL here comes from whatever service fronts your MCP server with an authorization layer.

There is no default URL, and the button renders nothing until a valid HTTPS value is set — so installing the module on a store that has not been onboarded changes nothing on the storefront.

The link opens Claude's add-connector dialog with the URL and name prefilled. The shopper reviews and approves it there; the link itself grants no access.

License

MIT — see LICENSE.


All versions of module-mcp-server with dependencies

PHP Build Version
Package Version
Requires php Version ~8.1.0||~8.2.0||~8.3.0||~8.4.0||~8.5.0
magento/framework Version >=103.0.6 <104
magento/module-authorization Version >=100.4.6 <101
magento/module-catalog Version >=104.0.6 <105
magento/module-catalog-inventory Version >=100.4.6 <101
magento/module-configurable-product Version >=100.4.6 <101
magento/module-cron Version >=100.4.6 <101
magento/module-customer Version >=103.0.6 <104
magento/module-integration Version >=100.4.6 <101
magento/module-store Version >=101.1.6 <102
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package angeo/module-mcp-server contains the following files

Loading the files please wait ...