Python: docs: exclude standard MCP servers from community catalog

[Eduard van Valkenburg (eavanvalkenburg)]

Motivation & Context

Protocol-level MCP compatibility can be mistaken for an Agent Framework-specific integration when reviewing community project submissions. The catalog criteria should make clear that standard MCP servers and gateways belong on their own project sites, consistent with the existing treatment of standard OpenTelemetry and OTLP integrations.

Description & Review Guide

• What are the major changes? Add an exclusion for MCP servers and gateways that only use Agent Framework's standard MCP client or tool configuration, and remove the existing Quilzo gateway entry from the Python catalog.
• What is the impact of these changes? Future community submissions based only on standard MCP interoperability will not be listed, and the current catalog is consistent with that rule.
• What do you want reviewers to focus on? Whether the exclusion clearly distinguishes protocol-level MCP compatibility from a published Agent Framework-specific integration.

Related Issue

N/A - trivial change. This is a small catalog eligibility clarification and removal of an entry that directly matches the clarified exclusion.

AI Assistance

• No material AI assistance was used.
• This is an AI-assisted contribution. I reviewed, understood, and verified all submitted content and accept responsibility for it.

AI assistance details: Documentation wording, catalog consistency update, and PR description.

Contribution Checklist

• The code builds clean without any errors or warnings
• All unit tests pass, and I have added new tests where possible
• The PR follows the Contribution Guidelines
• This PR links to an agreed issue with no competing open PR, or the Related Issue section documents a trivial-change or repository-automation exception.
• This is not a breaking change. If it is a breaking change, add the breaking change label (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.

[Copilot]

🟢 Approval recommended

Both documentation changes match the stated scope, with no blocking issues identified.

0 open findings

What changed in this PR

Clarifies community catalog eligibility by distinguishing standard MCP interoperability from Agent Framework-specific integrations.

Changes:

• Excludes MCP servers and gateways that require only standard client or tool configuration.
• Removes Quilzo from the Python catalog to align with that exclusion.

File	Description
python/​samples/​community-projects.md	Removes the Quilzo gateway entry.
.github/​skills/​community-projects/​SKILL.md	Adds the standard MCP interoperability exclusion.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

MAF Automated Review — Iteration 1

Result: No findings
Scope: full PR (1 commit(s)): 456902268b45
Model: gpt-5.6-sol

Overview

This documentation-only PR distinguishes protocol-level MCP interoperability from published Agent Framework-specific integrations and removes the existing catalog entry that relied on standard MCP tool configuration. The conditional “only require” wording preserves eligibility for genuine framework-specific integrations, while the shared review procedure, catalog structure checks, and Markdown link workflow provide concrete guardrails. No Critical, High, or Medium defect is supported by the changed behavior.

Reviewed the supplied pull-request change set across correctness, security/reliability, architecture, and failure behavior.
No publishable findings remained after source verification for this scope.