accessiBe

accessFlow MCP Server

The accessFlow Model Context Protocol server connects AI clients such as GitHub Copilot and Cursor directly to accessFlow accessibility data. It exposes three tools — getMostUrgentIssues, getIssueRemediation and resolveIssue — over both a local stdio transport (npx accessflow-mcp-server, configured with API_KEY and DOMAIN) and a hosted remote HTTP transport at https://flow-mcp.accessibe.com/mcp authenticated with a bearer AI MCP token plus an X-Domain header. It works against both accessFlow platform audits and SDK-based audits selected via the auditSource parameter.

GitHub

Documentation

📖
Documentation
https://accessibe.com/blog/knowledgebase/accessflows-sdk-and-mcp

Other Resources

🔗
MCPServer
https://raw.githubusercontent.com/api-evangelist/accessibe/refs/heads/main/mcp/accessibe-mcp.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/accessflow-mcp"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑ 
aid: accessibe:accessflow-mcp
name: accessFlow MCP Server
description: The accessFlow Model Context Protocol server connects AI clients such as GitHub Copilot and
  Cursor directly to accessFlow accessibility data. It exposes three tools — getMostUrgentIssues, getIssueRemediation
  and resolveIssue — over both a local stdio transport (npx accessflow-mcp-server, configured with API_KEY
  and DOMAIN) and a hosted remote HTTP transport at https://flow-mcp.accessibe.com/mcp authenticated with
  a bearer AI MCP token plus an X-Domain header. It works against both accessFlow platform audits and
  SDK-based audits selected via the auditSource parameter.
humanURL: https://www.npmjs.com/package/accessflow-mcp-server
baseURL: https://flow-mcp.accessibe.com/mcp
tags:
- MCP
- Accessibility
- Agents
- Remediation
properties:
- type: MCPServer
  url: mcp/accessibe-mcp.yml
- type: Documentation
  url: https://accessibe.com/blog/knowledgebase/accessflows-sdk-and-mcp