Server Everything vs Shipi18n

A side-by-side look at the Server Everything and Shipi18n MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Server Everything logoServer EverythingOther Tools and Integrations · Local subprocess (stdio)MCP server that exercises all the features of the MCP protocol55GoodAuth: no auth requiredShipi18n logoShipi18nTranslation Services · Local subprocess (stdio)Translation QA for locale files: keyless validators, semantic review and BYO-key translation44FairAuth: not declared

Verdict: choose Server Everything for other tools and integrations work as a local process; choose Shipi18n for translation services as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Server Everything logoChoose Server Everything when

  • You need dedicated capabilities in the Other Tools and Integrations domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Server Everything

Shipi18n logoChoose Shipi18n when

  • You need dedicated capabilities in the Translation Services domain.
  • You prefer a local stdio subprocess transport.
Explore Shipi18n

Feature & specification comparison

Rows where the two servers differ are marked.

SpecServer Everything logoServer EverythingShipi18n logoShipi18n
CategoryOther Tools and IntegrationsTranslation Services
Quality signal55/100 · Good44/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars91,4050
Directory activity 9 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Server Everything tools

No tool names declared yet. Check the project README from the listing page.

Shipi18n tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Server Everything

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "modelcontextprotocol-server-everything": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-everything"
      ]
    }
  }
}

Shipi18n

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "shipi18n": {
      "command": "npx",
      "args": [
        "-y",
        "@shipi18n/cli"
      ]
    }
  }
}

Frequently asked questions

Server Everything is categorized under Other Tools and Integrations and uses a local stdio subprocess. Shipi18n belongs to Translation Services and uses a local stdio subprocess. Pick Server Everything for other tools and integrations work and Shipi18n for translation services.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Server Everything is listed as free. Auth: no auth required. Shipi18n has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add modelcontextprotocol-server-everything and shipi18n as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Server Everything has a quality signal of 55/100 (Good) with 9 views, 0 installs and 91,405 GitHub stars. Shipi18n has 44/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.