Skip to main content
Glama
Sign In
deenesjakoruzh
brd-enhancer-mcp

brd-enhancer-mcp

by arushsingh17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

brd-enhancer-mcp

A package that ships three MCP servers for an AI-assisted SDLC workflow:

Server

Executable

Purpose

enhance-prompt

prompt-enhancer-mcp

Enhance dev tasks with project documentation context

test-workflow

test-workflow-mcp

Generate & submit Gherkin test cases from Confluence

pipeline-analyzer

pipeline-analyzer-mcp

Analyze Harness pipeline failures with RAG context from past incidents

Prerequisites

⚠️ Use Official Python (NOT Microsoft Store Python)

Download Python from https://www.python.org/downloads/

During installation, make sure to check:

✅ "Add Python to PATH"

Verify you have the correct Python:

where python

Output

Status

C:\Python313\python.exe

✅ Official Python — Good

C:\Users\...\WindowsApps\python.exe

❌ Microsoft Store Python — Reinstall from python.org

Related MCP server: Context7 MCP

Installation

Option A — Global Install (Recommended for most developers)

pip install git+https://github.com/arushsingh17/mcp.git

Verify installation:

pip show brd-enhancer-mcp
where brd-enhancer-mcp        # Windows
which brd-enhancer-mcp        # Mac/Linux

Option B — Virtual Environment Install

# Step 1: Create and activate a virtual environment
python -m venv venv
venv\Scripts\activate          # Windows
source venv/bin/activate       # Mac/Linux

# Step 2: Install the package
pip install git+https://github.com/arushsingh17/mcp.git

# Step 3: Get the exact executable path (needed for config)
python -c "import shutil; print(shutil.which('brd-enhancer-mcp'))"

Example output:

C:\Users\YourName\Desktop\myproject\venv\Scripts\brd-enhancer-mcp.exe

Copy this path — you will need it in the config below.

Configuration

🌍 Global Install Config

Since brd-enhancer-mcp is registered in system PATH, no file path is needed.

Claude Desktop → %APPDATA%\Claude\claude_desktop_config.json (Windows) Claude Desktop → ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) Claude Code → ~/.claude.json

{
    "mcpServers": {
        "brd-enhancer": {
            "command": "brd-enhancer-mcp",
            "env": {
                "API_KEY": "your_api_key",
                "PROJECT_ID": "your_project_id",
                "API_URL": "https://your-backend.com"
            }
        }
    }
}

📦 Virtual Environment Config

Use the full path you got from the command above.

⚠️ On Windows replace every \ with \\ in the path

{
    "mcpServers": {
        "brd-enhancer": {
            "command": "C:\\Users\\YourName\\Desktop\\myproject\\venv\\Scripts\\brd-enhancer-mcp.exe",
            "env": {
                "API_KEY": "your_api_key",
                "PROJECT_ID": "your_project_id",
                "API_URL": "https://your-backend.com"
            }
        }
    }
}

Mac/Linux venv config:

{
    "mcpServers": {
        "brd-enhancer": {
            "command": "/Users/yourname/myproject/venv/bin/brd-enhancer-mcp",
            "env": {
                "API_KEY": "your_api_key",
                "PROJECT_ID": "your_project_id",
                "API_URL": "https://your-backend.com"
            }
        }
    }
}

Environment Variables

Shared (all servers)

Variable

Required

Default

Description

API_KEY

✅ Yes

—

Your personal backend API key

PROJECT_ID

✅ Yes

—

Your project ID/GUID

API_URL

❌ No

http://localhost:8000

Backend URL

pipeline-analyzer-mcp only

Variable

Required

Default

Description

HARNESS_API_KEY

✅ Yes

—

Harness personal access token (pat.ACCOUNT.TOKEN_ID.SECRET)

HARNESS_ACCOUNT_ID

✅ Yes

—

Harness account identifier

HARNESS_PROJECT_ID

✅ Yes

—

Harness project identifier

HARNESS_ORG_ID

❌ No

default

Harness organization identifier

HARNESS_BASE_URL

❌ No

https://app.harness.io

Harness base URL (change for self-hosted)

pipeline-analyzer example config

{
    "mcpServers": {
        "pipeline-analyzer": {
            "command": "pipeline-analyzer-mcp",
            "env": {
                "API_URL": "https://your-backend.com",
                "API_KEY": "your_backend_api_key",
                "PROJECT_ID": "your_project_id",
                "HARNESS_API_KEY": "pat.ACCOUNT.TOKEN_ID.SECRET",
                "HARNESS_ACCOUNT_ID": "your_harness_account_id",
                "HARNESS_ORG_ID": "default",
                "HARNESS_PROJECT_ID": "your_harness_project_id",
                "HARNESS_BASE_URL": "https://app.harness.io"
            }
        }
    }
}

Quick Reference

Scenario

Command in config

Global install (Official Python)

"command": "brd-enhancer-mcp"

Global install (Microsoft Store Python)

Full path from where brd-enhancer-mcp

Virtual environment (any OS)

Full path from python -c "import shutil; print(shutil.which('brd-enhancer-mcp'))"

Available Tools

1 tool
enhance_taskA

Search project documentation and return an enhanced prompt with relevant context. Use this to get background info, requirements, or architecture context for a task.

This is a standalone remote lookup — it queries an API and returns results directly.

After receiving the result, display it to the user and wait for their instructions.

Args: task: The task or query to enhance project_id: Optional project ID/GUID. Defaults to PROJECT_ID env var.

Inputs: task (required), project_id. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'enhance_task' has a clearly defined and distinct purpose of searching documentation to enhance prompts with context.

    Naming Consistency5/5

    A single tool inherently exhibits perfect naming consistency, as there are no other tools to compare against. The name 'enhance_task' follows a clear verb_noun pattern that is appropriate for its function.

    Tool Count2/5

    One tool is too few for a server named 'brd-enhancer-mcp', which suggests a broader scope of enhancing tasks or documents. A single lookup tool feels thin and incomplete for what could involve multiple enhancement-related operations.

    Completeness2/5

    The tool surface is severely incomplete for an enhancement domain. While 'enhance_task' provides context lookup, there are obvious gaps such as creating, updating, or managing enhanced tasks or documents, leaving agents with limited functionality.

    Resources

    Related MCP Connectors

    Related MCP Servers

    • MCP Prompt Enhancer

      soniankur948
      A
      license
      Not graded
      quality
      D
      maintenance
      Intelligently analyzes codebases to enhance LLM prompts with relevant context, featuring adaptive context management and task detection to produce higher quality AI responses.
      2
      MIT

    • doc-bot

      afterxleep
      A
      license
      A
      quality
      C
      maintenance
      Provides AI assistants with intelligent access to project documentation and API references through smart search, contextual rules, and Docset integration. Enables AI to understand project-specific conventions, patterns, and official framework documentation without token limits.
      11
      49 npm
      6
      MIT