Podlings MCP

Podlings MCP

An 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.

Category
访问服务器

README

Podlings MCP

A small dependency-free MCP server for working with Apache Software Foundation Incubator podlings.xml data.

It exposes tools to:

  • load podling metadata from a URL or local XML file
  • list podlings with optional filtering
  • list current, graduated, and retired podlings
  • fetch details for a specific podling
  • return basic Incubator summary statistics
  • return mentor-count coverage statistics
  • analyze podling starts and active population over time
  • analyze yearly completion counts
  • analyze graduation rate over time
  • analyze graduation and retirement duration over time

If source is omitted, the server defaults to https://incubator.apache.org/podlings.xml.

The default ASF podlings XML source is cached locally for 24 hours. Set PODLINGS_MCP_CACHE_DIR to override the cache directory.

Requirements

  • Python 3.12+

Install

python3 -m pip install .

For development tools:

python3 -m pip install -e .[dev]

Run

After installation, run the stdio MCP server with:

podlings-mcp

For local development without installing first, you can still run:

python3 server.py

The server uses stdio, so it is intended to be launched by an MCP client. It accepts standard JSON-RPC 2.0 request objects and non-empty batches, ignores notifications, and returns structured JSON-RPC errors for malformed input, invalid request shapes, unknown methods, and invalid MCP tool parameters.

Test

python3 -m unittest discover -s tests -v

The tests cover parser behavior, tool functions, error cases, and a small end-to-end MCP stdio exchange.

Developer Commands

make format
make check-format
make test
make coverage
make lint
make typecheck
make check

Formatting and linting use ruff, including make check-format for CI-style format verification, and type checking uses mypy. See docs/architecture.md for the current module layout.

Example MCP client config

{
  "mcpServers": {
    "podlings": {
      "command": "podlings-mcp"
    }
  }
}

The package also keeps apache-podlings-mcp as a backwards-compatible command alias.

Concepts and Defaults

  • sponsor_type defaults to incubator across the filtering and analytics tools.
  • completed means podlings that reached an end state: graduated or retired.
  • Count and rate timeline tools use podling enddate to place outcomes into a year.
  • Duration timeline tools use both startdate and enddate to calculate months to graduate or retire.
  • completed_podlings_by_year returns both lists by default, and the graduated_podlings_by_year and retired_podlings_by_year tools are convenience wrappers over that same lookup.

Tools

list_podlings

List podlings from podlings.xml.

Arguments:

  • source: URL or local file path
  • status: optional exact status filter
  • sponsor_type: optional sponsor type filter, defaults to incubator
  • search: optional case-insensitive name/description/champion search
  • limit: optional max number of results to return

source is optional and defaults to the ASF Incubator podlings.xml URL.

list_current_podlings

List podlings with status="current".

Arguments:

  • source: URL or local file path
  • sponsor_type: optional sponsor type filter, defaults to incubator
  • search: optional case-insensitive name/description/champion search
  • limit: optional max number of results to return

source is optional and defaults to the ASF Incubator podlings.xml URL.

list_graduated_podlings

List podlings with status="graduated".

Arguments:

  • source: URL or local file path
  • sponsor_type: optional sponsor type filter, defaults to incubator
  • search: optional case-insensitive name/description/champion search
  • limit: optional max number of results to return

source is optional and defaults to the ASF Incubator podlings.xml URL.

list_retired_podlings

List podlings with status="retired".

Arguments:

  • source: URL or local file path
  • sponsor_type: optional sponsor type filter, defaults to incubator
  • search: optional case-insensitive name/description/champion search
  • limit: optional max number of results to return

source is optional and defaults to the ASF Incubator podlings.xml URL.

get_podling

Return a single podling by name.

Arguments:

  • source: URL or local file path
  • name: podling name

source is optional and defaults to the ASF Incubator podlings.xml URL.

podling_stats

Return summary statistics for a podlings.xml source.

Arguments:

  • source: URL or local file path
  • sponsor_type: optional sponsor type filter, defaults to incubator

source is optional and defaults to the ASF Incubator podlings.xml URL.

The stats include sponsor classification so you can distinguish:

  • incubator: sponsored by the Incubator
  • project: sponsored by another ASF project/PMC
  • unknown: no sponsor value was found

mentor_count_stats

Return mentor coverage and mentor-count distribution stats for a podlings.xml source.

Arguments:

  • source: URL or local file path
  • sponsor_type: optional sponsor type filter, defaults to incubator

source is optional and defaults to the ASF Incubator podlings.xml URL.

raw_podlings_xml_info

Return source metadata and a small preview of parsed records for troubleshooting.

Arguments:

  • source: URL or local file path

source is optional and defaults to the ASF Incubator podlings.xml URL.

graduation_rate_over_time

Return yearly graduation and retirement counts plus graduation rate based on podling enddate.

Arguments:

  • source: URL or local file path
  • start_year: optional inclusive start year filter
  • end_year: optional inclusive end year filter
  • sponsor_type: optional sponsor type filter, defaults to incubator

source is optional and defaults to the ASF Incubator podlings.xml URL.

podlings_started_over_time

Return yearly podling start counts based on startdate.

Arguments:

  • source: URL or local file path
  • start_year: optional inclusive start year filter
  • end_year: optional inclusive end year filter
  • sponsor_type: optional sponsor type filter, defaults to incubator

source is optional and defaults to the ASF Incubator podlings.xml URL.

started_podlings_by_year

Return the podlings that started in a specific year.

Arguments:

  • source: URL or local file path
  • year: required year to inspect
  • sponsor_type: optional sponsor type filter, defaults to incubator

source is optional and defaults to the ASF Incubator podlings.xml URL.

active_podlings_by_year

Return yearly active-podling counts based on lifecycle span.

Arguments:

  • source: URL or local file path
  • start_year: optional inclusive start year filter
  • end_year: optional inclusive end year filter
  • sponsor_type: optional sponsor type filter, defaults to incubator

source is optional and defaults to the ASF Incubator podlings.xml URL.

active_podlings_in_year

Return the podlings that were active during a specific year.

Arguments:

  • source: URL or local file path
  • year: required year to inspect
  • sponsor_type: optional sponsor type filter, defaults to incubator

source is optional and defaults to the ASF Incubator podlings.xml URL.

completion_rate_over_time

Return yearly completion rate using completed outcomes divided by active population.

Arguments:

  • source: URL or local file path
  • start_year: optional inclusive start year filter
  • end_year: optional inclusive end year filter
  • sponsor_type: optional sponsor type filter, defaults to incubator

source is optional and defaults to the ASF Incubator podlings.xml URL.

completion_count_over_time

Return yearly completed podling counts based on enddate, split into graduated and retired outcomes.

Arguments:

  • source: URL or local file path
  • start_year: optional inclusive start year filter
  • end_year: optional inclusive end year filter
  • sponsor_type: optional sponsor type filter, defaults to incubator

source is optional and defaults to the ASF Incubator podlings.xml URL.

completed_podlings_by_year

Return the podlings that completed in a specific year, split into graduated and retired outcomes.

Arguments:

  • source: URL or local file path
  • year: required year to inspect
  • status: optional filter, graduated or retired
  • sponsor_type: optional sponsor type filter, defaults to incubator

source is optional and defaults to the ASF Incubator podlings.xml URL.

completed_podlings_in_range

Return the podlings that completed within an inclusive year range.

Arguments:

  • source: URL or local file path
  • start_year: required inclusive start year
  • end_year: required inclusive end year
  • status: optional filter, graduated or retired
  • sponsor_type: optional sponsor type filter, defaults to incubator

source is optional and defaults to the ASF Incubator podlings.xml URL.

graduated_podlings_by_year

Return the podlings that graduated in a specific year.

Arguments:

  • source: URL or local file path
  • year: required year to inspect
  • sponsor_type: optional sponsor type filter, defaults to incubator

source is optional and defaults to the ASF Incubator podlings.xml URL.

retired_podlings_by_year

Return the podlings that retired in a specific year.

Arguments:

  • source: URL or local file path
  • year: required year to inspect
  • sponsor_type: optional sponsor type filter, defaults to incubator

source is optional and defaults to the ASF Incubator podlings.xml URL.

graduation_time_over_time

Return yearly time-to-graduate stats in months based on podling startdate and enddate, including average, median, and percentile views.

Arguments:

  • source: URL or local file path
  • start_year: optional inclusive start year filter
  • end_year: optional inclusive end year filter
  • sponsor_type: optional sponsor type filter, defaults to incubator

source is optional and defaults to the ASF Incubator podlings.xml URL.

time_to_retirement_over_time

Return yearly time-to-retirement stats in months based on podling startdate and enddate, including average, median, and percentile views.

Arguments:

  • source: URL or local file path
  • start_year: optional inclusive start year filter
  • end_year: optional inclusive end year filter
  • sponsor_type: optional sponsor type filter, defaults to incubator

source is optional and defaults to the ASF Incubator podlings.xml URL.

Usage Examples

These examples show natural-language requests an MCP client can answer with the tools below.

Current Podling Review Workflow

Use these when preparing for a regular review of the active Incubator podling roster:

  • "Show me the current Incubator-sponsored podlings."
  • "Summarize the current Incubator podlings, including how many have descriptions, sponsors, champions, and mentors listed."
  • "Which current podlings have unusually low mentor coverage?"
  • "Give me the full podlings.xml record for PodlingFoo."

This gives reviewers a quick view of the active roster, basic metadata coverage, and mentor coverage without needing to inspect podlings.xml directly.

Cohort And Lifecycle Review

Use these when trying to understand how a group of podlings moved through incubation over time:

  • "How many Incubator-sponsored podlings started each year from 2020 onwards?"
  • "Which podlings started in 2022?"
  • "Show the active podling count by year from 2020 to 2025."
  • "Which podlings were active during 2023?"

This connects yearly trends to the specific podlings behind those trends.

Completion And Graduation Review

Use these when reviewing graduation and retirement outcomes for a period:

  • "Show yearly Incubator podling completions since 2020, split into graduations and retirements."
  • "What was the graduation rate for completed podlings each year from 2020 to 2025?"
  • "Which podlings completed between 2023 and 2024?"
  • "Which podlings retired in 2023?"

This is useful for turning trend charts into a concrete list of podlings to discuss.

Duration Trend Review

Use these when reviewing how long podlings take to reach terminal outcomes:

  • "How long did graduated podlings take to graduate each year, including median and percentile timings?"
  • "Show retirement timing by year for podlings that retired after 2020."
  • "What is the average and median time to retirement for recent retired podlings?"

This separates completion volume from time-to-outcome trends.

Source Troubleshooting Workflow

Use these when a local XML file or alternate URL does not produce the expected results:

  • "Inspect /path/to/podlings.xml and show me the source metadata plus a few parsed records."
  • "List the first 10 normalized podling records from /path/to/podlings.xml."
  • "In /path/to/podlings.xml, show me the parsed record for ExampleOne."
  • "Using /path/to/podlings.xml, show yearly completion counts from 2020 onwards."

This helps separate source-loading issues from filtering or analytics questions.

Source examples

  • ASF URL: https://incubator.apache.org/podlings.xml
  • Local file: /path/to/podlings.xml

Notes

  • Remote sources are fetched with Python's standard library.
  • XML parsing targets the ASF Incubator podlings.xml structure directly.
  • Tools that accept sponsor_type default to incubator.
  • Valid sponsor_type values are incubator, project, and unknown.

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选