What is the key difference between CleanSlice and WeJob?

CleanSlice belongs to the Developer Tools category with cloud HTTP/SSE execution, while WeJob belongs to the Developer Tools category with cloud HTTP/SSE execution.

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

CleanSlice operates under a Free / Open Source model (No auth required). WeJob operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

CleanSlice lists 4 tools with 0 views and 18 GitHub stars. WeJob lists 8 tools with 1 views and 1 GitHub stars.

Can I use both CleanSlice and WeJob 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 CleanSlice or WeJob 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 CleanSlice and WeJob free to use, or do they require API keys?

CleanSlice is listed under a Free / Open Source model with No auth required . WeJob operates under a Free / Open Source model with No auth required . 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 CleanSlice and WeJob at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both cleanslice and wejob 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, CleanSlice has a Quality Score of 52 /100 ( Good ) with 0 views, 0 installs, and 18 GitHub stars. WeJob holds a Quality Score of 51 /100 ( Good ) with 1 views, 0 installs, and 1 GitHub stars.

Side-by-Side Model Context Protocol Comparison

CleanSlice vs WeJob

In-depth architectural comparison of the CleanSlice and WeJob 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

CleanSlice

Developer Tools · Remote HTTP/SSE

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

WeJob

Developer Tools · Remote HTTP/SSE

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

Verdict Summary: Choose CleanSlice if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose WeJob if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose CleanSlice 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: get-started, list-categories, search.

Explore CleanSlice Details

Choose WeJob 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: search, fetch, wejob_search_jobs.

Explore WeJob Details

Feature & Specification Comparison

Specification	C CleanSlice Developer Tools	WeJob Developer Tools
Summary	Architecture docs and patterns for NestJS + Nuxt full-stack apps	Read-only MCP server for public WeJob jobs, formations, and companies.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

CleanSlice Tools (4)

get-started

Returns the essential CleanSlice rules and conventions. **Call this first.

list-categories

Lists all documentation categories available for search filtering

Search docs by query, category, framework, phase, or tags. Returns **snippets** (keyword-in-context excerpts) and document paths

read-doc

Read the full content of a specific document by path. Use after `search` to get complete docs

WeJob Tools (8)

Unified search across jobs, formations, companies

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

CleanSlice Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "cleanslice": {
      "url": "https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/en/install-mcp?name=cleanslice&config=eyJ1cmwiOiJodHRwczovL21jcC5jbGVhbnNsaWNlLm9yZy9tY3AifQ%3D%3D"
    }
  }
}

WeJob Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "wejob": {
      "url": "https://wejob.ch/mcp-wejob**"
    }
  }
}

Frequently Asked Questions

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

More alternatives to CleanSlice More alternatives to WeJob Developer Tools category hub