Enterprise DNAEnterprise DNA

MCP Servers

mumez/pharo-smalltalk-interop-mcp-server

A local MCP server to communicate local Pharo Smalltalk image

Visit site ↗

Our verdict

Not reviewed yet

We have not reviewed mumez/pharo-smalltalk-interop-mcp-server yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About mumez/pharo-smalltalk-interop-mcp-server

A local MCP server that enables communication with a Pharo Smalltalk image. It uses Python to bridge the Model Context Protocol, allowing external tools to interact with the Smalltalk environment.

Best for

Developers working with Pharo Smalltalk who want to connect it to MCP-based tools or AI assistants

Use cases

  • Connecting AI assistants to a live Pharo Smalltalk image for code analysis
  • Automating Smalltalk image operations from external scripts or tools
  • Integrating Pharo Smalltalk into MCP-compatible development workflows

Notes

10 stars on GitHub. Last updated 2025-12-19. Licensed MIT.

Pros

  • Enables modern tooling integration with legacy Smalltalk environments
  • Lightweight Python implementation with a focused scope
  • Open source with a permissive license for customization

Cons

  • Very early stage with only 10 stars and limited community adoption
  • Requires running a local server and managing Smalltalk image connectivity
  • Narrow use case limited to Pharo Smalltalk developers

Key facts

What we have checked

Days since the last commit
79
Checked GitHub
GitHub forks
10
Checked GitHub
GitHub stars
12
Checked GitHub
Open issues
2
Checked GitHub
Releases in the last 90 days
0
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

How to use

How to set it up

As the listing publishes it. We have not run this install.

Install

uvx --from git+https://github.com/mumez/pharo-smalltalk-interop-mcp-server.git pharo-smalltalk-interop-mcp-server

Tools exposed

  • eval
  • get_class_source
  • get_method_source
  • get_class_comment
  • search_classes_like
  • search_methods_like
  • search_traits_like
  • search_implementors
  • search_references
  • search_references_to_class
  • list_packages
  • list_classes
  • list_extended_classes
  • list_methods
  • export_package
  • import_package
  • install_project
  • run_package_test
  • run_class_test
  • read_screen

Clients the listing names (not checked here)

Cursor, Claude Code

Example client config

{
  "mcpServers": {
    "smalltalk-interop": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/mumez/pharo-smalltalk-interop-mcp-server.git",
        "pharo-smalltalk-interop-mcp-server"
      ],
      "env": {
        "PHARO_SIS_PORT": "8086"
      }
    }
  }
}

Install

Add mumez/pharo-smalltalk-interop-mcp-server to your client

Not verified yet

No install recipe yet. We write one for Claude Code, Claude Desktop, Cursor, VS Code, Codex and ChatGPT when the server is in the official MCP registry with a package or remote address we can use.

Until then, follow the project's own README, or the setup the listing publishes under How to set it up.

Works with

What mumez/pharo-smalltalk-interop-mcp-server connects to

No confirmed connections yet. A product appears here when the server's registry name, repo, homepage or name ties it to that product, and a client appears when we have an install recipe for it.

Health and security

Is mumez/pharo-smalltalk-interop-mcp-server looked after, and what do its setup files show

Health score

0 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Archived0Repository is archived

Security check static checks

100 out of 100

Reads what is published about the server: package advisories, licence, secrets in the documented setup and tool permissions. Nothing is installed or run, so this is not a security assessment. Checked by edna-static-v1. What it checks

Licence: MIT

  • Note No published npm or PyPI package of this repository was found, so package advisories were not checked.
  • Note The lab has not recorded this server's tool list yet, so tool permissions were not checked.
Tool permissions (1)
  • PHARO_SIS_PORT, environment variable it asks for

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

  1. Shut down

    Source: GitHub

Pairs with

Other entries in the index that connect to this one. Click through to see the chain.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.

← Back to MCP ServersSubmit your own entry →