Skip to main content
Glama
mumez

pharo-nc-mcp-server

by mumez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PHARO_DIRNoPath to Pharo installation directory (default: ~/pharo)~/pharo

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": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
evaluate_smalltalk_with_neo_consoleC
Evaluate a Pharo Smalltalk expression using NeoConsole.

Args:
    expression: The Smalltalk expression to evaluate
    command: The NeoConsole command to use (default: eval)

Returns:
    The result of the evaluation
quit_neo_consoleA
Send quit command to NeoConsole to terminate the REPL session.

Returns:
    The result of the quit command
evaluate_simple_smalltalkB
Evaluate a Pharo Smalltalk expression using the simple -e option.

Args:
    expression: The Smalltalk expression to evaluate

Returns:
    The result of the evaluation
get_pharo_metricC
Get a system metric from Pharo using NeoConsole.

Args:
    metric: The metric to retrieve (e.g., 'system.status', 'memory.free')

Returns:
    The metric value
install_packageB
Install a Pharo package using Metacello.

Args:
    baseline: The baseline name of the package (e.g., 'Historia')
    repository: The repository URL (e.g., 'github://mumez/Historia:main/src')

Returns:
    The result of the package installation
get_class_commentC
Get the comment of a Pharo class.

Args:
    class_name: The name of the class to get the comment for

Returns:
    The class comment
get_class_definitionB
Get the definition of a Pharo class.

Args:
    class_name: The name of the class to get the definition for

Returns:
    The class definition
get_method_listB
Get the list of method selectors for a Pharo class.

Args:
    class_name: The name of the class to get method selectors for

Returns:
    The list of method selectors
get_method_sourceA
Get the source code of a specific method in a Pharo class.

Args:
    class_name: The name of the class
    selector: The method selector (message name)

Returns:
    The method source code
get_neo_console_command_historyA
Get the command history from the current NeoConsole session.

Returns:
    The command history as a string, showing numbered entries of previously executed commands
shutdown_repl_sessionB
Shutdown the persistent NeoConsole REPL session and server.

Returns:
    The result of the shutdown operation

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

B3.3/5.0

Scored across 11 tools

Disambiguation3/5

Most tools have distinct purposes, but there is significant overlap between the two evaluation tools (evaluate_simple_smalltalk and evaluate_smalltalk_with_neo_console) which could cause confusion. The two shutdown tools (quit_neo_console and shutdown_repl_session) also have unclear boundaries, though their descriptions provide some differentiation.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern with snake_case throughout. The naming convention is predictable and readable, with clear action-object relationships (e.g., get_class_comment, install_package, shutdown_repl_session).

Tool Count4/5

With 11 tools, the count is reasonable for a Pharo development server. However, there is some redundancy (two evaluation tools, two shutdown tools) that suggests the count could be slightly optimized without losing functionality.

Completeness3/5

The toolset covers core Pharo development operations like class/method inspection, package installation, and system metrics, but has notable gaps. There are no tools for creating or modifying classes/methods, running tests, or managing the Pharo image beyond shutdown operations, which limits workflow coverage.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources