Axe MCP Server Version 1.8.0 Release Notes

This page is not available in the language you requested. You have been redirected to the English version of the page.
Link to this page copied to clipboard
Not for use with personal data

Release Date

November 11, 2026

Overview

This v1.8.0 release introduces the Free plan for the Axe MCP Server: unlimited accessibility scans with the analyze tool, no credit card required.

note

The Axe MCP Server Free plan launches on November 12, 2026. Until then, the Free plan features described here aren't available.

important

To get this release:

  • Docker — re-pull the image: docker pull dequesystems/axe-mcp-server:latest
  • npm — no separate install step is required; npx runs the latest published version. See Choosing a Distribution.

New Features

Free Plan

Anyone can now use the Axe MCP Server for free. The Free plan includes unlimited analyze scans with the standard axe-core ruleset. Sign up, authenticate with an API key or by signing in through the @deque/axe-auth CLI, and connect your coding agent. The Free plan requires Axe MCP Server 1.8.0 or later.

See Free and Premium Plans to compare plans.

Bug Fixes

  • AI reasoning is now returned for Interactive Elements and Modal Dialog findings. Previously, aiReasoning was filled in only for Keyboard findings. It now carries the same "Why AI made this recommendation" text you see in axe DevTools.
  • Automated Keyboard and Interactive Elements IGTs now respect selector. When you scope analyze with selector, these tests check only that part of the page instead of the whole page.
  • One failed guided test no longer causes the rest to fail. If a test fails or times out, the server restarts the browser before running the next test in the same call.
  • Canceling a request now stops the scan. When your MCP client cancels an analyze call, the server closes the browser and skips any guided tests that haven't started.
  • The scan browser now uses your proxy on macOS and Windows. Previously, only Linux and Docker sent the scan browser's traffic through HTTPS_PROXY, so guided tests could fail on networks that only allow traffic through a proxy.
  • Network problems are no longer reported as API key errors. DNS failures, refused connections, and timeouts now produce a message that names the host and points to your network, VPN, or proxy. Failed connections are retried automatically.
  • A rejected axe-auth sign-in now says so. Instead of "Invalid API key," the message tells you to sign in again with npx @deque/axe-auth login.

Is this page helpful?

Help us improve this page

Still need help?