Skip to main content
Glama
HPC-MCP

HPC-MCP

by TomMelt

hpc-mcp :zap::computer:

This project provides MCP tools for HPC. These are designed to integrate with LLMs. My initial plan is to integrate with LLMs called from IDEs such as cursor and vscode.

Quick Start Guide :rocket:

This project uses uv for dependency management and installation. If you don't have uv installed, follow installation instructions on their website.

Once we have uv installed we can install the dependencies and run the tests with the following command:

uv run --dev pytest

Adding the MCP Server

Cursor

  1. Open Cursor and go to settings.

  2. Click Tools & Integrations

  3. Click Add Custom MCP

NOTE

This will open your system-wide MCP settings ($HOME/.cursor/mcp.json). If you prefer to set this on a project-by-project basis, then you can create a local configuration using <path/to/project/root>/.cursor/mcp.json.

  1. Add the following configuration:

{
  "mcpServers": {
    "hpc-mcp": {
      "command": "uv",
      "args": [
                "--directory",
                "<path/to>/hpc-mcp",
                "run",
                "src/debug.py"
            ]
    }
  }
}

VSCode

  1. Open command palette (Ctrl+Shift+p) and select MCP: Add Server...

add MCP server

  1. Choose the option command (stdio) since the server will be run locally

  2. Type the command to run the MCP server:

uv --directory <path/to>/hpc-mcp run src/debug.py
  1. Select reasonable name for the server e.g. "HpcMcp" (camel case is a convention)

  2. Select whether to add the server locally or globally.

  3. You can tune the settings by opening setting.json (global settings) or .vscode/setting.json (workspace settings)

add MCP server

Zed

  1. Open Zed and go to settings.

  2. Open general settings CTRL-ALT-C

  3. Under section Model Context Protocol (MCP) Servers click Add Custom Server

  4. Add the following text (changing the <path/to>/hpc-mcp to your actual path)

{
  /// The name of your MCP server
  "hpc-mcp": {
    /// The command which runs the MCP server
    "command": "uv",
    /// The arguments to pass to the MCP server
    "args": [
      "--directory",
      "<path/to>/hpc-mcp",
      "run",
      "src/debug.py"
    ],
    /// The environment variables to set
    "env": {}
  }
}

Test the MCP Server

Test the MCP using our simple example

  • open terminal

  • cd example/simple

  • build the example using make

  • this should generate segfault.exe

  • then type the following prompt into your IDE LLM agent

"debug a crash in the program examples/simple/segfault.exe"
  • this should ask your permission to run debug_crash MCP tool

  • accept and you should get a response like the following cursor-demo

Related MCP server: jlab-mcp

Running local LLMs with Ollama

To run the hpc-mcp MCP tool with a local Ollama model use the Zed text editor. It should automatically detect local running ollama models and make them available. As long as you have installed the hpc-mcp MCP server in zed (see instructions here) it should be available to your models. For more info on ollama integration with zed see zed's documentation.

NOTE

Not all models support calling of MCP tools. I managed to have success withqwen3:latest.

Core Dependencies

  • python

  • uv

  • fastmcp

Available Tools

1 tool
debug_crashC

Debug crashing program and return the stack trace.

Inputs: target (required), args (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly defined and distinct by default.

    Naming Consistency5/5

    Since there is only one tool, naming consistency is inherently perfect—there are no other tools to create inconsistency or mixed conventions. The tool name follows a clear verb_noun pattern.

    Tool Count2/5

    A single tool is too few for a server named 'HPC-MCP', which suggests a High-Performance Computing domain that typically involves complex workflows like job submission, monitoring, and resource management. This minimal toolset severely limits functionality.

    Completeness1/5

    The tool surface is severely incomplete for an HPC domain; it only provides a debug function, missing essential operations such as job submission, status checking, file management, and resource allocation, which are core to HPC workflows.

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      C
      maintenance
      An MCP server that enables LLMs to execute Python code on GPU-accelerated compute nodes within SLURM-managed HPC environments. It bridges local clients to remote clusters by launching JupyterLab sessions via SLURM jobs to facilitate high-performance notebook-based computation.
      7
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      An MCP server and VS Code extension that enables AI clients to interactively debug code using breakpoints, execution control, and state inspection. It is language-agnostic and works with any debugger that supports VS Code's launch.json configurations.
      -
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI assistants to control GDB debugging sessions, including breakpoint management, thread analysis, and variable inspection, using the GDB/MI protocol.
      22
      1
      MIT