What is the key difference between Code Health Suite and Sem?

Code Health Suite belongs to the Developer Tools category with local stdio execution, while Sem belongs to the Developer Tools category with local stdio execution.

How do I install Code Health Suite or Sem in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Code Health Suite and Sem free or paid?

Code Health Suite operates under a Free / Open Source model (No auth required). Sem operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Code Health Suite lists 0 tools with 0 views and 0 GitHub stars. Sem lists 0 tools with 1 views and 3,334 GitHub stars.

Can I use both Code Health Suite and Sem together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Code Health Suite vs Sem

In-depth architectural comparison of the Code Health Suite and Sem 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.

At a Glance & Executive Verdict

Code Health Suite

Developer Tools · Local stdio

Quality: 35/100 (Fair) | Auth: No auth required

Sem

Developer Tools · Local stdio

Quality: 49/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Code Health Suite if you need specialized Developer Tools tools running via a local process. Choose Sem if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Code Health Suite 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).

Explore Code Health Suite Details

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

Explore Sem Details

Feature & Specification Comparison

Specification	Code Health Suite Developer Tools	Sem Developer Tools
Summary	16 engines, 28 MCP tools for Python code quality. Zero external dependencies.	Entity-level code intelligence: semantic diff, impact analysis, blame, and context for AI agents
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Code Health Suite Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Sem Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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

Code Health Suite Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "code-health-suite": {
      "command": "uvx",
      "args": [
        "code-health-suite"
      ]
    }
  }
}

Sem Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "sem": {
      "command": "npx",
      "args": [
        "-y",
        "sem"
      ]
    }
  }
}

Frequently Asked Questions

Code Health Suite is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Sem belongs to Developer Tools using local stdio subprocess. Select Code Health Suite when you need capabilities focused on developer tools and Sem when you require tools for developer tools.

More alternatives to Code Health Suite More alternatives to Sem Developer Tools category hub