BLT-MCP

An MCP (Model Context Protocol) server that provides AI agents and developers with structured access to the BLT (Bug Logging Tool) ecosystem. This server enables seamless integration with IDEs and chat interfaces to log bugs, triage issues, query data, and manage security workflows.

Overview

BLT-MCP implements the MCP standard, giving AI agents structured access to BLT through three powerful layers:

🔗 Resources (blt:// URIs)

Access BLT data through standardized URIs:

• blt://issues - All issues in the system

• blt://issues/{id} - Specific issue details

• blt://repos - Tracked repositories

• blt://repos/{id} - Specific repository details

• blt://contributors - All contributors

• blt://contributors/{id} - Specific contributor details

• blt://workflows - All workflows

• blt://workflows/{id} - Specific workflow details

• blt://leaderboards - Leaderboard rankings and statistics

• blt://rewards - Rewards and bacon points

🛠️ Tools

Perform actions on BLT:

• submit_issue - Report new bugs and vulnerabilities

• award_bacon - Award bacon points to contributors (gamification)

• update_issue_status - Change issue status (open, in_progress, resolved, closed, wont_fix)

• add_comment - Add comments to issues

💡 Prompts

AI-guided workflows for common security tasks:

• triage_vulnerability - Guide AI through vulnerability triage and severity assessment

• plan_remediation - Create comprehensive remediation plans for security issues

• review_contribution - Evaluate contributions with quality assessment and bacon point recommendations

Features

• ✅ JSON-RPC 2.0 - Standard protocol for reliable communication

• ✅ OAuth/API Key Authentication - Secure access to BLT endpoints

• ✅ Unified Interface - Single agent-friendly interface to all BLT functionality

• ✅ Autonomous Workflows - Enable AI agents to work independently

• ✅ Gamification Support - Built-in support for BLT's bacon point system

• ✅ Security-First - Designed for vulnerability management and security workflows

Installation

Prerequisites

• Node.js 18 or higher

• npm or yarn

Install Dependencies

Build

Configuration

Environment Variables

Create a .env file based on .env.example:

Configure the following variables:

MCP Client Configuration

To use this server with an MCP client (like Claude Desktop or Cline), add it to your MCP settings:

Usage

Running the Server

The server runs using stdio transport for MCP communication:

Using with AI Agents

Once configured in your MCP client, you can interact with BLT through natural language:

Example: Submitting an Issue

The AI agent will use the submit_issue tool to create the issue.

Example: Accessing Resources

The AI agent will read from blt://leaderboards to display the rankings.

Example: Using Prompts

The AI agent will use the triage_vulnerability prompt to guide the analysis.

API Reference

Resources

List All Issues

Get Specific Issue

Leaderboards

Tools

submit_issue

Submit a new issue to BLT.

Parameters:

• title (string, required) - Issue title

• description (string, required) - Detailed description

• repo_id (string, optional) - Repository ID

• severity (string, optional) - One of: low, medium, high, critical

• type (string, optional) - One of: bug, vulnerability, feature, other

Example:

award_bacon

Award bacon points to a contributor.

Parameters:

• contributor_id (string, required) - Contributor ID

• points (number, required) - Points to award

• reason (string, required) - Reason for the award

update_issue_status

Update the status of an issue.

Parameters:

• issue_id (string, required) - Issue ID

• status (string, required) - One of: open, in_progress, resolved, closed, wont_fix

• comment (string, optional) - Explanation for status change

add_comment

Add a comment to an issue.

Parameters:

• issue_id (string, required) - Issue ID

• comment (string, required) - Comment text

Prompts

triage_vulnerability

Guides AI through vulnerability triage.

Arguments:

• vulnerability_description (required) - Description of the vulnerability

• affected_component (optional) - Affected component or system

plan_remediation

Creates remediation plans for security issues.

Arguments:

• issue_id (required) - Issue ID to create plan for

• context (optional) - Additional context

review_contribution

Evaluates security contributions.

Arguments:

• contribution_id (required) - Contribution ID

• contribution_type (optional) - Type of contribution

Development

Watch Mode

For development, use watch mode to automatically rebuild on changes:

Project Structure

Security Considerations

• API Keys: Never commit API keys to version control. Use environment variables.

• Access Control: Ensure proper authentication is configured for production use.

• Rate Limiting: Be mindful of API rate limits when making requests.

• Input Validation: The server validates all inputs before sending to the BLT API.

Contributing

Contributions are welcome! Please follow these guidelines:

1. Fork the repository

2. Create a feature branch

3. Make your changes

4. Submit a pull request

License

MIT License - see LICENSE file for details

Support

For issues, questions, or contributions, please visit:

• GitHub: https://github.com/OWASP-BLT/BLT-MCP

• OWASP BLT: https://owasp.org/www-project-bug-logging-tool/

Acknowledgments

• Built on the Model Context Protocol

• Part of the OWASP BLT Project

• Powered by the security community