IPMC MCP
IPMC MCP
Apache Incubator PMC 감독 뷰를 위한 소규모 의존성 없는 MCP 서버입니다.
다음 요소들을 구성합니다:
PodlingsMCP의 포들링 수명 주기 데이터apache-health의 커뮤니티 및 보고서 신호
IPMC를 돕기 위해 다음과 같은 인큐베이터 수준의 도구들을 제공합니다:
주의가 필요한 포들링 식별
졸업 준비 상태 평가
포들링 브리핑 생성
멘토링 개입 필요성 표시
포들링 전반의 커뮤니티 건강 패턴 요약
요구 사항
Python 3.12+
Related MCP server: Podlings MCP
실행
python3 server.py이 서버는 stdio를 사용하므로 MCP 클라이언트에 의해 실행되도록 설계되었습니다.
설치
python3 -m pip install -e .개발 도구의 경우:
python3 -m pip install -e .[dev]MCP 클라이언트 설정 예시
{
"mcpServers": {
"ipmc": {
"command": "python3",
"args": [
"/Users/justinmclean/IncubatorMCP/server.py",
"--podlings-mcp-repo",
"/Users/justinmclean/PodlingsMCP",
"--health-mcp-repo",
"/Users/justinmclean/HealthMCP",
"--health-source",
"/Users/justinmclean/incubator/tools/health/reports"
]
}
}
}기본 런타임은 형제 소스 MCP 저장소와 건강 보고서가 다음 위치에 있다고 가정합니다:
/Users/justinmclean/PodlingsMCP/Users/justinmclean/HealthMCPreports(단,--health-source가 설정되지 않은 경우)
도구 호출 시 podlings_source 및 health_source를 사용하여 소스 데이터 경로를 재정의할 수도 있습니다.
시작 인수를 사용하여 소스 MCP 위치와 건강 보고서 디렉토리를 구성하십시오:
--podlings-mcp-repo:PodlingsMCP체크아웃 경로--health-mcp-repo:HealthMCP체크아웃 경로--health-source: 기본 apache-health 보고서 디렉토리
테스트
python3 -m unittest discover -s tests -v커버리지
python3 -m coverage run -m unittest discover -s tests
python3 -m coverage report -m커버리지는 로컬 ipmc 패키지로 범위가 지정되어 있어 가져온 형제 MCP가 보고서를 희석하지 않습니다.
아키텍처
모듈 레이아웃, 런타임 흐름 및 테스트 구조는 docs/architecture.md를 참조하십시오.
도구
ipmc_watchlist
수명 주기 및 건강 신호를 결합하여 IPMC의 주의가 가장 필요한 포들링을 반환합니다.
인수:
podlings_source:podlings.xml에 대한 선택적 URL 또는 로컬 파일 경로health_source: apache-health 마크다운 보고서를 위한 선택적 보고서 디렉토리as_of_date: 기간에 민감한 뷰를 위한 선택적YYYY-MM-DD날짜limit: 선택적 최대 결과 수severity_at_least: 선택적 최소 심각도 필터include_reasons: 선택적 이유 필터 목록
graduation_readiness
포들링이 졸업 준비가 되었는지, 거의 준비되었는지, 아직 준비되지 않았는지 평가합니다.
인수:
podling: 필수 포들링 이름podlings_sourcehealth_sourceas_of_dateinclude_evidence: 선택적 불리언, 기본값은 truestrict_mode: 선택적 불리언
podling_brief
한 포들링에 대한 IPMC 지향 브리핑을 반환합니다.
인수:
podling: 필수 포들링 이름podlings_sourcehealth_sourceas_of_datefocus: 선택적 영역 목록brief_format: 선택적summary또는detailed
mentoring_attention_needed
멘토링 개입이 필요해 보이는 포들링을 반환합니다.
인수:
podlings_sourcehealth_sourceas_of_datelimit: 선택적 최대 결과 수urgency_at_least: 선택적 최소 긴급도 필터include_causes: 선택적 원인 필터 목록
community_health_summary
포들링 전반의 커뮤니티 건강 패턴에 대한 IPMC 수준의 요약을 반환합니다.
인수:
podlings_sourcehealth_sourceas_of_datescope: 선택적all_podlings,active_podlings또는reporting_podlingsgroup_by: 선택적none,risk_band,mentor_load또는age_bandinclude_examples: 선택적 불리언
기본값
생략 시
podlings_source는 ASFpodlings.xmlURL을 기본값으로 합니다.생략 시
health_source는--health-source를 사용하거나, 해당 시작 인수가 설정되지 않은 경우reports를 사용합니다.감독 뷰는 기본적으로 현재 포들링에 초점을 맞춥니다.
건강 분석은
3m,6m,12m,to-date순서로 가장 최신의 가용 기간을 선호합니다.
의견 모델
이 서버는 소스 사실과 도출된 의견을 분리합니다. 위험 및 준비 상태 뷰는 다음에서 도출됩니다:
멘토 커버리지
보고 신뢰성
멘토 승인 신호
커뮤니티 활동
릴리스 가시성
인큐베이션 기간
참여 범위
결과물은 IPMC의 판단을 대체하는 것이 아니라 지원하기 위한 것입니다.
Available Tools
21 toolscommunity_health_summaryC
Return an IPMC-level summary of community health across podlings, including strong patterns, risks, and mentoring-capacity signals.
Inputs: podlings_source, health_source, report_source, mail_source, +5 more.
configure_sourcesA
Set or inspect process-level source defaults so later IPMC tool calls can omit source override arguments.
Inputs: podlings_source, health_source, report_source, mail_source, +3 more.
cross_source_mismatchesB
Return concrete mismatches between cached report narrative and current health or release evidence.
Inputs: podlings_source, health_source, report_source, mail_source, +5 more.
current_podlings_overviewB
Return a factual overview of current Incubator podlings from podlings.xml lifecycle metadata.
Inputs: podlings_source, as_of_date, limit, include_descriptions.
graduation_readinessB
Assess whether a podling appears ready, near ready, or not yet ready for graduation.
Inputs: podling (required), podlings_source, health_source, report_source, +5 more.
ipmc_watchlistA
Return podlings that most need IPMC attention based on combined lifecycle and health signals.
Inputs: podlings_source, health_source, report_source, mail_source, +5 more.
mentoring_attention_neededA
Return podlings where mentoring intervention appears necessary, with urgency and likely causes.
Inputs: podlings_source, health_source, report_source, mail_source, +5 more.
podling_briefB
Return an IPMC-oriented briefing for a single podling, including status, trajectory, and attention areas.
Inputs: podling (required), podlings_source, health_source, report_source, +5 more.
recent_changesC
Return per-podling recent deltas the IPMC should scan, excluding unchanged or static fields.
Inputs: podlings_source, health_source, report_source, mail_source, +4 more.
refresh_mail_cacheC
Refresh cached general@incubator.apache.org message summaries used by IPMC mail evidence tools.
Inputs: mail_source, mail_api_base, mail_timespan, query, +1 more.
refresh_report_cacheB
Refresh cached ASF Incubator report data used by IPMC report-narrative tools.
Inputs: report_source, years, full_history, limit, +2 more.
release_artifact_evidenceB
Return ReleaseMCP artifact, sidecar, cadence, Incubator naming evidence, and optional release-page and GitHub/Docker Hub/PyPI/Maven distribution hints for one podling.
Inputs: podling (required), release_dist_base, release_archive_base, release_max_depth, +6 more.
release_visibilityB
Return release-governance visibility concerns, including no releases and activity/release mismatches.
Inputs: podlings_source, health_source, report_source, mail_source, +5 more.
release_vote_evidenceB
Return MailMCP release vote/result thread evidence for one podling alongside IPMC release visibility signals.
Inputs: podling (required), podlings_source, health_source, report_source, +5 more.
reporting_cohortB
Return current reporting podlings grouped into non-ranked IPMC review buckets: reporting issues, release visibility issues, recent significant changes, and no obvious concerns.
Inputs: podlings_source, health_source, report_source, mail_source, +3 more.
reporting_gapsB
Return podlings with Incubator reporting compliance gaps, excluding activity analysis.
Inputs: podlings_source, health_source, report_source, mail_source, +5 more.
reporting_reliabilityB
Return objective reporting reliability patterns over time, separating one-off late reporting from repeated late or missing reporting.
Inputs: podlings_source, health_source, report_source, mail_source, +5 more.
reporting_scheduleB
Return expected Incubator reporting cadence, due-this-month status, and next expected reporting period from PodlingsMCP.
Inputs: podlings_source, podling, as_of_date, report_month, +2 more.
report_narrative_signalsB
Return report-derived narrative signals such as latest reported issues, recurring issues, low observed mentor sign-off, and release visibility mismatches.
Inputs: podlings_source, health_source, report_source, mail_source, +5 more.
significant_changesC
Return a structured factual subset of recent changes: no 12-month releases, large activity shifts, and newly visible reporting or release transitions.
Inputs: podlings_source, health_source, report_source, mail_source, +5 more.
stalled_podlingsB
Return podlings that match the strict low-delivery, no-release stalled definition.
Inputs: podlings_source, health_source, report_source, mail_source, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 21 tools
Each tool has a clearly defined and distinct purpose, focusing on specific aspects of IPMC oversight such as community health, podling status, releases, reporting, or mentoring. There is no ambiguity between tools.
All tool names follow a consistent pattern of descriptive phrases using underscores (e.g., community_health_summary, graduation_readiness). No mixing of camelCase or other conventions is observed.
With 21 tools, the server covers a broad domain of IPMC responsibilities. While the count is relatively high, each tool addresses a necessary function, and the scope justifies the number.
The tool set provides comprehensive coverage of IPMC information needs, including community health, podling lifecycle, releases, reporting, and mentoring. Minor gaps may exist for direct actions, but the analysis surface is thorough.
Related MCP Connectors
MCP server for VC pitch-deck scoring, thesis-fit matching, and deal-flow management.
MCP server for CertScore.ai public website risk-signal workflows.
Guarded MCP server for agent-readable business truth, provenance, readiness, and discovery.
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
Related MCP Servers
- FlicenseAqualityDmaintenanceA deterministic, network-free MCP server for validating repository release hygiene and version alignment in local projects. It enables automated repository health checks and generates standardized release checklists based on project state.1-
- AlicenseBqualityDmaintenanceAn MCP server for accessing and analyzing Apache Software Foundation Incubator podling data from podlings.xml. It provides tools to query podling metadata, generate statistics, and analyze incubation trends over time.22MIT
- AlicenseAqualityDmaintenanceAn MCP server for querying and analyzing Apache Incubator podling health reports. It provides tools to list, search, and compare podling metrics across different time windows from Apache's health report Markdown files.9MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for comprehensive PyPI package intelligence, providing tools for dependency analysis, security scanning, health scoring, license compliance, and trend tracking.MIT