more descriptions

Author: evilnick

docs/diagram-format.md

@@ -1,6 +1,8 @@
 ---
 title: diagram.json File Format
 sidebar_label: diagram.json
+description: Reference guide for the `diagram.json` file for Wokwi simulation projects. This file defines components, their attributes, layout positions, and the connections between them.
+keywords: [diagram.json, connections, wiring, component layout, virtual hardware, ESP32, STM32, Arduino, wire placement, simulation diagram, simulation editor]
 ---
 
 Each simulation project contains a diagram.json file. This file defines the components

docs/gdb-debugging.md

@@ -1,6 +1,8 @@
 ---
 title: GDB Debugging (Advanced)
 sidebar_label: GDB Debugging
+description: Use GDB to debug Arduino and Raspberry Pi Pico code directly in the Wokwi simulator. This guide describes how to launch a web-based GDB session, step through code, set breakpoints and inspect variables.
+keywords: [GDB, debugging, Arduino, Raspberry Pi Pico, web gdb, gdb commands, breakpoint, gdb cheatsheet, sketch.ino, step-through debugging, avr debugging]
 ---
 
 GDB is a powerful source code debugger. You can use it to debug your Arduino and Raspberry Pi Pico code in Wokwi.

docs/wokwi-ci/automation-scenarios.md

@@ -1,6 +1,8 @@
 ---
 title: Wokwi Automation Scenarios
 sidebar_label: Automation Scenarios
+description: Automate simulations in Wokwi using YAML-based automation scenarios. Simulate button presses, sensor input, and verify serial output to test firmware programmatically.
+keywords: [automation, simulation testing, YAML automation scenarios, embedded simulation, automated firmware testing, sensor state simulation]
 ---
 
 Automation scenarios allow you to automate the simulation, push buttons, change the state of the sensors, and check the serial output. You can use automation scenarios to test your firmware in a realistic environment, and verify that it behaves as expected.

docs/wokwi-ci/cli-installation.md

@@ -1,6 +1,8 @@
 ---
 title: Wokwi CLI Installation
 sidebar_label: CLI Installation
+description: Install the CLI to run and automate Wokwi simulations from your terminal.
+keywords: [CLI, terminal, CI, Powershell, wokwi-cli]
 ---
 
 The CLI allows you to run Wokwi simulations from your terminal, and integrate them with your CI system. We recommend using the [Wokwi for VS Code](../vscode/getting-started) extension for local development, and the CLI for running your tests on CI.

docs/wokwi-ci/cli-usage.md

@@ -1,6 +1,8 @@
 ---
 title: Wokwi CLI Usage
 sidebar_label: CLI Usage
+description: Wokwi CLI command reference
+keywords: [ reference, Wokwi, CLI, API, CI Dashboard, serial monitor]
 ---
 
 Create an API token on the [Wokwi CI Dashboard](https://wokwi.com/dashboard/ci). Set the `WOKWI_CLI_TOKEN` environment variable to the token value.

docs/wokwi-ci/getting-started.md

@@ -1,6 +1,9 @@
 ---
 title: Wokwi for CI and GitHub Actions
 sidebar_label: Introduction
+description: Use Wokwi CI to automate embedded firmware testing in continuous integration workflows like GitHub Actions and GitLab CI. Learn about WITL (Wokwi in the Loop), automation scenarios, simulation limits, and integrating with AI agents using MCP.
+
+keywords: [Wokwi CI, embedded testing, continuous integration, GitHub Actions, GitLab CI, firmware simulation, automation scenarios, Wokwi CLI, WITL, Model Context Protocol, MCP, AI-assisted development, simulation limits, embedded workflows]
 ---
 
 Wokwi provides a robust simulation solution for automated testing of your embedded firmware on CI systems like [GitHub Actions](./github-actions), GitLab CI, and others. You can use Wokwi to run your tests on every commit, and get instant feedback on your code changes.

docs/wokwi-ci/github-actions.md

@@ -1,6 +1,8 @@
 ---
 title: Using Wokwi in GitHub Actions
 sidebar_label: Github Actions
+description: Integrate Wokwi CI with GitHub Actions to automatically test your embedded firmware on every commit. 
+keywords: [GitHub Actions, embedded testing, firmware automation, CI/CD, automation scenarios, CI workflows, embedded projects, continuous integration]
 ---
 
 You can use Wokwi CI with GitHub Actions to run your tests on every commit. You need to have a workflow that builds your project's firmware. Add the following step to your workflow:
@@ -16,7 +18,7 @@ You can use Wokwi CI with GitHub Actions to run your tests on every commit. You
 
 For a complete list of options, check out the [action's README](https://github.com/wokwi/wokwi-ci-action?tab=readme-ov-file#usage).
 
-## CLI Tokens
+## CLI tokens
 
 You also need to set up the `WOKWI_CLI_TOKEN` secret in your repository settings. You can create an API token on the [Wokwi CI Dashboard](https://wokwi.com/dashboard/ci).
 

docs/wokwi-ci/mcp-support.md

@@ -1,8 +1,14 @@
-# MCP Support
+---
+title: Model Context Protocola (MCP) support
+sidebar_label: MCP support
+description: Integrate AI agents like Copilot, Claude, Cursor, Gemini, and ChatGPT with Wokwi using the Model Context Protocol (MCP). This guide covers configuring the Wokwi MCP server, enabling real-time simulation, automated testing, and virtual hardware interaction.
+keywords: [MCP, Model Context Protocol, AI integration, Copilot, Claude, ChatGPT, Gemini, Cursor, automated testing, serial console]
+---
+
 
-## What is MCP?
+# MCP Support
 
-The Model Context Protocol (MCP) is an open standard that allows AI agents—such as Copilot, Claude Code, Cursor, and others to securely interact with external tools and services. For Wokwi users, MCP enables seamless integration between AI assistants and embedded simulation.
+The Model Context Protocol (MCP) is an open standard that allows AI agents—such as Copilot, Claude Code, Cursor, Gemini, ChatGPT and others to securely interact with external tools and services. For Wokwi users, MCP enables seamless integration between AI assistants and embedded simulation.
 
 ## Wokwi MCP Server