docs: clarify MCP YAML examples need context or block metadata

- Add ellipsis (...) to YAML examples to indicate they're part of a larger config file
- Add explicit note about required metadata fields when creating standalone block files
- This prevents confusion when users try to copy snippets directly into .continue/mcpServers/

Generated with [Continue](https://continue.dev)

Co-Authored-By: Continue <[email protected]>

Author: bdougie

docs/customize/deep-dives/mcp.mdx

@@ -77,15 +77,21 @@ block](https://hub.continue.dev/new?type=block&blockType=mcpServers) or add a lo
 server block to your [config file](./configuration.md):
 
 ```yaml title="config.yaml"
+# ...
 mcpServers:
   - name: SQLite MCP
     command: npx
     args:
       - "-y"
       - "mcp-sqlite"
       - "/path/to/your/database.db"
+# ...
 ```
 
+<Note>
+When creating a standalone block file in `.continue/mcpServers/`, remember to include the required metadata fields (`name`, `version`, `schema`) as shown in the Quick Start example above.
+</Note>
+
 ### How to Configure MCP Server Properties
 
 MCP blocks follow the established syntax for blocks, with a few additional properties specific to MCP servers.
@@ -105,35 +111,41 @@ MCP now supports remote server connections through HTTP-based transports, expand
 For real-time streaming communication, use the SSE transport:
 
 ```yaml
+# ...
 mcpServers:
   - name: Name
     type: sse
     url: https://....
+# ...
 ```
 
 #### How to Use Standard Input/Output (`stdio`)
 
 For local MCP servers that communicate via standard input and output:
 
 ```yaml
+# ...
 mcpServers:
   - name: Name
     type: stdio
     command: npx
     args:
       - "@modelcontextprotocol/server-sqlite"
       - "/path/to/your/database.db"
+# ...
 ```
 
 #### How to Use Streamable HTTP Transport
 
 For standard HTTP-based communication with streaming capabilities:
 
 ```yaml
+# ...
 mcpServers:
   - name: Name
     type: streamable-http
     url: https://....
+# ...
 ```
 
 These remote transport options allow you to connect to MCP servers hosted on remote infrastructure, enabling more flexible deployment architectures and shared server resources across multiple clients.
@@ -146,6 +158,7 @@ With some MCP servers you will need to use API keys or other secrets. You can le
 as well as access hosted secrets in the Continue Hub. To leverage Hub secrets, you can use the `inputs` property in your MCP env block instead of `secrets`.
 
 ```yaml
+# ...
 mcpServers:
   - name: Supabase MCP
     command: npx
@@ -163,4 +176,5 @@ mcpServers:
       - "@modelcontextprotocol/server-github"
     env:
       GITHUB_PERSONAL_ACCESS_TOKEN: ${{ secrets.GITHUB_PERSONAL_ACCESS_TOKEN }}
+# ...
 ```