Fill gaps from assistant conversations: gRPC metadata, MCP, comments

ai/integration/overview.mdx

@@ -11,6 +11,12 @@ You can configure Bruno to use any AI agent and editor of your choice.
 
 See [Use cases](./use-cases) for common workflows (generating collections, writing tests, CI/CD) and example prompts you can use with any supported agent.
 
+## MCP Server
+
+[Bruno MCP](https://github.com/usebruno/bruno-mcp) is a Model Context Protocol (MCP) server that lets MCP-compatible AI assistants, such as Claude and Cursor, work with your Bruno API collections. It exposes your requests, folders, and environments as MCP tools so an agent can discover, inspect, and run them, while your collection files stay on your local filesystem.
+
+The Bruno desktop app does not include a built-in MCP server. See the [Bruno MCP repository](https://github.com/usebruno/bruno-mcp) for details.
+
 ## Supported Agents
 
 - [Cursor](https://cursor.com) - AI code editor with powerful automation for API development workflows

bru-lang/language.mdx

@@ -3,7 +3,7 @@
 sidebarTitle: "Language"
 ---
 
 A Bru file is made up of blocks.
 There are three kinds of blocks
 - Dictionary block
 - Text block
@@ -49,3 +49,18 @@
 ```
 Any key in the array block can be prefixed with `~` to indicate that it is disabled.
 
+### Comments
+
+The Bru markup language does not have a dedicated comment syntax. To keep an entry in a file without it taking effect, prefix it with `~` to disable it:
+
+```bash
+headers {
+  content-type: application/json
+  ~transaction-id: {{transactionId}}
+}
+```
+
+The content of `script:pre-request`, `script:post-response`, and `tests` blocks is JavaScript, so standard JavaScript comments (`//` and `/* */`) work inside those blocks.
+
+To document a request, use the `docs` block or the **Docs** tab in the app.
+

get-started/configure/keybindings.mdx

@@ -81,6 +81,17 @@ Below are the default keyboard shortcuts. macOS equivalents replace `Ctrl` with
 | Open preferences | `⌘ ,` | `Ctrl ,` |
 | Close Bruno | `⌘ Q` | `Ctrl Shift Q` |
 
+**Code editor**
+
+These shortcuts work inside code editors such as the request body, script, and tests editors. They are built into the editor and don't appear in the Keybindings panel.
+
+| Command | macOS | Windows / Linux |
+|---|---|---|
+| Toggle comment on selected lines | `⌘ /` | `Ctrl /` |
+| Fold all | `⌘ Y` | `Ctrl Y` |
+| Unfold all | `⌘ I` | `Ctrl I` |
+| Trigger autocomplete | `⌘ Space` | `Ctrl Space` |
+
 ## Customizing keybindings
 
 You can remap most keyboard shortcuts to your preferred key combinations.

send-requests/grpc/grpc-request.mdx

@@ -5,14 +5,14 @@
 
 Bruno provides comprehensive support for gRPC requests, enabling you to test and interact with gRPC services directly from the interface. With Bruno's gRPC support, you can:
 
 - **Add Proto files** for enhanced IntelliSense and method discovery
 - **Use Server Reflection** as an alternative to Proto files for automatic method suggestions
 - **Call server methods** with full parameter support and type validation
 - **Test real-time streaming APIs** including unary, server streaming, client streaming, and bidirectional streaming
 
 ## gRPC Interface
 
 Bruno gRPC interface provides an intuitive way to interact with gRPC services. The interface automatically adapts based on whether you're using Proto files or Server Reflection.
 
 ![gRPC Interface](/images/screenshots/send-request/grpc/1-grpc-interface.webp)
 
@@ -51,4 +51,16 @@
 
 You'll see the response in the **Response** section with detailed information about the request execution.
 
+## Adding metadata
+
+gRPC uses metadata instead of HTTP headers. Use metadata to send key-value pairs such as access tokens or tenant identifiers with a request.
+
+1. Open your gRPC request and select the **Metadata** tab in the request pane.
+2. Click **Add Metadata** and enter the key and value.
+3. Use the checkbox next to an entry to enable or disable it.
+
+Metadata values support variable interpolation, so you can reference environment or collection variables like `{{token}}`.
+
+For authentication methods such as Basic, Bearer, or API key, use the **Auth** tab instead of adding metadata manually.
+
 To learn about proto files, navigate to the [Adding Proto file section.](./grpc-proto)