"Introduction to Selenium for Browsing Automation" matching MCP servers:

Automatically fixes broken Selenium test locators when UI changes occur, reducing test maintenance overhead.

Records browser interactions (clicks, DOM mutations, console logs, JS errors) via Chrome DevTools Protocol while you manually navigate, and provides tools to retrieve and analyze recordings for test generation.

Enables Claude to read, analyze, optimize, and execute IP-Symcon PHP scripts via JSON-RPC API, turning automation development into a dialogue.

Enables AI agents to operate the Unreal Editor via MCP: reading, creating, and editing blueprints at the node level, authoring materials and UMG widgets, auditing projects, and verifying runtime behavior in PIE with read-back checks.

Enables MCP clients to call VCF Automation 9 REST operations as individual tools across 16 services, including deployments, catalog items, blueprints, policies, and IaaS resources. It also supports service-account setup, automatic token refresh, read-only filtering, and selective service loading.

Lets an LLM like Claude inspect and control an automation job queue — list jobs, check status, trigger new runs, retry failures, and pull queue-wide stats through natural language.

Converts AI Skills (following Claude Skills format) into MCP server resources, enabling LLM applications to discover, access, and utilize self-contained skill directories through the Model Context Protocol. Provides tools to list available skills, retrieve skill details and content, and read supporting files with security protections.

Enables MCP clients to turn Make blueprints and Zapier exports into n8n workflow files, with a per-step report of what converted, what to review, and what must be finished by hand. Also lists zaps, explains how individual steps are handled, checks workflow files for broken links or placeholders, and can upload the result to an n8n instance as an inactive workflow.

MCP server for AI agents to send notifications, copy to clipboard, request confirmations, and collect text input from users across their devices.

Gives AI assistants structured access to a test automation stack so they can run suites, inspect failure details and captured output, look up test data, and file Jira bugs (or drafts) only for confirmed defects. It works with any framework that emits JUnit XML, letting assistants triage flaky, environment, and test-data issues alongside real product defects.

Routes one brief to the right image model across 60+ (gpt-image-1.5, Ideogram 3, Recraft V4, Flux), validates the output, and fans out to iOS/Android/PWA/favicon/visionOS/Flutter bundles. Works without an API key via Pollinations, HF Inference, Stable Horde, or host-LLM inline SVG.

Enables MCP clients to run read-only static audits on supplied n8n, Dify, Trigger.dev, Activepieces, and OpenAPI exports, and to screen HTTPS URLs for unsafe schemes, returning structured findings and limitations.

Enables users to turn any API's documentation into a tested MCP server whose tools expose the API's own operations, with linting, contract tests, and live verification. It accepts OpenAPI/Swagger, Postman, RAML, WSDL, GraphQL, RSS, and HTML docs.

Enterprise web automation testing MCP server that controls local Chrome via Playwright CDP, providing tools for page element analysis, interaction, dynamic layer exploration, VTable scene graph, test recording, and Shadcn-style Excel export.

Enables turning requirements documents into RFCs, functional test scenarios, and a traceability matrix, with tools to parse, diff, and verify coverage.

Enables coverage-driven test generation for RHDH plugin forests by analyzing git diffs and coverage reports, recommending the cheapest test layer, and emitting actionable test briefs, including Playwright MCP prompts for UI gaps.

Enables checking build status, starting/canceling builds, and managing Unity Cloud Build targets directly from Claude Code.

Processes test scenarios from user prompts to generate complete WDIO test suites with intelligent file management that analyzes existing files to determine whether to update them or create new ones.

A Model Context Protocol server that converts Markdown content to HTML format.

Enables automation of browser tasks using Playwright by interacting via Claude Desktop for executing user-defined prompts and operations.

MCP server for integrating coding agents (Claude Code CLI, etc.) with the GIMS Automation system. Enables development of automation scripts, data source types, activator types, and Git synchronization.

Enables an MCP-compatible AI client to author Blender Python, run Blender, import the resulting asset into Unity with materials and a prefab, place it in the active scene, verify the import, and revise the same asset using stable IDs.

Enables AI assistants to query PostgreSQL, MySQL, SQL Server, Oracle, and MongoDB databases through MCP with read-only, audited access.

A Model Context Protocol server that enables AI assistants to interact with iOS simulators, perform accessibility testing, manage apps, and automate complex iOS workflows.

Generates standalone, human-readable MCP servers from RAML 1.0 or OpenAPI 3.x specs, exposing one tool per resource and method that makes real HTTP calls. It understands Mule/Anypoint auth patterns such as Client ID enforcement and OAuth2, wiring the expected credentials from environment variables at call time.

Turns any OpenAPI REST or GraphQL API into an MCP server, allowing AI assistants like Claude to interact with APIs without writing code.

Deterministic Markdown-to-Word (.docx) publishing compiler with native OMML equations, three-line tables, CSL citations, and quality gates for AI agents.

A sophisticated server that enables AI assistants to automatically analyze codebases and generate comprehensive, professional documentation.

Enables existing Express routers to be exposed as MCP tools, dispatching tool calls through the Express middleware stack in-process without a network hop.

Enables AI agents to programmatically control and automate VSCode by interacting with its UI, executing commands, and inspecting the DOM structure. It supports advanced workflows like UI testing, extension development, and debugging through a standalone VSCode instance.

Auto-generates MCP tools from your OpenAPI spec, allowing natural language interaction with any API via configurable headers and serverless deployment.

A bridge that enables any LLM to access and interact with documented REST APIs through the Model Context Protocol (MCP).

Enables MCP clients to manage SQLite-backed TODOs and schedule durable coding-agent jobs over stdio, with persistent job memory, run history, and a read-only dashboard.

Enables an MCP client to retrieve explicitly allowlisted Markdown context, create and read local task contracts, write local handoffs, and return locally configured routing metadata without invoking a model, executing commands, or writing to the vault.

Enables AI assistants to call any SOAP/WSDL web service as MCP tools, automatically converting each WSDL operation into a callable tool with authentication and security controls.

An MCP server for controlling Siemens TIA Portal, enabling AI agents to connect, read PLC tags, list blocks, inspect project structure, and compile projects. This community edition provides 5 read-only tools under the MIT license.

Enables users to record, review, verify, and expose permitted browser workflows as callable MCP tools with typed inputs, isolated Chromium verification, and approval-gated writes.

A minimal MCP server that auto-generates tools from your OpenAPI spec, optimized for Vercel.

A standalone proxy that transforms any OpenAPI or Swagger-described REST API into an MCP server by mapping API operations to executable MCP tools. It enables AI clients to interact with existing web services through automated HTTP requests based on their official documentation.

Turns any OpenAPI/Swagger or REST API into callable MCP tools for Claude, ChatGPT, Copilot, and Cursor, with secure authentication and role-based access control.