MCP Server

What is MCP?

MCP means Model Context Protocol. It allows an AI agent, coding tool, browser agent, or automation client to connect to a service and ask for clearly defined information through known tools instead of scraping pages, guessing routes, or inventing answers.

We built the AZ2 MCP server because AI agents are now part of the web. If an agent wants to understand AZ2, search merchants, inspect categories, read public catalogue data, or view platform activity, it should not need to pretend to be a browser or scrape random HTML. It should have a clean way in. That is what this server provides.

Why AZ2 has an MCP server

AZ2 is built to be readable by humans, search engines, and AI systems.

The public website is rendered as proper HTML. The sitemap is available. The llms.txt file explains the site to language models. The /webmcp.json file publicly describes the available MCP-style tools and endpoints.

The MCP server completes that path.

It gives AI agents a proper interface to the same public data that users can browse on the site. It also lets us keep control of safety, authentication, rate limits, and access rules without hiding what the platform does.

We do not want agents scraping blindly. We do not want fake traffic pretending to be human. We do not want useful public catalogue data locked away behind unnecessary friction either. So we made a proper door.

Free access

Basic MCP access is free.

A standard user can create one API key for one user and one IP address. That key can be used by an AI agent or MCP client to request access to the AZ2 MCP server.

That free access is enough for normal reading, testing, catalogue lookup, merchant discovery, category lookup, brand lookup, and platform activity checks.

It is free because that is how we do things. Useful public access should not be made difficult just because the client is an AI agent instead of a person with a browser.

Authentication and AIE

The public MCP description is available for anyone to inspect at /webmcp.json. The tool list is public. The live endpoints are protected.

To call protected MCP endpoints, an agent needs an API key created from a normal AZ2 user profile. The API key is then used to request a short-lived AIE bearer token.

AIE is the AZ2 encrypted access layer. It protects requests without relying on ordinary cookie or session behaviour. The agent authenticates with an API key, receives a limited bearer token, and then uses that token to call the MCP tools it is allowed to use.

The first MCP access level is read-only. That means an agent can read public catalogue and platform data, but it cannot change accounts, create clicks, alter merchants, update products, or perform manager actions.

What agents can do

An authorised MCP client can use AZ2 tools to:

• search the catalogue
• find merchants
• inspect merchant details
• browse brands
• browse categories
• read public platform activity
• understand what AZ2 exposes without scraping the site

These tools are designed for AI agents, coding tools, and automated assistants that need structured access to AZ2.

Merchant access

Merchant-specific MCP tools can come later.

The first version is deliberately simple: public catalogue and platform read access only.

In future, a merchant account may be able to create merchant-scoped API keys, allowing AI tools to read merchant-specific data or help manage merchant information through carefully limited permissions.

That will only be added when the permission model is correct.

Why this matters

The web is changing.

Search engines still matter. Human visitors still matter. But AI agents now read, summarise, compare, recommend, and automate.

AZ2 is being built so those agents can interact honestly.

We would rather publish clear rules, clear endpoints, and clear access paths than force agents into scraping behaviour that looks like abuse.

The MCP server is part of that principle.

MCP Server

AZ2 MCP access is free for one user and one IP address.

Create an AZ2 account, generate an API key from your profile, and connect your MCP-compatible agent using that key.

Public tool description: /webmcp.json. Protected MCP access requires an AIE bearer token requested with a valid API key.