Debugg Ai MCP logo

Debugg Ai MCP

Unclaimed

by debugg-ai

Zero-Config, Fully AI-Managed End-to-End Testing for all code gen platforms.

Install

$docker run -i --rm --init -e DEBUGGAI_API_KEY=your_api_key quinnosha/debugg-ai-mcp

Set up this server

This server needs project-specific setup. Follow the project instructions; no reusable public launch command is available yet.

Project instructions
automationbrowserend-to-end-testingweb

More in Search & Web

Browse the full directory

Unclaimed listing

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

13 of 13 tools

Documented tools (13)

From project documentation. A server handshake does not verify each tool’s description or behavior.

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about Debugg Ai MCP Server

How do I connect Debugg Ai MCP Server to Claude?
The listing records `docker run -i --rm --init -e DEBUGGAI_API_KEY=your_api_key quinnosha/debugg-ai-mcp` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Code as compatible clients.
Is Debugg Ai MCP Server free?
The listed licence is Apache-2.0. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can Debugg Ai MCP Server do?
Debugg Ai MCP Server documents 13 tools to the agent, including auth.username, check_app_in_browser, create_project. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.