What is the key difference between Dazzle and Slima?

Dazzle belongs to the Developer Tools category with cloud HTTP/SSE execution, while Slima belongs to the Developer Tools category with local stdio execution.

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

Dazzle 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?

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

Can I use both Dazzle 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

Dazzle vs Slima

In-depth architectural comparison of the Dazzle 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

Dazzle

Developer Tools · Remote HTTP/SSE

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

Slima

Developer Tools · Local stdio

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

Verdict Summary: Choose Dazzle if you need specialized Developer Tools tools running via a hosted cloud SSE transport. 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 Dazzle when:

You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: cli, edit_file, guide.

Explore Dazzle 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	Dazzle Developer Tools	S Slima Developer Tools
Summary	Cloud stages for AI agents and live streaming. Create, manage, and broadcast content.	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

Dazzle Tools (8)

cli

Run a dazzle CLI command. Use ["--help"] to discover available commands. Output is JSON.

edit_file

Edit a file in the stage workspace by exact string replacement. The old_string must match exactly once in the file. Use read_file first to see the current content.

guide

Get the complete Dazzle reference — getting started, CLI commands, content capabilities, and streaming setup. Read this before creating or modifying stage content.

list_files

List all files in the stage workspace (~/.dazzle/stages/{stage}/). Returns relative paths, one per line.

read_file

Read a file from the stage workspace (~/.dazzle/stages/{stage}/{path}).

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

Dazzle Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "dazzle": {
      "url": "https://dazzle.fm"
    }
  }
}

Slima Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Dazzle is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Slima belongs to Developer Tools using local stdio subprocess. Select Dazzle when you need capabilities focused on developer tools and Slima when you require tools for developer tools.