What is the key difference between Letswork and Slima?

Letswork belongs to the Developer Tools category with local stdio execution, while Slima belongs to the Developer Tools category with local stdio execution.

How do I install Letswork or Slima 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 Letswork and Slima free or paid?

Letswork operates under a Free / Open Source model (No auth required). Slima operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Letswork lists 14 tools with 0 views and 0 GitHub stars. Slima lists 14 tools with 0 views and 1 GitHub stars.

Can I use both Letswork and Slima 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

Letswork vs Slima

In-depth architectural comparison of the Letswork and Slima 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

Letswork

Developer Tools · Local stdio

Quality: 51/100 (Good) | Auth: No auth required

Slima

Developer Tools · Local stdio

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

Verdict Summary: Choose Letswork if you need specialized Developer Tools tools running via a local process. Choose Slima 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 Letswork 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: list_files, read_file, write_file.

Explore Letswork Details

Choose Slima 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: create_book, list_books, get_book.

Explore Slima Details

Feature & Specification Comparison

Specification	L Letswork Developer Tools	S Slima Developer Tools
Summary	Real-time collaborative coding via MCP — two developers, one codebase	MCP Server for Slima - AI Writing IDE for Novel Authors with AI Beta Reader.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Letswork Tools (14)

list_files

List files and directories with lock status

read_file

Read file contents (1MB limit, text files only)

write_file

Submit a file change (guest changes need host approval)

lock_file

Lock a file for exclusive editing

unlock_file

Release your own file lock

get_status

Show session info, connected users, and active locks

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

Letswork Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "letswork": {
      "command": "uvx",
      "args": [
        "letswork"
      ]
    }
  }
}

Slima Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "slima": {
      "command": "npx",
      "args": [
        "-y",
        "slima-mcp@0"
      ]
    }
  }
}

Frequently Asked Questions

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