What is the key difference between Devilge and Yutu?

Devilge belongs to the Browser Automation category with local stdio execution, while Yutu belongs to the Browser Automation category with local stdio execution.

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

Devilge operates under a Free / Open Source model (No auth required). Yutu operates under a BYOK (Pay Provider Direct) model (OAuth 2.0).

Which MCP server has more tools and community activity?

Devilge lists 0 tools with 0 views and 0 GitHub stars. Yutu lists 5 tools with 4 views and 606 GitHub stars.

Can I use both Devilge and Yutu 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.

How do I install Devilge or Yutu in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Devilge and Yutu free to use, or do they require API keys?

Devilge is listed under a Free / Open Source model with No auth required . Yutu operates under a BYOK (Pay Provider Direct) model with OAuth 2.0 . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Devilge and Yutu at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both devilge and eat-pray-ai-yutu as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Devilge has a Quality Score of 27 /100 ( Emerging ) with 0 views, 0 installs, and 0 GitHub stars. Yutu holds a Quality Score of 51 /100 ( Good ) with 4 views, 0 installs, and 606 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Devilge vs Yutu

In-depth architectural comparison of the Devilge and Yutu 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

Devilge

Browser Automation · Local stdio

Quality: 27/100 (Emerging) | Auth: No auth required

Yutu

Browser Automation · Local stdio

Quality: 51/100 (Good) | Auth: OAuth 2.0

Verdict Summary: Choose Devilge if you need specialized Browser Automation tools running via a local process. Choose Yutu if your workspace requires Browser Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Devilge when:

You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).

Explore Devilge Details

Choose Yutu when:

You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (BYOK (Pay Provider Direct)).
You have access to required keys: YUTU_CREDENTIAL, YUTU_CACHE_TOKEN, YUTU_ROOT.
Primary tools included: YouTube Data API v3 integration for video and channel management, OAuth 2.0 authentication with token caching, CLI and MCP server interfaces for automation.

Explore Yutu Details

Feature & Specification Comparison

Specification	D Devilge Browser Automation	Yutu eat-pray-ai Browser Automation
Summary	Android/KMM MCP server: logcat, ADB device control, Compose previews, network, Maestro flows.	A fully functional MCP server and CLI for YouTube to automate YouTube operation
Category & Scope	Browser Automation	Browser Automation
Quality signal

Tools & Capabilities Breakdown

Devilge Tools (0)

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

Yutu Tools (5)

YouTube Data API v3 integration for video and channel management

OAuth 2.0 authentication with token caching

CLI and MCP server interfaces for automation

Support for YouTube Analytics and Reporting APIs (optional)

Configurable credential and token paths via environment variables

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

Devilge Configuration

mcpServers (Claude Desktop / Cursor)

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

Yutu Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "eat-pray-ai-yutu": {
      "command": "npx",
      "args": [
        "-y",
        "skills"
      ],
      "env": {
        "YUTU_CREDENTIAL": "YOUR_YUTU_CREDENTIAL_HERE",
        "YUTU_CACHE_TOKEN": "YOUR_YUTU_CACHE_TOKEN_HERE",
        "YUTU_ROOT": "YOUR_YUTU_ROOT_HERE"
      }
    }
  }
}

Frequently Asked Questions

Devilge is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Yutu belongs to Browser Automation using local stdio subprocess. Select Devilge when you need capabilities focused on browser automation and Yutu when you require tools for browser automation.

More alternatives to Devilge More alternatives to Yutu Browser Automation category hub