Axe MCP Server Version 1.9.1 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 17, 2026

Overview

This v1.9.1 release fixes Intelligent Guided Tests (IGTs) that stopped responding in long sessions signed in with axe-auth, and replaces several raw technical errors with messages that explain what went wrong and what to do next.

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.

Bug Fixes

IGTs Keep Working After Your Sign-In Refreshes

If you sign in with OAuth 2.0 through axe-auth, your access token is refreshed automatically before it expires. Before this release, Intelligent Guided Tests kept using the token from when the server started, so once that token expired every IGT stopped responding until it timed out, and only restarting the server fixed it. IGTs now use the current token, including IGTs that are already running when the token refreshes, so long sessions keep working without a restart.

Clearer Error Messages

  • The axe extension doesn't load. When the axe extension can't start in the server's browser, scans used to fail after 30 seconds with a raw browser timeout. The error now says the extension didn't load, that a browser extension policy or security software may be blocking it, and links to Troubleshooting. If you point the server at your own Chrome with AXE_CHROME_PATH, it also tells you that Google Chrome 137 and later can't load the extension and to use Chrome for Testing instead.
  • The page changes during a scan. If the page navigates, reloads, or hot-reloads while analyze is running, the error now says the page changed during the scan and that retrying once the page has finished loading should help, instead of showing a raw browser messaging error.
  • A refreshed sign-in can't be saved. When axe-auth refreshes your sign-in but can't save the new tokens (for example, because the system keychain refuses the write), the warning now says your next run may require signing in again. Before, it said you always would, but the previous sign-in usually still works.