Inception MCP Server
ADR-017: Domain Development Lifecycle
MCP Server for AI-driven Business Case creation through conversational interface.
Overview
This MCP server provides tools for creating, refining, and finalizing Business Cases through a structured question-answer workflow. It integrates with the governance database and optionally uses LLM for intelligent extraction.
Tools
| Tool | Description |
|---|---|
start_business_case |
Start new BC from free-text description |
answer_question |
Answer clarifying questions |
finalize_business_case |
Finalize BC and derive Use Cases |
list_business_cases |
List BCs with filters |
get_business_case |
Get full BC details |
get_categories |
Get available categories |
submit_for_review |
Submit BC for review |
get_session_status |
Check inception session status |
Installation
cd packages/inception-mcp
pip install -e .
Configuration
Environment variables:
# Database connection
DATABASE_URL=postgresql://user:pass@localhost:5432/platform
# LLM Gateway (optional)
LLM_GATEWAY_URL=http://localhost:8080/v1
LLM_API_KEY=sk-...
LLM_MODEL=claude-3-sonnet
Usage
Run as MCP Server
inception-mcp
Configure in Windsurf/Claude Desktop
Add to mcp_config.json:
{
"mcpServers": {
"inception": {
"command": "inception-mcp",
"env": {
"DATABASE_URL": "postgresql://..."
}
}
}
}
Workflow
- Start: Call
start_business_casewith initial description - Refine: Answer questions via
answer_question(7 questions) - Finalize: Call
finalize_business_caseto complete - Review: Submit via
submit_for_reviewwhen ready
Example Session
User: Create BC for "Wir brauchen eine bessere Suchfunktion"
→ start_business_case(initial_description="Wir brauchen...")
← session_id, bc_code="BC-001", question="Wer ist die Zielgruppe?"
User: Alle registrierten Benutzer
→ answer_question(session_id, answer="Alle registrierten Benutzer")
← question="Welche konkreten Vorteile werden erwartet?"
... (5 more questions) ...
→ finalize_business_case(session_id, derive_use_cases=true)
← bc_code="BC-001", derived_use_cases=[...], next_steps=[...]
Questions
The inception workflow asks these questions in order:
- target_audience: Who benefits?
- expected_benefits: What benefits are expected?
- scope: What's included?
- out_of_scope: What's excluded?
- success_criteria: How to measure success?
- risks: What risks exist?
- requires_adr: Is an ADR needed?
Database Schema
Uses tables from apps.governance:
platform.dom_business_caseplatform.dom_use_caseplatform.dom_conversationplatform.dom_conversation_turnplatform.dom_status_historyplatform.lkp_domain/platform.lkp_choice
Development
# Install dev dependencies
pip install -e ".[dev]"
# Run tests
pytest
Related
- ADR-015: Platform Governance System
- ADR-017: Domain Development Lifecycle
- governance app: Django models and admin
Metadata
Release files for iil-inception-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| iil_inception_mcp-0.1.0.tar.gz | 17.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| iil_inception_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.1 kB
Release files / iil_inception_mcp-0.1.0.tar.gz
| Download URL | iil_inception_mcp-0.1.0.tar.gz |
|---|---|
| Size | 17.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
abcd68d508081e4c0c19b85c3bf28a9b0a7fcf3cb1522520ebe5b6af75094e78
|
|
BLAKE2b-256 checksum How to use checksums |
a5cd6a79bd2a127ab9a5a469d21c2d7d9dee5856f7e729aa916f33209d28ec10
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / iil_inception_mcp-0.1.0-py3-none-any.whl
| Download URL | iil_inception_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 15.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d5feb7b432f663d7bf219accd1f1a4c8c13c606de323c080a485cbcaec8b0cfe
|
|
BLAKE2b-256 checksum How to use checksums |
6a627b7b18e6d0b0d311a19df0b14f69e2a6458e1ebd872af42fdb0ec47020fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for iil-inception-mcp 0.1.0
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.