Execute a TCL command and return the result. This is the primary interface for interacting with Vivado. The command is sent

Truncate response content if it exceeds max_chars. Large Vivado reports can be tens of thousands of lines. Rather than overwhelming the

Start the Vivado TCL session. This spawns a new Vivado process in TCL mode with: - No journal file (-nojournal): Avoids clut

Stop the Vivado session gracefully. Sends the "exit" command to Vivado and waits for the process to terminate. If graceful e

Load feature requests from the persistent JSON file. Feature requests allow the AI assistant to record when it encounters limitations or

Check if the Vivado session is responsive. Sends a simple command to Vivado and checks if it responds within a short timeout

Run the MCP server. This function starts the MCP server using stdio transport (stdin/stdout). It's designed to be launched by an MCP cli

Verify actual Vivado run status instead of relying on output parsing. Vivado run status is stored as properties on the run object. This func

Classify errors based on context - distinguishes real failures from report content that happens to contain 'error' strings. This functio

Check session health and restart if needed. This is the recommended way to recover from session failures. It checks if the s

Ensure the reports directory exists and clean up old reports. This function is called before generating new reports. It: 1. Creates the

Generate a unique 8-character report ID. Uses UUID4 for uniqueness, truncated to 8 chars for readability. The ID is used to reference re

Get the depth of a hierarchical path. Vivado uses "/" to separate hierarchy levels (e.g., "cpu/alu/adder"). This function counts the dep

Get or create the global Vivado session. This function implements the singleton pattern for VivadoSession. The first call creates a new

Get session statistics for monitoring and debugging. Returns: Dictionary containing: - is_running: Whether s

Parse Vivado messages into categorized lists. Vivado outputs messages with severity prefixes: - ERROR: Design or tool errors that must b

Extract structured summary of timing paths from report_timing output. Parses Vivado's timing path reports to extract key information about

Parse a Vivado timing summary report into structured data. Timing summary reports contain critical information about whether the design

Parse a Vivado utilization report into structured data. Utilization reports show how much of each FPGA resource type is used. This is cr

Save a feature request to the persistent JSON file. Args: request: Dictionary containing the feature request with fields:

Context manager entry - start the session. Example: with VivadoSession() as session: session.run_tcl("..

Context manager exit - stop the session. Ensures Vivado is properly shut down even if an exception occurred.

Initialize the Vivado session manager. Args: vivado_path: Path to Vivado executable. Defaults to "vivado" which

Handle tool calls from MCP clients. This is the main dispatcher that routes tool calls to their implementations. Each tool returns a lis

Return True only if this is a real error, not report content.

List all available Vivado tools. This function is called by MCP clients to discover available tools. Tools are organized into categories

Entry point for the vivado-mcp console script. This function is called when running: - vivado-mcp (after pip install) - python -m vi

Reset the global session (stop if running and clear instance). Use this to force a fresh Vivado session, for example after recovering fr