Connect an MCP client

The hosted server speaks Streamable HTTP at https://mcp.binclusive.io/mcp. Any spec-compliant MCP client connects with two fields and no secret.

Claude Code

claude mcp add --transport http binclusive https://mcp.binclusive.io/mcp

Or commit the config with the project, as .mcp.json at the repo root:

{
  "mcpServers": {
    "binclusive": {
      "type": "http",
      "url": "https://mcp.binclusive.io/mcp"
    }
  }
}

Committing this is safe: it carries no token, no header, and no connection string. Credentials are obtained at runtime by the sign-in flow and stored by your client, not in the file.

Cursor and other clients

Take the same type: "http" + url entry into the client’s own MCP config. Clients that implement OAuth 2.1 discovery and Dynamic Client Registration need nothing else; the server advertises its authorization server through the 401 it returns to an unauthenticated request.

Sign in

There is no separate login step. On the first request your client sends without a credential, the server answers 401 with a WWW-Authenticate header; your client discovers the authorization server from it, registers itself, opens a browser, and stores the resulting token. If your client reports a connection as successful but every tool call fails, it is almost certainly not performing that discovery — see About authentication.

Use a machine credential instead

For CI and other unattended callers, present a b8e_ API key as the Bearer token instead of going through the browser flow. Mint one in the dashboard under Settings → CI access; it carries its own organization scope.

A machine credential reaches exactly one tool: create_ticket. Every other tool requires a signed-in person and refuses a machine caller with “Not authenticated” — so use this for filing findings from a pipeline, not for reading your backlog. See File a finding from a coding agent.

Add the accessibility skills

The server does not serve accessibility skill content — skills are public and static, so they ship as a Claude Code plugin:

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 the skills and the data connection; the OAuth flow fires on first real MCP use. For non-Claude harnesses (Cursor, Codex, Gemini, Copilot), pull the skill files directly:

npx skills add Binclusive/Binclusive-Accessibility-Skills --all

Why the split exists at all is covered in About what this server serves.

Confirm the connection

Ask the agent to call get_viewer. A profile with an organization back means the credential is good and the org context resolved. See the identity tools.