mcp-setup
This skill should be used when the user asks to "set up Axe MCP", "configure the Axe MCP Server", "install axe accessibility tooling", "connect Axe MCP", "authenticate axe", or runs /axe-accessibility:mcp-setup. It interactively wires the Axe MCP Server into the user's IDE/MCP client, helps choose a distribution (npm or Docker) and authentication (API key or OAuth), and verifies the connection.
Install
With your agent
Install OMGSkills skill "dequelabs/axe-accessibility:skills/mcp-setup" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/dequelabs/axe-accessibility /tmp/axe-accessibility && ln -s /tmp/axe-accessibility/skills/mcp-setup ~/.claude/skills/mcp-setupFrom README
Set up the Axe MCP Server Guide the user from nothing to a working, authenticated Axe MCP Server connection. There are two independent choices — distribution (npm or Docker) and authentication (API key or OAuth) — giving four valid configurations. Drive both with AskUserQuestion, then write the correct configuration for their client and verify it. The one universal prerequisite is an Axe DevTools for Web subscription whose Bundle plan includes Axe MCP Server access (pricing: https://www.deque.com/axe/devtools/pricing/). Without it the tools will fail to authenticate — point the user to the pricing page. If $1 names a client, skip the client question. Step 1 — Choose a distribution Ask which to use (AskUserQuestion). Recommend npm for local development — it is the default the plugin ships. npm (recommended) — runs as a local Node process via npx -y axe-mcp-server@1.6.0. Requires Node.js >= 22.19.0 and a one-time Chromium with Playwright pinned to that server release's version (below).