MCP Hub
Back to servers

ASF Policy MCP

MCP server for answering questions about Apache Software Foundation policies, offering tools to list, retrieve, and search policy documents on releases, licensing, branding, security, infrastructure, and incubator topics.

glama
Updated
May 7, 2026

ASF Policy MCP

MCP server for answering questions about Apache Software Foundation policies.

Covers the full set of policies listed at https://www.apache.org/board/policies — releases, licensing, branding, security, infrastructure, incubator, and more.

Policy pages are cached locally for 30 days. Use force_refresh=true on read tools to bypass the cache for a single call.

Install

python3 -m venv .venv
. .venv/bin/activate
pip install -e .

Run

asf-policy-mcp

For local development:

python -m asf_policy_mcp.server

Test

pip install -e ".[dev]"
make check

Configure with Claude Desktop or Codex

{
  "mcpServers": {
    "asf-policy": {
      "command": "<path to PolicyMCP>/.venv/bin/python",
      "args": ["-m", "asf_policy_mcp.server"]
    }
  }
}

Tools

  • list_policies — list all available policy documents organised by section, with cache status.
  • get_policy — retrieve the full text of a policy document by key (e.g. release_policy, branding, incubator).
  • search_policies — keyword search across all policy documents, returning ranked excerpts with context.
  • refresh_cache — force re-fetch of one or all policy documents from the ASF website.

Example questions

Releases

  • What files must be included in a release artifact for it to be valid?
  • Can we ship a release with only one +1 vote from the PMC?
  • Where must release artifacts be published — can we use GitHub Releases as the primary download?

Incubator

  • What does a podling need to do before it can graduate?
  • Can a podling cut a release before graduating, and what extra requirements apply?
  • Who can vote on a podling release, and whose votes are binding?

Licensing

  • Is the MIT licence compatible with Apache 2.0 for bundling in a release?
  • Can we include a library licensed under LGPL 2.1?
  • What is a Category X licence and why does it matter?
  • Do we need a CLA from every contributor, or only committers?
  • What licence headers are required in source files?

Security

  • If someone reports a vulnerability privately, how long before we must disclose?
  • Should security issues be discussed on the public dev list?

Branding

  • Can a company call its commercial product "Apache Foo Enterprise Edition"?
  • Can a third party use "Apache Foo" in the name of their commercial product?
  • What must appear on a project website for trademark compliance?

Infrastructure, press, privacy, and reporting

  • Can a project use an external Git host like GitLab as its primary code repository?
  • Can a project host its website on GitHub Pages?
  • Can a company issue a press release announcing new features they've added support for in an Apache project?
  • Are Apache mailing list archives public, and what does that mean for personal data posted to them?
  • If a PMC discovers a company misusing their project's trademark, who handles it and what should they do first?
  • Can a project list corporate affiliations next to committer names on a "Who We Are" page?
  • What fields are required in every PMC board report?

Apache Foo scenarios

  • Apache Foo wants to publish container images, nightly builds, and release candidates from the same Docker Hub namespace. Which parts are allowed, and what labels or warnings are needed?
  • ExampleCo donated most of Apache Foo's original code and still employs most committers. What website, branding, and project independence issues should the PMC watch for?
  • A security researcher privately reports a vulnerability in Apache Foo, but a downstream vendor wants to publish a fix immediately. How should the PMC coordinate disclosure, release voting, and public communication?
  • Apache Foo wants to accept a large generated code contribution produced with AI tooling and containing third-party snippets. Which licensing, provenance, and source-header checks apply?
  • The Apache Foo PMC wants to run an in-person "FooCon" with paid sponsors, project swag, and talks by vendors. Which event branding, merchandise, press, and conduct policies apply?
  • A former Apache Foo committer asks for their name and email to be removed from old mailing list archives and Git commits. What do the privacy, public archive, and repository policies imply?
  • Apache Foo has not released in two years, has no recent PMC additions, and depends on infrastructure that Infra wants to retire. What should the next board report include?

Policy documents

KeyTitleSection
pmcPMC GuideCommunity And Project Oversight
code_of_conductCode of ConductCommunity And Project Oversight
anti_harassmentAnti-Harassment PolicyCommunity And Project Oversight
public_archivesPublic Forum Archive PolicyCommunity And Project Oversight
project_independenceProject IndependenceIndependence
board_reportingBoard Reporting RequirementsReporting
release_policyRelease PolicyRelease
votingApache Voting ProcessRelease
release_distributionRelease Distribution PolicyRelease
docker_hubDocker Hub PolicyRelease
release_download_pagesRelease Download Pages PolicyRelease
nightliesProject Use of nightlies.apache.orgRelease
securitySecurity Team GuidanceSecurity
security_committersVulnerability Handling for CommittersSecurity
licensesContributor License AgreementsLicensing
apply_licenseApplying the Apache License, Version 2.0Licensing
cla_faqCLA FAQLicensing
source_headersApache Source HeadersLicensing
resolved_licensesApproved/Resolved Third-Party LicensesLicensing
crypto_policyHandling Cryptography within an ASF ReleaseLicensing
generative_toolingGenerative Tooling GuidanceLicensing
brandingProject Branding RequirementsBranding
trademark_maintenanceTrademark Maintenance ResponsibilitiesBranding
website_linkingWebsite Linking PolicyBranding
event_brandingThird-Party Event Branding PolicyBranding
merchandise_brandingNon-Software Merchandise Branding PolicyBranding
domain_name_brandingDomain Name Branding PolicyBranding
downstream_distributionApache Software Downstream Distribution PolicyBranding
podling_brandingIncubator Podling Branding GuideBranding
event_code_of_conductEvent Code of ConductEvents
trademark_policyASF Trademark PolicyBranding
repo_policyRepository PolicyInfrastructure
infra_site_banSite-Wide BanInfrastructure
committer_outreachOutreach to CommittersInfrastructure
content_moderationContent ModerationInfrastructure
mail_rejectionMail Rejection PolicyInfrastructure
spam_reportingDealing with Spam in Your ASF Email AccountInfrastructure
password_policyPassword RequirementsInfrastructure
third_party_servicesPolicy on Issues in Third-Party ServicesInfrastructure
slack_policyPolicy for Using ASF SlackInfrastructure
sensitive_informationPolicy on Sharing Sensitive Information with InfraInfrastructure
github_actionsGitHub ActionsInfrastructure
website_policyWebsite PolicyInfrastructure
content_security_policyContent Security PolicyInfrastructure
app_upgrade_policyApplication UpgradesInfrastructure
backup_policyBackupsInfrastructure
os_upgrade_policyOperating System UpgradesInfrastructure
vm_policyVirtual Machines for ProjectsInfrastructure
jira_account_approvalApproving Jira Account RequestsInfrastructure
jira_account_retentionJira Account Retention PolicyInfrastructure
pressPress & Marketing PolicyPress
sponsorshipSponsorship RequirementsFundraising
privacyPrivacy PolicyPrivacy
privacy_contributorsPrivacy Policy for ContributorsPrivacy
privacy_committersPrivacy Policy for CommittersPrivacy
privacy_project_websitesPrivacy Policy for Project WebsitesPrivacy
privacy_downloadable_products_highPrivacy Policy for ASF Downloadable Applications (High Privacy Standards)Privacy
privacy_downloadable_products_mediumPrivacy Policy for Products with Medium Privacy StandardsPrivacy
privacy_mailing_listsMailing List PolicyPrivacy
incubatorIncubator Podling PoliciesIncubator
incubator_ip_clearanceIncubator IP ClearanceIncubator

Reviews

No reviews yet

Sign in to write a review