feat: support transitive MCP dependency propagation

docs/dependencies.md

@@ -75,9 +75,21 @@ dependencies:
     - microsoft/apm-sample-package  # Design standards, prompts
     - github/awesome-copilot/skills/review-and-refactor  # Code review skill
   mcp:
-    - io.github.github/github-mcp-server
+    - io.github.github/github-mcp-server          # Registry reference
+    - name: my-knowledge-base                      # Inline config
+      type: streamable-http
+      url: https://my-kb.example.com/
 ```
 
+MCP dependencies support two formats:
+
+- **Registry strings** — resolve via the MCP server registry (e.g. `io.github.github/github-mcp-server`).
+- **Inline dicts** — written directly to runtime configs, bypassing the registry. Useful for private or self-hosted servers.
+
+Inline entries require `name`, `type` (`sse` or `streamable-http`), and `url`. An optional `headers` map is also supported.
+
+MCP dependencies declared by transitive APM packages are collected automatically during `apm install`.
+
 ### 2. Install Dependencies
 
 ```bash

docs/integrations.md

@@ -483,11 +483,18 @@ APM provides first-class support for MCP servers:
 # apm.yml - MCP dependencies
 dependencies:
   mcp:
+    # Registry references
     - ghcr.io/github/github-mcp-server
     - ghcr.io/modelcontextprotocol/filesystem-server
     - ghcr.io/modelcontextprotocol/postgres-server
+    # Inline config (private / self-hosted servers)
+    - name: my-knowledge-base
+      type: streamable-http
+      url: https://my-kb.example.com/
 ```
 
+Inline MCP entries (`name`/`type`/`url` dicts) are written directly into runtime configs and bypass the registry. They are also collected transitively from APM dependencies.
+
 ```bash
 # Install MCP dependencies
 apm install