IPMC MCP
IPMC MCP
Un pequeño servidor MCP sin dependencias para vistas de supervisión del PMC de Apache Incubator.
Compone:
datos del ciclo de vida de los podlings desde
PodlingsMCPseñales de la comunidad y de informes desde
apache-health
Expone herramientas de nivel de Incubator con opiniones para ayudar al IPMC a:
identificar podlings que necesitan atención
evaluar la preparación para la graduación
generar informes de podlings
marcar necesidades de intervención de mentoría
resumir patrones de salud comunitaria entre los podlings
Requisitos
Python 3.12+
Related MCP server: Podlings MCP
Ejecución
python3 server.pyEl servidor utiliza stdio, por lo que está diseñado para ser iniciado por un cliente MCP.
Instalación
python3 -m pip install -e .Para herramientas de desarrollo:
python3 -m pip install -e .[dev]Ejemplo de configuración de cliente 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"
]
}
}
}El tiempo de ejecución predeterminado asume que los repositorios MCP de origen hermanos y los informes de salud están disponibles en:
/Users/justinmclean/PodlingsMCP/Users/justinmclean/HealthMCPreports, a menos que se establezca--health-source
Las llamadas a herramientas también pueden anular las rutas de datos de origen con podlings_source y health_source.
Configure las ubicaciones de los MCP de origen y el directorio de informes de salud con argumentos de inicio:
--podlings-mcp-repo: ruta al checkout dePodlingsMCP--health-mcp-repo: ruta al checkout deHealthMCP--health-source: directorio predeterminado de informes de apache-health
Prueba
python3 -m unittest discover -s tests -vCobertura
python3 -m coverage run -m unittest discover -s tests
python3 -m coverage report -mLa cobertura se limita al paquete local ipmc para que los MCP hermanos importados no diluyan el informe.
Arquitectura
Consulte docs/architecture.md para conocer el diseño del módulo, el flujo de ejecución y la estructura de pruebas.
Herramientas
ipmc_watchlist
Devuelve los podlings que más necesitan la atención del IPMC basándose en señales combinadas de ciclo de vida y salud.
Argumentos:
podlings_source: URL opcional o ruta de archivo local parapodlings.xmlhealth_source: directorio de informes opcional para informes markdown de apache-healthas_of_date: fecha opcionalYYYY-MM-DDpara vistas sensibles a la duraciónlimit: número máximo opcional de resultadosseverity_at_least: filtro de severidad mínima opcionalinclude_reasons: lista de filtros de motivos opcional
graduation_readiness
Evalúa si un podling parece estar listo, casi listo o aún no listo para la graduación.
Argumentos:
podling: nombre del podling requeridopodlings_sourcehealth_sourceas_of_dateinclude_evidence: booleano opcional, por defecto es truestrict_mode: booleano opcional
podling_brief
Devuelve un informe orientado al IPMC para un podling.
Argumentos:
podling: nombre del podling requeridopodlings_sourcehealth_sourceas_of_datefocus: lista de áreas opcionalbrief_format:summaryodetailedopcional
mentoring_attention_needed
Devuelve los podlings donde parece necesaria una intervención de mentoría.
Argumentos:
podlings_sourcehealth_sourceas_of_datelimit: número máximo opcional de resultadosurgency_at_least: filtro de urgencia mínima opcionalinclude_causes: lista de filtros de causas opcional
community_health_summary
Devuelve un resumen a nivel de IPMC de los patrones de salud comunitaria entre los podlings.
Argumentos:
podlings_sourcehealth_sourceas_of_datescope:all_podlings,active_podlingsoreporting_podlingsopcionalgroup_by:none,risk_band,mentor_loadoage_bandopcionalinclude_examples: booleano opcional
Valores predeterminados
Cuando se omite,
podlings_sourcetoma como valor predeterminado la URL depodlings.xmlde la ASF.Cuando se omite,
health_sourceutiliza--health-source, oreportssi ese argumento de inicio no está configurado.Las vistas de supervisión se centran en los podlings actuales de forma predeterminada.
El análisis de salud prefiere la ventana más reciente disponible en este orden:
3m,6m,12m,to-date.
Modelo de opinión
Este servidor mantiene los hechos de origen separados de las opiniones derivadas. Las vistas de riesgo y preparación se derivan de:
cobertura de mentores
fiabilidad de los informes
señales de aprobación de los mentores
actividad de la comunidad
visibilidad de las versiones
duración de la incubación
amplitud de la participación
Los resultados obtenidos están destinados a respaldar el juicio del IPMC, no a reemplazarlo.
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