Inclusify Accessibility MCP server

Inclusify for AI agents

Connect your AI assistant to Inclusify and ask about the accessibility of your own websites: what is failing, where it lives in your source, and whether the fix you just wrote actually fixes it.

This repository is the install surface — the plugin manifests, the registry entry and one skill. The MCP server itself runs at https://app.inclusifyapp.com/api/mcp/customer and is not open source.

Install

Cursor — Add to Cursor, or install the Inclusify plugin from the Cursor marketplace.

Claude Code

claude mcp add --transport http inclusify https://app.inclusifyapp.com/api/mcp/customer

Or install this repository as a plugin marketplace, which brings the skill with it:

/plugin marketplace add magebitcom/inclusify-plugin

Gemini CLI

gemini extensions install https://github.com/magebitcom/inclusify-plugin

Everything else — Claude web and desktop, ChatGPT, VS Code, Windsurf, Continue and the rest are one URL each. The exact file and field name per client are documented at inclusifyapp.com/docs/integrations/mcp.

First connection

Your client registers itself and opens a browser tab. You sign in to Inclusify or create an account; if you have no organisation yet you are asked to name one, which is your workspace. A consent screen shows what the client gets — your basic profile and email address, nothing else. Nothing to paste, and no key to manage.

Installing this plugin is optional. If your assistant cannot install anything, the same tools answer over plain HTTP with a key we email you, and an assistant can create the account for you without you opening a browser at all. See inclusifyapp.com/docs/agents.

What you need for it to say anything useful

returns "no website by that name here" rather than scanning a stranger's site. An assistant can add one for you.

• The website has to be in your Inclusify account. Asking about a domain you have not added

website, and reading where a site stands, what plan it is on and whether the widget is live work on every plan including Free — the same things the panel already lets a Free customer do. What is actually wrong with a site, every check that loads a page, and the full-site crawl need Pro. The account-wide rollups need Enterprise.

• Plans gate the answers, not the connection. Finding out what the account holds, adding a

reporting a good one.

• A site that has never been scanned has no score yet, and the tools say so rather than

What it can do

Where a site stands, the fix list with the strings to grep for in your own templates, live keyboard and screen-reader checks, rendering under forced colours and 400% zoom, alt-text review, checking a fix before you deploy it, a pass/fail gate for CI, and running the product itself: widget on or off, appearance and profiles, publishing the accessibility statement, monitoring alerts, and filing findings into Jira or Slack.

Anything consequential asks first. Those tools return a plain-language description of exactly what would change plus a single-use token, and change nothing until you call again with it. The account owner then gets an email with an undo link.

Nothing here can move money: no tool changes a plan, sets payout details or charges anything. Upgrading hands you a link to do it yourself.

The current tool list, what each one deliberately does not know, and the allowances that bound the live checks are documented on the page linked above. It is generated from the server's own registry, so it cannot drift; this README deliberately does not restate it.

The skill

Shortened. The full README is on GitHub.