Skip to main content
Glama
manalejandro

MCP ProcFS Server

by manalejandro

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
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
read_procfsC

Read a file from the /proc filesystem

write_procfs

Write a value to a /proc filesystem file

get_cpu_infoB

Get detailed CPU information

get_memory_infoB

Get detailed memory information

get_load_average

Get system load average

get_network_statsC

Get network interface statistics

get_disk_statsC

Get disk I/O statistics

get_process_infoC

Get information about a specific process

list_processes

List all process IDs

read_sysctl

Read a sysctl kernel parameter

write_sysctlB

Write a sysctl kernel parameter

list_sysctlB

List all sysctl parameters

set_process_priorityB

Set process priority (nice value)

set_process_affinityC

Set CPU affinity for a process

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
CPU InformationDetailed CPU information from /proc/cpuinfo
Memory InformationMemory statistics from /proc/meminfo
Load AverageSystem load average from /proc/loadavg
Network StatisticsNetwork interface statistics
Disk StatisticsDisk I/O statistics

TDQS

B3.3/5.0

Scored across 10 tools

Disambiguation4/5

Most tools target clearly distinct resources or actions, such as CPU info, memory info, network stats, and disk stats. The main ambiguity is between the generic read_procfs tool and the specialized get_* wrappers, since raw CPU/memory data could also be fetched via read_procfs.

Naming Consistency4/5

Tool names follow a consistent verb_noun snake_case pattern, with get_, set_, read_, write_, and list_ prefixes. The only minor inconsistency is mixing read_procfs with get_* for similar information-retrieval operations, but the naming remains predictable overall.

Tool Count5/5

Ten tools is a well-scoped size for a /proc filesystem server. Each tool covers a meaningful area of system inspection or tuning without unnecessary redundancy or bloat.

Completeness4/5

The tool set covers reading proc files, retrieving key system metrics, viewing and setting sysctl parameters, and adjusting process scheduling properties. Minor gaps exist, such as no explicit process listing or broader process signal control, but the core /proc workflows are well covered.

Maintenance

ActivityInactive
ResponsivenessNo issues