MCP Gopls vs Pharo Smalltalk Interop MCP Server

In-depth architectural comparison of the MCP Gopls and Pharo Smalltalk Interop MCP Server 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.

Which MCP Server Should You Choose?

Choose MCP Gopls when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Go LSP navigation and workspace symbol search, Diagnostics, hover, completion, formatting, and code actions, Symbol renaming through MCP.

Explore MCP Gopls Details

Choose Pharo Smalltalk Interop MCP Server when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• You have access to required keys: PHARO_SIS_PORT.
• Primary tools included: eval, get_class_source, get_method_source.

Feature & Specification Comparison

Specification	MCP Gopls hloiseaufcms Developer Tools	Pharo Smalltalk Interop MCP Server mumez Developer Tools
Summary	A MCP server for interacting with Go's Language Server Protocol (gopls) and benefit from advanced Go code analysis features.	Pharo Smalltalk integration enabling code evaluation, class/method introspection, package management, test execution, and project installation for interactive development with Pharo images.
Category & Scope

Tools & Capabilities Breakdown

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).

{
  "mcpServers": {
    "hloiseaufcms-mcp-gopls": {
      "command": "npx",
      "args": [
        "-y",
        "@mark3labs/mcp-inspector"
      ]
    }
  }
}

{
  "mcpServers": {
    "mumez-pharo-smalltalk-interop-mcp-server": {
      "command": "uvx",
      "args": [
        "--from"
      ],
      "env": {
        "PHARO_SIS_PORT": "YOUR_PHARO_SIS_PORT_HERE"
      }
    }
  }
}

Related MCP Server Comparisons