Skip to main content
Glama
vltansky

e11y-docs-mcp

by vltansky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to e11y-docs-mcp

No user-submitted related servers found.

    Related Servers

    • a11y-mcp-server

      shawnmcb
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for accessibility auditing that provides WCAG 2.2 criteria lookup, HTML remediation guidance, and automated documentation generation for UI components. It enables users to analyze code snippets for issues and generate professional accessibility audit reports.
      140 npm
      MIT

    • mcp-docs

      pgupta1795
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for documentation search that automatically indexes web documentation sites and provides semantic, full-text, or hybrid search capabilities.
      2 npm
      MIT

    • guia-wcag-mcp

      smkbarbosa
      A
      license
      A
      quality
      B
      maintenance
      A local MCP server that exposes a web accessibility knowledge base with WCAG 2.2 criteria and ABNT NBR 17225 correlations, enabling AI agents to retrieve criterion details, search by keyword, and generate manual test routines.
      3
      1
      AGPL 3.0

    • w3c-mcp

      shuji-bonji
      A
      license
      A
      quality
      B
      maintenance
      MCP Server for accessing W3C/WHATWG/IETF web specifications. Provides AI assistants with access to official web standards data including specifications, WebIDL definitions, CSS properties, and HTML elements.
      11
      363 npm
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct role: search, fetch, and list. Search finds articles by query, fetch retrieves full content by path, and list provides an overview. No overlap in their primary functions.

    Naming Consistency5/5

    All tool names follow the verb_noun pattern with the same resource: search/fetch/list + accessibility_articles. The naming is uniform and predictable.

    Tool Count5/5

    Three tools is well-scoped for a documentation repository. The count covers the essential discover and retrieve actions without unnecessary bloat.

    Completeness4/5

    The set covers the core read-only workflow: discovering articles (list/search) and retrieving content (fetch). There is no update/create/delete, which is appropriate for a docs server, but a direct get-by-ID could be a minor addition.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources