Add MCP server integration details to AGENTS.md

AGENTS.md

@@ -17,6 +17,10 @@ Use a virtual environment to isolate dependencies:
 
 Write Python to PEP 8 with four-space indentation, descriptive variable names, and concise docstrings that explain API usage choices. Name new notebooks with lowercase, dash-or-underscore-separated phrases that match their directory—for example `examples/gpt-5/prompt-optimization-cookbook.ipynb`. Keep markdown cells focused and prefer numbered steps for multi-part workflows. Store secrets in environment variables such as `OPENAI_API_KEY`; never hard-code keys inside notebooks.
 
+## MCP Server Integration
+
+Gradio apps can serve as MCP servers, with an MCP tool corresponding to each API endpoint. To enable this functionality, launch the Gradio app with `.launch(mcp_server=True)` or set the `GRADIO_MCP_SERVER` environment variable to `"True"`.
+
 ## Testing Guidelines
 
 Execute notebooks top-to-bottom after installing dependencies and clear lingering execution counts before committing. For Python modules or utilities, include self-check cells or lightweight `pytest` snippets and show how to run them (for example, `pytest examples/object_oriented_agentic_approach/tests`). When contributions depend on external services, mock responses or gate the cells behind clearly labeled opt-in flags.
@@ -32,6 +36,7 @@ New or relocated content must have an entry in `registry.yaml` with an accurate
 ## Review Guidelines
 
 These are considered priority 0 issues for this repo, in addition to the normal priority for possible issues.
+
 - Verify file, function, and notebook names follow the repo's naming conventions and clearly describe their purpose.
 - Scan prose and markdown for typos, broken links, and inconsistent formatting before approving.
 - Check that code identifiers remain descriptive (no leftover placeholder names) and that repeated values are factored into constants when practical.