Enable your code gen agents to create & run 0-config end-to-end tests against new code changes in remote browsers via the Debugg AI testing platform.
AI-driven browser automation and E2E test server implementing the Model Context Protocol (MCP), designed to help AI agents test UI changes, simulate user behavior, and analyze visual outputs of running web applications β all via natural language and CLI tools.
End to end testing used to be a nightmare. Not just to setup, but to manage over time as you made changes to your app.
Debugg AI's MCP server offers a NEW way to test, where you never have to worry about setting up playwright
, local browsers or proxies with it fully remote, managed browsers that simply connect to a server running locally or remotely via a secure tunnel
.
That means no distracting chrome pop ups as it's running tests, no managing chrome or playwright versions, and best of all - ZERO CONFIGURATION. Just grab an API key and add us to your MCP server list.
Should you want to later rerun those tests or create a suite of them to run in your CI / CD pipeline, you can see all historical test results in your dashboard - Debugg.AI App
π§ MCP Protocol Support Full MCP server implementation with CLI and tool registry support.
π§ͺ End-to-End Test Automation
Trigger UI tests based on user stories or natural language descriptions via the debugg_ai_test_page_changes
tool.
π Localhost Web App Integration
Test your running dev app on any localhost
port with simulated user flows.
π§Ύ MCP Tool Notifications Sends real-time progress updates back to clients with step descriptions and UI state goals.
π§· Screenshot Support Capture final visual state of the page for LLMs with image rendering support.
π§± Stdio Server Compatible Plug into any MCP-compatible client (like Claude Desktop, LangChain agents, etc.) via stdin/stdout.
**Task Completed**
- Duration: 86.80 seconds
- Final Result: Successfully completed the task of signing up and logging into the account with the email 'alice.wonderland1234@example.com'.
- Status: Success
Watch a more in-depth, Full Use Case Demo
npx -y @debugg-ai/debugg-ai-mcp
Use this when testing or integrating into tools like Claude Desktop or your own AI agent.
docker run -i --rm --init \
-e DEBUGGAI_API_KEY=your_api_key \
-e TEST_USERNAME_EMAIL=your_test_email \
-e TEST_USER_PASSWORD=your_password \
-e DEBUGGAI_LOCAL_PORT=3000 \
-e DEBUGGAI_LOCAL_REPO_NAME=your-org/your-repo \
-e DEBUGGAI_LOCAL_BRANCH_NAME=main \
-e DEBUGGAI_LOCAL_REPO_PATH=/app \
-e DEBUGGAI_LOCAL_FILE_PATH=/app/index.ts \
quinnosha/debugg-ai-mcp
debugg_ai_test_page_changes
Run an end-to-end test on a running web app, testing a UI feature or flow described in natural language. Allows AI agents in ANY code gen platform to quickly evaluate proposed changes and ensure new functionality works as expected.
Name | Type | Required | Description |
---|---|---|---|
description | string | β | What feature or page to test (e.g. "Signup page form") |
localPort | number | β | Port of your running app (default: 3000 ) |
repoName | string | β | GitHub repo name |
branchName | string | β | Current branch |
repoPath | string | β | Absolute path to the repo |
filePath | string | β | File to test |
{
"mcpServers": {
"debugg-ai-mcp": {
"command": "npx",
"args": ["-y", "@debugg-ai/debugg-ai-mcp"],
"env": {
"DEBUGGAI_API_KEY": "YOUR_API_KEY",
"TEST_USERNAME_EMAIL": "test@example.com",
"TEST_USER_PASSWORD": "supersecure",
"DEBUGGAI_LOCAL_PORT": 3000,
"DEBUGGAI_LOCAL_REPO_NAME": "org/project",
"DEBUGGAI_LOCAL_BRANCH_NAME": "main",
"DEBUGGAI_LOCAL_REPO_PATH": "/Users/you/project",
"DEBUGGAI_LOCAL_FILE_PATH": "/Users/you/project/index.ts"
}
}
}
}
Variable | Description | Required |
---|---|---|
DEBUGGAI_API_KEY | API key for calling DebuggAI backend | β |
TEST_USERNAME_EMAIL | Email of test user account | β |
TEST_USER_PASSWORD | Password of test user account | β |
DEBUGGAI_LOCAL_PORT | Local port your app runs on | β |
DEBUGGAI_LOCAL_REPO_NAME | GitHub repo name | β |
DEBUGGAI_LOCAL_BRANCH_NAME | Branch name | β |
DEBUGGAI_LOCAL_REPO_PATH | Local path to repo root | β |
DEBUGGAI_LOCAL_FILE_PATH | File to test | β |
# Clone the repo and install dependencies
npm install
# Copy the test config and insert your creds
cp test-config-example.json test-config.json
# Run the local node-built dist
npx @modelcontextprotocol/inspector --config test-config.json --server debugg-ai-mcp-node
# OR Run the MCP server locally from above toplevel dir.
npx @modelcontextprotocol/inspector --config debugg-ai-mcp/test-config.json --server debugg-ai-mcp
.
βββ e2e-agents/ # E2E browser test runners
βββ services/ # Client for DebuggAI API
βββ tunnels / # Secure connections to remote web browsers
βββ index.ts # Main MCP server entry
βββ Dockerfile # Docker build config
βββ README.md
For bugs, ideas, or integration help, open an issue or contact the DebuggAI team directly.
MIT License Β© 2025 DebuggAI
Fetch comprehensive information about CRAN packages, including READMEs, metadata, and search functionality.
Seamlessly bring real-time production contextβlogs, metrics, and tracesβinto your local environment to auto-fix code faster.
Search dashboards, investigate incidents and query datasources in your Grafana instance
Provides call graph analysis for LLMs using the nuanced library.
A powerful and flexible MCP server designed to enhance the development experience with Shadcn UI components, providing tools for component management, documentation, and installation.
An MCP server for managing API test data and resources.
A self-hostable middleware to manage all your MCPs through a GUI and a local proxy, supporting multiple clients and workspaces.
Enhances LLM reasoning by transforming prompts into Chain of Draft or Chain of Thought formats, improving quality and reducing token usage. Requires API keys for external LLM services.
A platform for creating and managing AI agents with specific personalities and simulating their responses. Requires a DeepSeek API key.
A starter template for building Model Context Protocol (MCP) servers, designed for UI libraries and component registries.