Skip to main content
Glama
bobbyhiddn

Sympathy-MCP

by bobbyhiddn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
vm_execA

Execute a command on a remote host via SSH.

Runs the command via `sh -c` so shell features (pipes, redirects, etc.)
work as expected. Captures both stdout and stderr.

Args:
    vm: Name of the host (as configured in hosts.toml).
    command: Shell command to execute.
    workdir: Working directory on the remote host (default: /).
    timeout: Maximum seconds to wait (default: 120).

Returns:
    Command output with stdout, stderr, and exit code.
vm_file_readA

Read a file from a remote host via SSH.

Args:
    vm: Name of the host (as configured in hosts.toml).
    path: Absolute path to the file on the remote host.

Returns:
    File contents as a string, or an error message.
vm_file_writeA

Write content to a file on a remote host via SSH.

Handles arbitrary content safely by piping through SSH stdin.

Args:
    vm: Name of the host (as configured in hosts.toml).
    path: Absolute path where the file should be written.
    content: The content to write to the file.

Returns:
    Success confirmation or error message.
vm_file_pushA

Push a file from the local host to a remote host via SCP.

Args:
    vm: Name of the host (as configured in hosts.toml).
    local_path: Path to the file on the local host.
    remote_path: Absolute destination path on the remote host.

Returns:
    Success confirmation or error message.
vm_file_pullA

Pull a file from a remote host to the local host via SCP.

Args:
    vm: Name of the host (as configured in hosts.toml).
    remote_path: Absolute path to the file on the remote host.
    local_path: Destination path on the local host.

Returns:
    Success confirmation or error message.
vm_snapshotA

Create a snapshot of a VM/container (Incus).

Args:
    vm: Name of the VM or container.
    name: Name for the snapshot (alphanumeric, hyphens, underscores).

Returns:
    Success confirmation or error message.
vm_restoreB

Restore a VM/container to a named snapshot (Incus).

Args:
    vm: Name of the VM or container.
    snapshot: Name of the snapshot to restore.

Returns:
    Success confirmation or error message.
vm_statusA

Get the status of a VM/container (Incus).

Returns state (running/stopped), IP address, resource usage,
and available snapshots.

Args:
    vm: Name of the VM or container.

Returns:
    Formatted status information or error message.
vm_listA

List all available VMs and containers with their status (Incus).

Returns:
    Formatted list of all instances, or a message if none exist.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 9 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity. The tools cover separate operations: command execution, file transfer (pull/push), file reading/writing, listing instances, snapshot management, and status checking. The descriptions clearly differentiate between these functions, making misselection unlikely.

Naming Consistency5/5

All tools follow a consistent 'vm_' prefix with descriptive action suffixes (e.g., vm_exec, vm_file_pull, vm_snapshot). The naming pattern is perfectly uniform throughout the set, using snake_case consistently without any deviations or mixed conventions.

Tool Count5/5

With 9 tools, this is well-scoped for remote host/VM management. Each tool earns its place by covering essential operations like execution, file management, snapshot handling, and status monitoring. The count is neither too thin nor excessive for the domain.

Completeness5/5

The toolset provides complete coverage for remote VM/container management. It includes execution, bidirectional file transfer, file reading/writing, instance listing, snapshot creation/restoration, and status checking. There are no obvious gaps or missing operations that would hinder agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources