everything vs domscribe

Side-by-side comparison to help you pick between these two MCP servers.

	everything by modelcontextprotocol	domscribe by patchorbit
Stars	★ 85,748	★ 168
30d uses	—	—
Score	77	48
Official	✓	—
Categories	Developer ToolsAI / LLM ToolsOther	Developer ToolsAI / LLM ToolsProductivity
Language	TypeScript	TypeScript
Last commit	this month	this month

everything · Summary

Official MCP test server exercising all protocol features for client builders.

domscribe · Summary

Domscribe bridges the gap between running web applications and their source code via MCP, enabling AI agents to view live UI context and make targeted edits.

everything · Use cases

Testing MCP client implementations against all protocol features
Learning MCP protocol capabilities through a reference server
Validating client compatibility with different transport methods

domscribe · Use cases

AI agents inspect live UI state by querying source code locations to understand rendered components
Developers point to UI elements and describe changes in plain English for AI implementation
Cross-framework development with stable DOM-to-source mapping across hot reloads

everything · Install

NPX (recommended)

{
  "mcpServers": {
    "everything": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-everything"]
    }
  }
}

On Windows, use cmd /c:

{
  "mcpServers": {
    "everything": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "@modelcontextprotocol/server-everything"]
    }
  }
}

Docker

{
  "mcpServers": {
    "everything": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "mcp/everything"]
    }
  }
}

Global install

npm install -g @modelcontextprotocol/server-everything@latest
npx @modelcontextprotocol/server-everything

domscribe · Install

Install using the setup wizard:

npx domscribe init

This will walk you through connecting your coding agent and adding to your app. For manual setup:

Add to your bundler/framework (example for React with Vite):

npm install -D @domscribe/react

// vite.config.ts
import { defineConfig } from 'vite';
import react from '@vitejs/plugin-react';
import { domscribe } from '@domscribe/react/vite';

export default defineConfig({
  plugins: [react(), domscribe()],
});

Connect your coding agent (example for Claude Desktop):

Add to Claude's config.json:

{
  "mcpServers": {
    "domscribe": {
      "command": "npx",
      "args": ["domscribe", "mcp"]
    }
  }
}

Comparison generated from public README + GitHub signals. Last updated automatically.