Let the plugin launch the Axe MCP Server with Docker so the image tag follows plugin releases

Open
#35 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
57/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
shell
Domain
devtools

Research direction

Start by reading the plugin’s user configuration options and bundled MCP config, the two affected contracts named in the issue. Trace how the npm server command and its pinned version are selected, then see how a Docker distribution could follow plugin releases while keeping npm as the default. Done means users can select Docker without hand-writing MCP config, the Docker image pin updates with plugin releases, and npm users see no change.

Written by the indexing model from the issue text.

Description

Problem

The plugin's bundled MCP config only launches the server with npm, so its pinned version moves with each plugin release. Docker users have to write their own config, which keeps whatever image tag they copied until they edit it. Docker users therefore drift from the release the plugin's guidance is written against, while npm users don't.

Acceptance criteria

  • A user can choose Docker as the distribution through the plugin's own configuration, without writing an MCP config by hand.
  • A Docker user who installs a plugin release that moves the pin runs the newly pinned image without editing anything.
  • npm remains the default, and existing npm users see no change.

Non-goals

  • Changing which server release is pinned.
  • Removing the hand-written Docker configs from the setup docs.

Affected contracts

The plugin's user configuration options and bundled MCP config.

Dominant language
Shell
Stars
3
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dequelabs/axe-accessibility

All issues in dequelabs/axe-accessibility

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.