Add uuv mcp to official server

[luifr10]

Description

Motivation and Context

The UUV MCP (Model Context Protocol) was designed to make accessibility-focused end-to-end testing more efficient, more consistent, and more accessible to both humans and AI agents.

Writing high-quality E2E tests that respect accessibility standards (ARIA roles, accessible names, semantic structure) is often complex, repetitive, and error-prone. It requires deep knowledge of both testing frameworks and accessibility specifications. The UUV MCP addresses this challenge by exposing a structured and intelligent interface that automates and standardizes the generation of UUV test scenarios in Gherkin format.

By providing dedicated tools such as available_sentences, generate_role_and_name, and generate_table, the MCP enables:

• Automatic generation of reliable and compliant UUV test scenarios
• Consistent use of accessibility roles and semantic naming
• Simplified interaction for AI coding agents and non-expert users
• Reduction of manual effort and human errors in test writing
• Faster test creation without sacrificing readability or correctness

The UUV MCP Server acts as a bridge between human intent and executable accessibility tests, allowing users to describe what they want to validate (role, name, table structure) while the system produces structured, readable, and ready-to-run test scenarios.

In short, the UUV MCP exists to industrialize the creation of accessible E2E tests, ensuring that automation remains human-readable, accessibility-compliant, and seamlessly integrated into modern development and AI-driven workflows.

Many other tools are currently under development.

How Has This Been Tested?

Tested with:

• Claude Desktop
• MCP Inspector
• Opencode

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

Additional context