About what this server serves

Your coding agent needs two different things to do accessibility work well, and Binclusive ships them through two different channels. Knowing which is which saves you asking the wrong one.

Your data, through this server

The MCP server serves what only Binclusive knows about your system: your organizations, projects, pages, journeys, audits, runs, tickets, and findings. Everything it exposes is scoped to whoever signed in, and everything it writes is a real write — a ticket your agent moves is the ticket your teammate sees in the dashboard a second later, with no sync step in between.

That also means the rules are the same rules. Permissions, ticket statuses, who can delete a page: your permissions here are the permissions the dashboard enforces, so an agent signed in as you can do what you can do, and nothing more.

Accessibility knowledge, through the skills plugin

Knowing how to fix a focus trap or what a WCAG criterion demands is not your data — it is public, it is the same for everyone, and the skills that carry it bundle scripts that need to run on your machine. So they ship as a Claude Code plugin rather than as tools on this server:

claude plugin marketplace add Binclusive/Binclusive-Accessibility-Skills
claude plugin install accessibility@binclusive

The plugin also declares this MCP server, so one install wires up both. For other harnesses (Cursor, Codex, Gemini, Copilot), pull the skill files with npx skills add Binclusive/Binclusive-Accessibility-Skills --all.

The practical upshot: your agent reasons with the skills and grounds itself with the tools. It knows what a contrast failure is from the skill, and which of your pages has one from this server. If it is asking this server how to fix something, it is asking the wrong half.

One sign-in per session

You sign in once when your client connects, and that identity holds for the whole session rather than being re-checked on every call. If you have just been added to an organization and the server still does not show it, reconnect — the session predates the change.

For the sign-in itself, see About authentication.