Inclusify Accessibility

com.inclusifyappPublished by inclusifyapp.comOfficial publisherv1.0.2Updated Oct 26, 2026

Accessibility and WCAG data for your own websites: fix lists, live checks, and fix validation.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that gives an assistant WCAG accessibility data for your own Inclusify websites: fix lists, live checks and fix validation.

What you can do
  • Read where a site stands, its score, plan and widget status, and the fix list with strings to grep in your templates
  • Run live keyboard and screen-reader checks, forced-colour and 400% zoom rendering, and alt-text review
  • Validate a fix before deploying and run a pass/fail gate for CI
  • Manage the product: widget on or off, appearance and profiles, publishing the accessibility statement, monitoring alerts
  • File findings into Jira or Slack and add websites to the account
When to use it
Useful when you maintain websites in an Inclusify account and want an assistant to find accessibility failures, point at the source strings to change, and confirm a fix actually resolves the issue before deploying.
Requirements
A remote endpoint at app.inclusifyapp.com over streamable HTTP; OAuth sign-in with a browser consent screen (basic profile and email), or an emailed key for plain HTTP clients. The website must already be in your Inclusify account. Pro is needed for issue detail, page-loading checks and full-site crawls; Enterprise for account-wide rollups.
Before you install
Consequential tools return a description plus a single-use token and change nothing until called again with it; the account owner then gets an undo email. Tools can change widget settings, publish the accessibility statement, file findings into Jira or Slack, and add websites. No tool moves money or changes plans. Only sites in your account are queried.

Installation

In SourceWeft

  1. Open Inclusify Accessibility in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.inclusifyapp%2Finclusify/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "inclusify-accessibility": {
      "type": "http",
      "url": "https://app.inclusifyapp.com/api/mcp/customer"
    }
  }
}

README

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

bash
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:

bash
/plugin marketplace add magebitcom/inclusify-plugin

Gemini CLI

bash
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

  • The website has to be in your Inclusify account. Asking about a domain you have not added returns "no website by that name here" rather than scanning a stranger's site. An assistant can add one for you.
  • Plans gate the answers, not the connection. Finding out what the account holds, adding a 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.
  • A site that has never been scanned has no score yet, and the tools say so rather than reporting a good one.

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

skills/accessibility-fix-loop teaches the loop that actually resolves issues rather than silencing them: read the fix list, grep your source for the strings it hands you, validate the markup before deploying, then confirm against a later scan. It also tells the assistant to take a masked verdict seriously — aria-hidden, display: none and swapping a button for a div all make a scanner go quiet while leaving the barrier in place.

Contributing

Issues and pull requests on the manifests, the skill and the docs are welcome. Problems with the server itself, your account or your billing go to [email protected].

Licence

MIT, see LICENSE. The Inclusify name and logo are trademarks of Magebit.

Source: README.md at commit d503f27

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.