- 🧪 Official MCP Server for Debugg AI
🧪 Official MCP Server for Debugg AI
🧪 Official MCP Server for Debugg AI
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
🚀 Features
-
🧠 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_changestool. -
🌐 Localhost Web App Integration Test your running dev app on any
localhostport 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.
Server Config
{
"mcpServers": {
"debugg-ai-mcp": {
"command": "node",
"args": [
"dist/index.js"
],
"env": {
"DEBUGGAI_API_KEY": "your key here",
"TEST_USERNAME_EMAIL": "test email here",
"TEST_USER_PASSWORD": "test password here",
"MCP_REQUEST_TIMEOUT_RESET_ON_PROGRESS": "true",
"DEBUGGAI_LOCAL_PORT": 3000,
"DEBUGGAI_LOCAL_REPO_NAME": "your repo name here",
"DEBUGGAI_LOCAL_BRANCH_NAME": "your branch name here",
"DEBUGGAI_LOCAL_REPO_PATH": "/Users/your username here/Documents/GitHub/your repo name here",
"DEBUGGAI_LOCAL_FILE_PATH": "optional file path here"
},
"options": {}
},
"debugg-ai-mcp-live": {
"command": "npx",
"args": [
"-y",
"@debugg-ai/debugg-ai-mcp"
],
"env": {
"DEBUGGAI_API_KEY": "your key here",
"TEST_USERNAME_EMAIL": "test email here",
"TEST_USER_PASSWORD": "test password here",
"MCP_REQUEST_TIMEOUT_RESET_ON_PROGRESS": "true",
"DEBUGGAI_LOCAL_PORT": 3000,
"DEBUGGAI_LOCAL_REPO_NAME": "your repo name here",
"DEBUGGAI_LOCAL_BRANCH_NAME": "your branch name here",
"DEBUGGAI_LOCAL_REPO_PATH": "/Users/your username here/Documents/GitHub/your repo name here",
"DEBUGGAI_LOCAL_FILE_PATH": "optional file path here"
},
"options": {}
},
"debugg-ai-mcp-docker-live": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--init",
"-e",
"DEBUGGAI_API_KEY=your key here",
"-e",
"DEBUGGAI_LOCAL_PORT=3000",
"-e",
"DEBUGGAI_LOCAL_REPO_NAME=your repo name here",
"-e",
"DEBUGGAI_LOCAL_BRANCH_NAME=your branch name here",
"-e",
"DEBUGGAI_LOCAL_REPO_PATH=/Users/your username here/Documents/GitHub/your repo name here",
"quinnosha/debugg-ai-mcp"
],
"env": {
"DEBUGGAI_API_KEY": "your key here",
"TEST_USERNAME_EMAIL": "test email here",
"TEST_USER_PASSWORD": "test password here",
"MCP_REQUEST_TIMEOUT_RESET_ON_PROGRESS": "true",
"DEBUGGAI_LOCAL_PORT": 3000,
"DEBUGGAI_LOCAL_REPO_NAME": "your repo name here",
"DEBUGGAI_LOCAL_BRANCH_NAME": "your branch name here",
"DEBUGGAI_LOCAL_REPO_PATH": "/Users/your username here/Documents/GitHub/your repo name here",
"DEBUGGAI_LOCAL_FILE_PATH": "optional file path here"
}
}
}
}