quartus91-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QUARTUS91_ROOT | Yes | Path to the Quartus II 9.1 installation directory, e.g., C:\altera\91\quartus |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| quartus_infoA | Detect the Quartus II 9.1 installation, executable paths, version output, and license-related environment. |
| quartus_list_projectsB | Find .qpf projects under a directory and parse their revisions. |
| quartus_inspect_projectB | Parse a Quartus .qpf/.qsf project and summarize revisions, device, top entity, source files, SDCs, and assignments. |
| quartus_list_board_presetsA | List built-in board presets derived from existing Quartus projects, including default device settings and named pin resources. |
| quartus_extract_project_templateB | Extract reusable project defaults, source assignments, simulation settings, and pin assignments from an existing Quartus .qpf/.qsf project. |
| quartus_create_projectA | Create a Quartus project/revision with device, top entity, HDL/SDC files, pin assignments, and generic assignments using Quartus Tcl. |
| quartus_set_pinsB | Apply direct pin assignments or board-preset resource bindings to an existing Quartus project using set_location_assignment. |
| quartus_run_flowC | Run quartus_sh --flow for a project, such as compile or early_timing_estimate. |
| quartus_run_stageB | Run one Quartus command-stage executable such as quartus_map, quartus_fit, quartus_asm, quartus_sta, or quartus_pgm-adjacent tools. |
| quartus_run_tclB | Run a Quartus Tcl command, inline script, or script file through quartus_sh. |
| quartus_generate_vwfB | Generate a Quartus II Vector Waveform File (.vwf) from structured simulation requirements: signals, clocks, pulses, point events, and bus sequences. Optionally attach it to a project as VECTOR_WAVEFORM_FILE/VECTOR_INPUT_SOURCE. |
| quartus_simulate_vwfB | Run Quartus II simulation using a .vwf/.cvwf/.vec/.tbl/.scf/.vcd vector source. For functional simulation, it can first generate the functional simulation netlist with quartus_map. |
| quartus_read_reportC | Read and summarize a Quartus report/summary file from a project directory. |
| quartus_list_hardwareB | List available Quartus programming hardware and JTAG chains using quartus_pgm and jtagconfig. |
| quartus_program_deviceB | Program a device through quartus_pgm using a CDF file or explicit programming operations. |
| quartus_open_guiA | Launch the Quartus GUI, optionally opening a project. This starts a detached visible process. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/alglb123/quartus91-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server