What is the key difference between Srunx and Runno?

Srunx belongs to the Code Execution category with local stdio execution, while Runno belongs to the Code Execution category with local stdio execution.

How do I install Srunx or Runno in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Srunx and Runno free or paid?

Srunx operates under a Free / Open Source model (other). Runno operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Srunx lists 6 tools with 4 views and 18 GitHub stars. Runno lists 0 tools with 0 views and 773 GitHub stars.

Can I use both Srunx and Runno together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Srunx vs Runno

In-depth architectural comparison of the Srunx and Runno MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Srunx

Code Execution · Local stdio

Quality: 56/100 (Good) | Auth: other

Runno

Code Execution · Local stdio

Quality: 48/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Srunx if you need specialized Code Execution tools running via a local process. Choose Runno if your workspace requires Code Execution integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Srunx when:

You need dedicated capabilities in the Code Execution domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
Primary tools included: SLURM job submission and cancellation, YAML workflow DAG execution, GPU and cluster resource monitoring.

Explore Srunx Details

Choose Runno when:

You need dedicated capabilities in the Code Execution domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Runno Details

Feature & Specification Comparison

Specification	Srunx ksterx Code Execution	Runno Code Execution
Summary
Category & Scope	Code Execution	Code Execution
Quality signal

Tools & Capabilities Breakdown

Srunx Tools (6)

SLURM job submission and cancellation

YAML workflow DAG execution

GPU and cluster resource monitoring

SSH profile-based remote execution

Remote file synchronization

Pyxis, Apptainer, and Singularity support

Runno Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Srunx Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ksterx-srunx": {
      "command": "uvx",
      "args": [
        "--from",
        "srunx[mcp]",
        "srunx-mcp"
      ]
    }
  }
}

Runno Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "runno": {
      "command": "npx",
      "args": [
        "@runno/mcp"
      ]
    }
  }
}

Frequently Asked Questions

Srunx is categorized under Code Execution and uses a local stdio subprocess. In contrast, Runno belongs to Code Execution using local stdio subprocess. Select Srunx when you need capabilities focused on code execution and Runno when you require tools for code execution.

More alternatives to Srunx More alternatives to Runno Code Execution category hub