Electrik Slate vs OrchestKit Docs MCP

In-depth architectural comparison of the Electrik Slate and OrchestKit Docs MCP 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 Electrik Slate 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 Electrik Slate Details

O

Choose OrchestKit Docs MCP 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 OrchestKit Docs MCP Details

Feature & Specification Comparison

Specification	Electrik Slate Developer Tools	O OrchestKit Docs MCP Developer Tools
Summary	Read-only MCP for Electrik Slate: Blade component docs, blocks gallery, source, and llms.txt.	Read-only MCP server for the OrchestKit docs: full-text search + Markdown fetch. No auth.
Category & Scope	Developer Tools	Developer Tools

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": {
    "electrik-slate": {
      "command": "npx",
      "args": [
        "-y",
        "electrik-slate"
      ]
    }
  }
}

{
  "mcpServers": {
    "orchestkit-docs-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "skills"
      ]
    }
  }
}

Related MCP Server Comparisons