Accessibility your AI agent can run.MCP server or plain HTTP.
Ask Claude, Cursor, Gemini or ChatGPT to scan your site, read the WCAG findings and set the account up. Nothing to install.
Can an assistant set this up for me?
Yes. Three messages, no browser, no form to fill in. An assistant that hits a sign-up form has to hand the job back to you; this one is an endpoint, so it does not have to.
Read the endpoint reference1. Ask for it
Tell the assistant to set Inclusify up for your domain. Nothing exists yet.
2. Read back the code
Six digits arrive in your inbox. You read them back in the same chat.
3. You have an account
Workspace, website and free plan created, sign-in link in your inbox.
Connect it to your client.
One remote server, nothing to download. It signs you in with the Inclusify account you already have.
One click. Cursor opens, asks you to confirm, and the tools are there.
Devin Desktop, formerly Windsurf, and anything else that speaks streamable HTTP take the same endpoint. Published on the official MCP registry as com.inclusifyapp/inclusify.
36 tools, not one scanner.
32 of them work on one website and 4 across the whole account. Most of them only read.
Which ones your account can call depends on its plan, exactly as in the dashboard.
Understand a site
Where it stands, what changed, what to do next.
site_overview, compliance_status, next_steps, score_history, crawl_summary
Find what is wrong
Failing rules with the markup and selector, plus alt text and content clarity.
list_violations, list_alt_findings, list_content_findings, page_history
Check the live page
A real browser: tab through it, read it aloud, zoom it, re-check a fix.
keyboard_walk, screen_reader_transcript, simulate_condition, check_page_alt_text, validate_fix
Change settings
The widget, monitoring, the published statement, where findings get posted.
set_widget_enabled, set_widget_appearance, set_monitoring_settings, set_statement_published, set_jira_project, set_slack_channel
Set it up and ship it
Add a site, watch pages, run a crawl, get a pass or fail for CI.
add_website, add_monitored_pages, start_crawl, get_job, ci_gate
No MCP client? It still works.
MCP is one door, not the only one. Every tool is also a plain HTTP call, reachable from an assistant that has nothing but web access.
The plain HTTP reference- /api/agent/scan
- Start a free scan of any site and have the report emailed. No account needed.
- /api/agent/register
- Create the account and the website, anchored on a code emailed to the owner.
- /api/v1
- Every tool, its input schema and whether it writes. Readable without a credential.
- /llms.txt
- The whole surface written for an assistant to act on, in one plain-text file.
What it will not do.
Handing an agent a credential to your compliance tooling is a real decision. Here is the shape of it.
It never touches your site
No tool edits your pages, your theme or your catalogue. They read accessibility data and change Inclusify's own settings for that website.
Most of the writes stop to ask
Twelve of the tools write anything at all. Eight of those show you a preview first and refuse to act without an explicit confirmation.
You get told about the quiet ones
Turning the widget off, or quietening Slack alerts, emails the account owner a link that undoes it.
Signing up needs your mailbox
An assistant can create the account, but only after you read back a code we emailed you. Nobody else's agent can enrol your domain.
Questions, answered.
The ones people and their assistants actually ask us.
Everything Inclusify does with AIYes. It is a remote streamable-HTTP server at https://app.inclusifyapp.com/api/mcp/customer, published on the official MCP registry as com.inclusifyapp/inclusify. Nothing runs on your machine, there is no package to install, and it authenticates with OAuth 2.1 through your normal Inclusify sign-in.
Yes. Any assistant that can fetch a URL can do it, with no connector and no install. It calls the signup endpoint, we email you a six-digit code, you read the code back in the same conversation, and the account and website are created. The code is what proves the mailbox is yours, so nothing is created before you supply it.
Yes, two doors onto the same tools. Everything the MCP server exposes is also reachable as plain HTTP under /api/v1 with a bearer credential, and the signup, sign-in and free-scan calls under /api/agent need no credential at all. GET /api/v1 lists every tool with its input schema, unauthenticated, so an agent can discover the surface before it holds anything.
Claude web, desktop and Claude Code, Cursor, ChatGPT, OpenAI Codex, VS Code, Google Antigravity, Devin Desktop (formerly Windsurf), and anything else that speaks MCP over streamable HTTP. Two names have moved recently: Gemini CLI reached end of life in June 2026 and Antigravity is Google's path now, though Gemini Code Assist Standard and Enterprise keep it. Anything without MCP at all uses the plain HTTP endpoints instead, which is every assistant with web access.
No. The MCP server is remote, so connecting it is a URL rather than a download, and the HTTP endpoints need nothing at all. There is no CLI, no npm package and no local process.
Most of the tools only read. Of the twelve that write, eight will not act until you confirm a preview, and the confirmation is bound to the exact arguments, to you, and to a ten-minute window. Disabling the widget or quietening alerts also emails the account owner an undo link. No tool can modify your website itself.
A static scan tells you what a rule engine can see in the markup. These tools drive a real browser: tab through the page and report where focus is lost, read it back the way a screen reader announces it, render it at 400 percent zoom or in a simulated condition, and re-check a fix against the live page before you ship it. History, monitoring and the compliance record then sit alongside the findings instead of in a separate tool.
The free plan already lets an assistant create the account, add domains, read a site overview and turn the widget on or off. Scheduled monitoring and score history need Starter. The findings themselves, the live browser checks and fix validation need Pro. Account-wide rollups and the CI gate need Enterprise.
Yes, and it has its own server at /api/mcp/partner with its own tools for leads, commissions and onboarding, kept separate so an organisation that is both a customer and a partner never gets one merged tool list. Enrolling a partner works over plain HTTP too, with the same emailed code.
Make your website accessible today.
Accessibility opens your site to millions more customers - and protects your business while you do it.
- Scans WCAG
- Scans ADA
- Report in 1 minute