democratize-quality-mcp-server

uppadhyayraj/democratize-quality-mcp-server

3.2

If you are the rightful owner of democratize-quality-mcp-server and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

The Democratize Quality MCP Server is a comprehensive Model Context Protocol server designed to enhance API testing capabilities, ensuring high-quality API performance and reliability.

Tools
3
Resources
0
Prompts
0

๐ŸŽฏ Democratize Quality MCP Server

A comprehensive Model Context Protocol (MCP) server that democratizes quality through comprehensive API testing capabilities.

๐Ÿ“‹ Overview

This MCP server offers 3 powerful API testing tools for comprehensive API quality assurance:

๐Ÿ”— API Testing Tools

  • api_request: HTTP requests with validation and session management
  • api_session_status: Query API test session status and logs
  • api_session_report: Generate comprehensive HTML test reports

Key Features:

  • โœ… Enhanced Validation: Shows "expected vs actual" values in validation failures
  • ๐Ÿ”— Request Chaining: Use response data in subsequent requests
  • ๐Ÿ“Š Session Management: Track API test sequences across multiple requests
  • ๐Ÿ“ˆ HTML Reports: Beautiful, interactive test reports with detailed validation results
  • ๐ŸŽฏ Comprehensive Testing: Support for all HTTP methods with advanced validation options

๏ฟฝ๏ธ Installation & Setup

Prerequisites

  • Node.js 14+
  • MCP-compatible client (Claude Desktop, VS Code, etc.)

Quick Start

Option 1: Use with npx (Recommended)

# Run directly without installation
npx @democratize-quality/mcp-server --help

# Use in Claude Desktop (see integration section below)

Option 2: Global Installation

# Install globally 
npm install -g @democratize-quality/mcp-server

# Then run anywhere
democratize-quality-mcp --help
dq-mcp-server --help

Option 3: Local Development

# Clone and install dependencies
git clone https://github.com/democratize-quality/mcp-server.git
cd mcp-server
npm install

# Test the server
npm test

# Start the server (API-only mode by default)
npm start

๐Ÿ”Œ Integration Methods

Claude Desktop Integration (Recommended)

Add to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "democratize-quality": {
      "command": "npx",
      "args": ["@democratize-quality/mcp-server"],
      "env": {
        "NODE_ENV": "production"
      }
    }
  }
}

Note: The server runs in api-only mode by default, providing secure and lightweight API testing capabilities.

Alternative Integration Methods

Global Installation:

npm install -g @democratize-quality/mcp-server

Then configure Claude Desktop:

{
  "mcpServers": {
    "democratize-quality": {
      "command": "democratize-quality-mcp"
    }
  }
}

MCP Inspector (Development/Testing):

npx @modelcontextprotocol/inspector npx @democratize-quality/mcp-server

Direct Usage:

# Run the server directly
npx @democratize-quality/mcp-server

# Or if installed globally
democratize-quality-mcp

๐Ÿ“š Usage Examples

Basic API Testing

// Single API request with validation
await tools.api_request({
  method: "GET", 
  url: "https://jsonplaceholder.typicode.com/users/1",
  expect: { 
    status: 200,
    contentType: "application/json"
  }
})

Advanced API Testing with Session Management

// 1. Start a test session
await tools.api_request({
  sessionId: "user-workflow-test",
  method: "POST", 
  url: "https://jsonplaceholder.typicode.com/users",
  data: {
    name: "John Doe",
    email: "john@example.com"
  },
  expect: { status: 201 }
})

// 2. Follow up request in same session
await tools.api_request({
  sessionId: "user-workflow-test",
  method: "GET",
  url: "https://jsonplaceholder.typicode.com/users/1",
  expect: { 
    status: 200,
    body: { name: "John Doe" }
  }
})

// 3. Generate comprehensive HTML report
await tools.api_session_report({
  sessionId: "user-workflow-test",
  outputPath: "user_workflow_test_report.html"
})

Request Chaining Example

// Chain requests using response data
await tools.api_request({
  sessionId: "chained-test",
  chain: [
    {
      name: "create_user",
      method: "POST",
      url: "https://jsonplaceholder.typicode.com/users",
      data: { name: "Jane Doe", email: "jane@example.com" },
      expect: { status: 201 },
      extract: { userId: "id" }
    },
    {
      name: "get_user",
      method: "GET", 
      url: "https://jsonplaceholder.typicode.com/users/{{ create_user.userId }}",
      expect: { 
        status: 200,
        body: { name: "Jane Doe" }
      }
    }
  ]
})

๐Ÿ“– For comprehensive API testing examples and advanced usage patterns, see:

โš™๏ธ Configuration

Environment Settings

The server runs in API-only mode by default for secure, lightweight deployments focused on API testing.

NODE_ENV=production                    # Default: API-only mode
OUTPUT_DIR=./output                   # Output directory for reports
MCP_FEATURES_ENABLEDEBUGMODE=true     # Enable debug logging

Command Line Options

npx @democratize-quality/mcp-server [options]

Options:
  --help, -h                Show help
  --version, -v             Show version
  --debug                   Enable debug mode
  --port <number>           Set server port

Configuration Examples

Basic Claude Desktop Configuration
{
  "mcpServers": {
    "democratize-quality": {
      "command": "npx",
      "args": ["@democratize-quality/mcp-server"],
      "env": {
        "OUTPUT_DIR": "~/api-test-reports"
      }
    }
  }
}
Debug Mode Configuration
{
  "mcpServers": {
    "democratize-quality": {
      "command": "npx",
      "args": ["@democratize-quality/mcp-server", "--debug"],
      "env": {
        "MCP_FEATURES_ENABLEDEBUGMODE": "true"
      }
    }
  }
}

Output Directory Behavior

  • VS Code/Local: Uses ./output in your project directory
  • Claude Desktop: Uses ~/.mcp-browser-control (in your home directory)
  • Custom: Set OUTPUT_DIR environment variable to specify location

Note: API test reports and session data will be saved to the configured output directory.

๐Ÿ”ง Troubleshooting

Common Issues

1. "No such file or directory: mkdir /mcp-output"

  • This happens when Claude Desktop runs the server with restricted permissions
  • The server automatically creates ~/.mcp-browser-control in your home directory
  • API test reports will be saved there instead of your project folder

2. Output files not appearing in expected location

  • Check the actual output directory: ~/.mcp-browser-control/
  • You can set a custom location with: OUTPUT_DIR=/your/custom/path

3. Server not starting in Claude Desktop

  • Verify the npx package is published: npx @democratize-quality/mcp-server --help
  • Check Claude Desktop logs for detailed error messages
  • Try running directly in terminal first to test functionality

4. API validation failures not showing details

  • The enhanced validation feature shows "expected vs actual" values
  • Check the generated HTML reports for detailed comparison views
  • Enable debug mode for more detailed logging

Debug Mode

# Enable debug output with CLI tool
npx @democratize-quality/mcp-server --debug

# Or via environment variable
MCP_FEATURES_ENABLEDEBUGMODE=true node mcpServer.js

Logging Levels:

  • Production Mode: Shows only essential startup messages and errors
  • Debug Mode: Shows detailed API request/response logs and validation details

๐Ÿ” Advanced API Testing Features

  • ๐Ÿ“Š Session Management: Track API test sequences across multiple requests
  • ๐Ÿ”— Request Chaining: Use response data from one request in subsequent requests
  • โœ… Enhanced Validation: Shows "expected vs actual" values when validation fails
  • ๐Ÿ“ˆ Interactive Reports: Beautiful HTML test reports with detailed validation results
  • ๐ŸŽฏ Comprehensive Testing: Support for all HTTP methods (GET, POST, PUT, DELETE, PATCH, etc.)
  • ๐Ÿ”„ Response Extraction: Extract and reuse data from API responses
  • ๐Ÿ“ Detailed Logging: Complete request/response logging for debugging

๐Ÿ“„ License

ISC License

Ready to democratize quality through comprehensive API testing with MCP! ๐ŸŽฏ

๐Ÿ“š Documentation

  • - Quick start guide
  • - Complete tool documentation
  • - Comprehensive API testing examples and patterns
  • - Extending the server
  • - Advanced configuration
  • - Real-world usage examples

๐Ÿ—๏ธ Architecture

src/
โ”œโ”€โ”€ tools/api/      # API testing tools
โ”œโ”€โ”€ config/         # Configuration management
โ””โ”€โ”€ utils/          # Utility functions

Key Features

  • Automatic Tool Discovery: API tools are automatically loaded and registered
  • Configuration System: Environment-based configuration with sensible defaults
  • Error Handling: Comprehensive error handling and validation with detailed reporting
  • Session Management: Track and manage API test sessions

๐Ÿ”ง Development

Adding New API Tools

  1. Create tool file in src/tools/api/
  2. Extend ToolBase class
  3. Define tool schema and implementation
  4. Tools are automatically discovered!

Example API Tool

class MyApiTool extends ToolBase {
  static definition = {
    name: "my_api_tool",
    description: "Performs API testing operations",
    input_schema: { /* JSON schema */ },
    output_schema: { /* JSON schema */ }
  };

  async execute(parameters) {
    // API tool implementation
    return { success: true, data: responseData };
  }
}

๐Ÿงช Testing

# Run tests
npm test

# Run with coverage
npm run test:coverage

๏ฟฝ Security Considerations

Default Security Posture

  • API-Only Mode: Enabled by default for secure, lightweight deployments
  • HTTP Requests: All API requests are performed using standard HTTP libraries
  • No File System Access: API tools don't access local file system (except for report generation)
  • No Browser Automation: No browser processes are launched in API-only mode

Production Deployment Recommendations

{
  "mcpServers": {
    "democratize-quality": {
      "command": "npx",
      "args": ["@democratize-quality/mcp-server"],
      "env": {
        "NODE_ENV": "production",
        "OUTPUT_DIR": "~/api-test-reports"
      }
    }
  }
}

Security Levels

  • ๐ŸŸข Low Risk: API Tools - HTTP requests with validation and reporting

Best Practices

  1. Secure Output Directory: Ensure output directories have appropriate permissions
  2. Regular Updates: Keep the package updated for security patches
  3. Environment Separation: Use different configurations for development vs production
  4. Monitoring: Enable debug mode during initial deployment to monitor API usage

๏ฟฝ๐Ÿ“„ License

[License Type] - see file for details

๐Ÿค Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Add your changes with tests
  4. Update documentation
  5. Submit a pull request

๐Ÿ“ž Support

  • - Bug reports and feature requests
  • - Questions and community support
  • - Comprehensive guides and references

Generated automatically from tool definitions and configuration