"Creating a Custom Local Knowledge Base" matching MCP servers:

MCP server enabling Claude Code to capture screenshots of Windows applications through WSL2, allowing AI to diagnose UI errors and verify layouts.

A validation layer for AI coding assistants that enforces explicit LLM evaluations on plans, code diffs, and tests to ensure safer and higher-quality code.

Enables AI agents to verify Ceph CLI commands, config parameters, and review test scripts using a pre-generated knowledge base.

Enables testing of secure MCP connections with custom CA certificates and verified TLS.

Exposes a version-controlled knowledge base as MCP tools so agents can read merged identity/state summaries and next recommended actions at runtime, plus run deterministic schema validation and cross-reference link checks. This lets agents fetch live state and verify integrity via self-describing calls instead of re-reading raw files.

Guarded, profile-driven Charles Proxy automation for macOS and Android testing. Uses immutable TOML profiles and explicit plan/apply confirmation.

This MCP server builds a local flakiness knowledge graph from Playwright test run history and enables AI agents to query flaky tests, failure patterns, trends, and correlated git commits, helping diagnose test reliability without manual analysis.

A local MCP server that connects Claude Desktop, Claude Code, and Claude Chat to your Azure DevOps organization, enabling querying work items, reviewing pull requests, triggering pipelines, searching code, managing test plans, and updating wikis using plain language.

MCP-first A/B testing server that enables agents to manage experiments (create, update traffic splits, read results, apply winning variants) from tools like Claude Code, with self-hosted Cloudflare backend.

A multi-language testing automation server that enables AI assistants to discover, plan, and execute tests across six major programming languages. It provides comprehensive tools for repository scanning, automated test execution, and detailed coverage reporting.

A local MCP server that lets Claude Code and Codex delegate repository exploration and test proposals to a remote LM Studio model, while enforcing security boundaries by keeping all repository access read-only and never applying patches or running commands remotely.

Enables measuring DOM elements and capturing screenshots in a real local Chrome browser over the DevTools Protocol, with in-page login so httpOnly cookies apply and overlay-masking before capture. It removes common Chrome automation traps such as sandbox kills, WebSocket origin rejection, and Retina pixel scaling, with no npm or Python dependencies beyond the MCP SDK.

A local MCP server that provides adversarial code review by having one frontier agent (Claude Code or Codex) critique code changes using the other agent (Codex or Claude Code) with full repository access, enabling a genuine second opinion on code and plans.

Enables authenticated clients to retrieve problem information and optimization hints, manage source revisions and custom data, and submit or query Ascend C/NPU evaluation tasks.

Provides a testable gateway path for running a local MCP-style server in hosted-like conditions, with tenant-isolated reads, approval-denied writes, deterministic failures, and smoke-test verification.

Extracts and analyzes key frames from Loom videos or local video files for debugging purposes. Automatically detects scene changes and provides visual context for troubleshooting issues.

Exposes repository reconnaissance tools — file listing and verbatim reading, regex search, dependency-tree parsing across Python/Node/Rust/Go, and test-coverage ingestion — so agents can gather line-numbered evidence from real source files. This lets an audit pipeline physically re-verify every claim and drop findings that cannot be located in the code.

Enables AI-driven management of Zephyr test assets and Jira integrations through natural language, including creating test cases, steps, cycles, and linking tests to issues.

A lightweight MCP server that simulates financial data interactions with dummy authentication and static JSON datasets for testing financial applications.

Generates a pytest suite from acceptance criteria that are withheld from the coding agent, so the tests can disagree with the code. Four tools, and qikly_run never returns the criteria, which a test in the suite enforces.