Skip to main content

AIDLC MCP Tools

A Model Context Protocol (MCP) server implementation that provides AI agents with tools to interact with the AIDLC Dashboard service. This enables seamless integration between AI tools and project management workflows.

🚀 Features

  • Project Management: Create and manage projects through MCP
  • Artifact Upload: Upload AI-generated artifacts (epics, user stories, domain models, etc.)
  • Progress Tracking: Update project status and track completion
  • Health Monitoring: Check service availability and performance
  • Batch Operations: Handle multiple artifacts efficiently
  • Amazon Q Integration: Optimized for Amazon Q Developer workflows

📋 Requirements

  • Python 3.11+
  • requests library
  • AIDLC Dashboard service running (for integration)

🛠️ Installation

# Install with uv
uv pip install -e .

# Or install from PyPI (when published)
uv pip install mcp-tools

Option 2: Using pip

# Install in development mode
pip install -e .

# Or install dependencies manually
pip install -r requirements.txt

Option 3: Quick Setup Script

./setup.sh

🌐 Usage

As MCP Server (Amazon Q Integration)

  1. Configure Amazon Q MCP settings:
{
  "mcpServers": {
    "aidlc-dashboard": {
      "command": "uvx",
      "args": ["--from", "aidlc-mcp-tools@latest", "aidlc-mcp-server"],
      "env": {
        "AIDLC_DASHBOARD_URL": "http://44.253.157.102:8000/api"
      }
    }
  }
}
  1. Start the MCP server:
aidlc-mcp-server

🔧 Configuration

Environment Variables

Variable Description Default
AIDLC_DASHBOARD_URL Dashboard API base URL http://localhost:8000/api
AIDLC_TIMEOUT Request timeout (seconds) 30
AIDLC_RETRY_ATTEMPTS Number of retry attempts 3
AIDLC_LOG_LEVEL Logging level INFO

📖 Available MCP Tools

1. aidlc_create_project

Create a new project in the AIDLC Dashboard.

Parameters:

  • name (string): Project name

Example:

{
  "name": "create_project",
  "arguments": {
    "name": "E-commerce Platform"
  }
}

2. aidlc_upload_artifact

Upload an artifact to a project.

Parameters:

  • project_id (string): Project identifier
  • artifact_type (string): Type of artifact (epics, user_stories, domain_model, model_code_plan, ui_code_plan)
  • content (object): Artifact content

Example:

{
  "name": "upload_artifact",
  "arguments": {
    "project_id": "project-123",
    "artifact_type": "epics",
    "content": {
      "title": "User Management",
      "description": "Complete user management system",
      "priority": "high"
    }
  }
}

3. aidlc_update_status

Update the status of an artifact.

Parameters:

  • project_id (string): Project identifier
  • artifact_type (string): Type of artifact
  • status (string): New status (not-started, in-progress, completed)

4. aidlc_get_project

Get project details and current status.

Parameters:

  • project_id (string): Project identifier

5. aidlc_list_projects

List all projects in the dashboard.

Parameters: None

6. aidlc_health_check

Check if the dashboard service is healthy and accessible.

Parameters: None

🎯 Artifact Types and Schemas

Epics

{
  "title": "Epic Title",
  "description": "Epic description",
  "user_stories": ["US-001", "US-002"],
  "priority": "high|medium|low",
  "acceptance_criteria": ["Criteria 1", "Criteria 2"]
}

User Stories

{
  "stories": [
    {
      "id": "US-001",
      "title": "Story Title",
      "description": "As a user, I want...",
      "acceptance_criteria": ["Criteria 1"],
      "priority": "high",
      "story_points": 5
    }
  ],
  "total_count": 1,
  "epics": ["Epic-001"]
}

Domain Model

{
  "entities": [
    {
      "name": "User",
      "attributes": ["id", "username", "email"],
      "description": "System user entity"
    }
  ],
  "relationships": [
    {
      "from": "User",
      "to": "Order",
      "type": "one-to-many"
    }
  ]
}

Model Code Plan

{
  "components": [
    {
      "name": "UserService",
      "type": "service",
      "dependencies": ["UserRepository"]
    }
  ],
  "implementation_steps": [
    "Create entities",
    "Implement repositories"
  ]
}

UI Code Plan

{
  "pages": [
    {
      "name": "LoginPage",
      "route": "/login",
      "components": ["LoginForm", "Header"]
    }
  ],
  "navigation": {
    "type": "SPA",
    "router": "React Router"
  }
}

Metadata

Release files for aidlc-mcp-tools 1.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for aidlc-mcp-tools 1.2.1
File Size Uploaded Provenance
aidlc_mcp_tools-1.2.1.tar.gz 21.9 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for aidlc-mcp-tools 1.2.1
File Interpreter ABI Platform
aidlc_mcp_tools-1.2.1-py3-none-any.whl Python 3 none any Details

Total release size: 35.7 kB

Release files / aidlc_mcp_tools-1.2.1.tar.gz

Download URL aidlc_mcp_tools-1.2.1.tar.gz
Size 21.9 kB
Tags Source
SHA-256 checksum
How to use checksums
8bde8f5ad75c09ac9b59db32d4bbce46d7b4b8a25e0f30ba8fe0d253ead45bed
BLAKE2b-256 checksum
How to use checksums
f575f6047b83db88667aaa769a1226a0a9a38701fd9490b2dd63670630429305
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.12.3

Release files / aidlc_mcp_tools-1.2.1-py3-none-any.whl

Download URL aidlc_mcp_tools-1.2.1-py3-none-any.whl
Size 13.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
79712a38a97c962441c57627c69c01476e71b1f8efe377bed9a9eb11f7d19629
BLAKE2b-256 checksum
How to use checksums
3b5d64f81385f13141d41f0713eb25de5ab4d47c8297c6d0dc64fcfa9f1a369b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.1.0 CPython/3.12.3

Security for aidlc-mcp-tools 1.2.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page