Saltar al contenido
Logo de ClaudeWorld

Servidor MCP de ClaudeWorld

Qué servidores del registro oficial de MCP son de ClaudeWorld, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-16

← Volver a ClaudeWorld

De quién es el servidor
  • Nombre en el registrocom.claude-world/worlds-knowledgeverificado en el registro MCP

El nombre en el registro está bajo claude-world.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

Cuando le preguntamoscomprobado el 2026-10-16
  • Estadorespondecomprobado el 2026-10-16
  • Herramientas12
  • El servidor se llamaworlds-knowledge-mcp-server
  • Versión del servidor0.5.0
  • Versión del protocolo2025-06-18

El 2026-10-16 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 135 ms.

Herramientas que ofrece12 herramientas · leído el 2026-10-16
  • worlds_search_knowledge

    Search 162 multilingual, source-checked operating manuals for Claude Code, Codex, and Grok Build: 18 CLI usage and feature modules per product in English, Traditional Chinese, and Japanese. Website articles, news, newsletters, opinion…

  • worlds_get_document

    Read the bounded public excerpt and metadata for one source-checked CLI manual returned by worlds_search_knowledge. Follow canonical_url for the complete manual. Structured CLI command tools remain complete.

  • worlds_compare_cli_workflows

    Find evidence for the same task across Claude Code, Codex, and Grok Build without pretending their commands or authority models are identical. Returns separately ranked groups with source dates and canonical links. Best for questions such…

  • worlds_list_catalog

    Return public corpus counts, supported worlds, languages, products, source-quality counts, the build commit, and the current publication gate. This public DTO deliberately excludes local paths, package names, and private repository URLs.

  • worlds_search_cli_reference

    Search current command paths, flags, interactive commands, configuration names, environment-variable names, workflows, and release drift for Claude Code, Codex, and Grok Build. Results contain factual metadata and official source links.

  • worlds_get_cli_command

    Return one current command path with all captured flags, arguments, value shapes, availability, risk, release metadata, and official source links. Accepts a stable id or full command path.

  • worlds_get_cli_configuration

    Search configuration keys and environment-variable names for one CLI. Returns public schema metadata and source links, never local values.

  • worlds_get_cli_workflow

    Find one provider-specific workflow and its recorded command steps without translating flags between providers.

  • worlds_list_cli_versions

    Return the exact release snapshot, capture date, factual entity counts, official sources, generated website reference, and drift status for all three CLIs.

  • worlds_list_cli_models

    Return dated, source-grounded model catalogs for Claude Code, Codex, and Grok Build, including selector syntax, per-model effort support, availability constraints, and provider-native orchestration modes. These are snapshots; verify the…

  • worlds_plan_cli_work

    Create a read-only, dependency-aware work plan across Claude Code, Codex, and Grok Build. It selects a concrete dated-catalog model and supported native effort for each workstream, while keeping CLI fit, orchestration, permissions…

  • worlds_advise_hard_problem

    Choose the maximum-depth model-and-effort pairing for one difficult problem within the caller's actual CLI set. For a single CLI it selects that provider's strongest catalog role; with multiple CLIs it returns provider candidates but does…

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

{
  "mcpServers": {
    "worlds-knowledge": {
      "type": "http",
      "url": "https://mcp.claude-world.com/mcp"
    }
  }
}

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.