HPC-MCP
Allows running the MCP server with local LLM models through Ollama, with specific support for models like qwen3 that can utilize MCP tools
Used for testing the MCP server functionality and ensuring proper integration with HPC tools
Serves as a core dependency for the MCP server, enabling development and execution of HPC-focused tools
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@HPC-MCP debug the crash in my MPI program at examples/mpi/crash.exe"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 pytestAdding the MCP Server
Cursor
Open Cursor and go to settings.
Click
Tools & IntegrationsClick
Add Custom MCP
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.
Add the following configuration:
{
"mcpServers": {
"hpc-mcp": {
"command": "uv",
"args": [
"--directory",
"<path/to>/hpc-mcp",
"run",
"src/debug.py"
]
}
}
}VSCode
Open command palette (Ctrl+Shift+p) and select
MCP: Add Server...

Choose the option
command (stdio)since the server will be run locallyType the command to run the MCP server:
uv --directory <path/to>/hpc-mcp run src/debug.pySelect reasonable name for the server e.g. "HpcMcp" (camel case is a convention)
Select whether to add the server locally or globally.
You can tune the settings by opening
setting.json(global settings) or.vscode/setting.json(workspace settings)

Zed
Open Zed and go to settings.
Open general settings
CTRL-ALT-CUnder section Model Context Protocol (MCP) Servers click
Add Custom ServerAdd the following text (changing the
<path/to>/hpc-mcpto 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/simplebuild the example using
makethis should generate
segfault.exethen 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_crashMCP toolaccept and you should get a response like the following

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.
Not all models support calling of MCP tools. I managed to have success withqwen3:latest.
Core Dependencies
pythonuvfastmcp
Available Tools
1 tooldebug_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
Scored across 1 tool
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.
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.
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.
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
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP Server for Slima - AI Writing IDE for Novel Authors with AI Beta Reader.
Shared memory MCP server for Claude Code, Codex, Gemini CLI and Cursor. Cited, editable.
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP (Model Context Protocol) server that enables interactive debugging with code instrumentation for AI coding assistants. Inspired by Cursor's debug mode.76 npm1MIT
- FlicenseAqualityCmaintenanceAn 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-
- FlicenseNot gradedqualityAmaintenanceAn 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.-
- AlicenseAqualityDmaintenanceAn MCP server that enables AI assistants to control GDB debugging sessions, including breakpoint management, thread analysis, and variable inspection, using the GDB/MI protocol.221MIT