{
  "markdown": "# Inclusify for AI agents\n\nConnect your AI assistant to [Inclusify](https://inclusifyapp.com) and ask about the\naccessibility of your own websites: what is failing, where it lives in your source, and whether\nthe fix you just wrote actually fixes it.\n\nThis repository is the install surface — the plugin manifests, the registry entry and one skill.\nThe MCP server itself runs at `https://app.inclusifyapp.com/api/mcp/customer` and is not open\nsource.\n\n## Install\n\n**Cursor** — [Add to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=inclusify&config=eyJ1cmwiOiJodHRwczovL2FwcC5pbmNsdXNpZnlhcHAuY29tL2FwaS9tY3AvY3VzdG9tZXIifQ==),\nor install the Inclusify plugin from the Cursor marketplace.\n\n**Claude Code**\n\n```bash\nclaude mcp add --transport http inclusify https://app.inclusifyapp.com/api/mcp/customer\n```\n\nOr install this repository as a plugin marketplace, which brings the skill with it:\n\n```bash\n/plugin marketplace add magebitcom/inclusify-plugin\n```\n\n**Gemini CLI**\n\n```bash\ngemini extensions install https://github.com/magebitcom/inclusify-plugin\n```\n\n**Everything else** — Claude web and desktop, ChatGPT, VS Code, Windsurf, Continue and the rest\nare one URL each. The exact file and field name per client are documented at\n[inclusifyapp.com/docs/integrations/mcp](https://inclusifyapp.com/docs/integrations/mcp).\n\n## First connection\n\nYour client registers itself and opens a browser tab. You sign in to Inclusify or create an\naccount; if you have no organisation yet you are asked to name one, which is your workspace.\nA consent screen shows what the client gets — your basic profile and email address, nothing\nelse. Nothing to paste, and no key to manage.\n\nInstalling this plugin is optional. If your assistant cannot install anything, the same tools\nanswer over plain HTTP with a key we email you, and an assistant can create the account for you\nwithout you opening a browser at all. See\n[inclusifyapp.com/docs/agents](https://inclusifyapp.com/docs/agents).\n\n## What you need for it to say anything useful\n\n- The website has to be in your Inclusify account. Asking about a domain you have not added\n  returns \"no website by that name here\" rather than scanning a stranger's site. An assistant\n  can add one for you.\n- Plans gate the answers, not the connection. Finding out what the account holds, adding a\n  website, and reading where a site stands, what plan it is on and whether the widget is live\n  work on every plan including Free — the same things the panel already lets a Free customer do.\n  What is actually wrong with a site, every check that loads a page, and the full-site crawl\n  need Pro. The account-wide rollups need Enterprise.\n- A site that has never been scanned has no score yet, and the tools say so rather than\n  reporting a good one.\n\n## What it can do\n\nWhere a site stands, the fix list with the strings to grep for in your own templates, live\nkeyboard and screen-reader checks, rendering under forced colours and 400% zoom, alt-text\nreview, checking a fix before you deploy it, a pass/fail gate for CI, and running the product\nitself: widget on or off, appearance and profiles, publishing the accessibility statement,\nmonitoring alerts, and filing findings into Jira or Slack.\n\nAnything consequential asks first. Those tools return a plain-language description of exactly\nwhat would change plus a single-use token, and change nothing until you call again with it. The\naccount owner then gets an email with an undo link.\n\nNothing here can move money: no tool changes a plan, sets payout details or charges anything.\nUpgrading hands you a link to do it yourself.\n\nThe current tool list, what each one deliberately does not know, and the allowances that bound\nthe live checks are documented on the page linked above. It is generated from the server's own\nregistry, so it cannot drift; this README deliberately does not restate it.\n\n## The skill\n\n`skills/accessibility-fix-loop` teaches the loop that actually resolves issues rather than\nsilencing them: read the fix list, grep your source for the strings it hands you, validate the\nmarkup before deploying, then confirm against a later scan. It also tells the assistant to take\na `masked` verdict seriously — `aria-hidden`, `display: none` and swapping a button for a div\nall make a scanner go quiet while leaving the barrier in place.\n\n## Contributing\n\nIssues and pull requests on the manifests, the skill and the docs are welcome. Problems with the\nserver itself, your account or your billing go to support@inclusifyapp.com.\n\n## Licence\n\nMIT, see [LICENSE](LICENSE). The Inclusify name and logo are trademarks of Magebit.\n",
  "bytes": 4621,
  "sha": "ff384d9727efa1157ea2978453efe6e586720bd6d6fe1d61ac5b89e72752e095",
  "repo_slug": "magebitcom/inclusify-plugin",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_magebitcom_inclusify_plugin_0554be2d/readme"
}