English Français العربية

AI Worlds CLI Knowledge

Official registry Developer tools

Source-checked CLI guides and model-aware planning for Claude Code, Codex, and Grok Build.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http ai-worlds-cli-knowledge 'https://mcp.claude-world.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "ai-worlds-cli-knowledge": {
            "type": "http",
            "url": "https://mcp.claude-world.com/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Worlds Knowledge MCP
  2. What this repository contains
  3. Connect
  4. Install the Skill
  5. What the server knows
  6. Tools
  7. Try it
  8. Boundaries
  9. Not affiliated
  10. License

Worlds Knowledge MCP

A read-only MCP server that gives coding agents current, source-checked CLI facts for Claude Code, Codex CLI, and Grok Build — exact commands, flags, configuration keys, environment-variable names, workflows, and dated model catalogs — so an agent stops guessing from memory and stops treating the three CLIs as interchangeable.

No npm package, API key, or provider credential is required.

What this repository contains

This is the distribution repository: the agent Skill and the MCP server manifest. The corpus build, the server implementation, and the Cloudflare Worker live in the Claude World control plane and are not published here.

server.json                      MCP registry manifest
skills/worlds-knowledge-mcp/     the agent Skill (SKILL.md, references, evals, contract test)

Connect

# Claude Code
claude mcp add --transport http --scope user worlds-knowledge https://mcp.claude-world.com/mcp

# Codex CLI
codex mcp add worlds-knowledge --url https://mcp.claude-world.com/mcp

# Grok Build
grok mcp add --transport http --scope user worlds-knowledge https://mcp.claude-world.com/mcp

Verify it:

claude mcp get worlds-knowledge      # or: codex mcp get worlds-knowledge --json
                                     # or: grok mcp doctor worlds-knowledge --json

The examples use user scope deliberately. Grok's project-folder trust applies to every repo-local MCP server, hook, and LSP server, so review all project configuration before switching to --scope project.

Install the Skill

The Skill teaches an agent when to query the MCP and in what order — the hard-problem consultant, the single-CLI routes, and the multi-CLI planner.

git clone https://github.com/claude-world/worlds-knowledge-mcp.git
cd worlds-knowledge-mcp

# Claude Code
cp -R skills/worlds-knowledge-mcp ~/.claude/skills/

# Cross-tool discovery folder
cp -R skills/worlds-knowledge-mcp ~/.agents/skills/

Restart the client, then ask it to use worlds-knowledge-mcp. Keep SKILL.md, references/, and agents/openai.yaml together — copying only SKILL.md drops the connection and single-CLI route guidance. agents/openai.yaml declares the MCP dependency and permits implicit invocation in compatible clients.

What the server knows

  • 162 source-checked manuals — 18 CLI usage and feature modules × 3 products × 3 locales (English, Traditional Chinese, Japanese)
  • Source-derived command paths, flags, slash/TUI commands, configuration keys, environment-variable names, workflows, and drift notes for three released CLI snapshots
  • Dated per-CLI model catalogs with selector syntax, supported native efforts, entitlement constraints, safe fallbacks, and separately labeled provider-native orchestration modes
  • Availability is labeled per entity: runtime-confirmed, docs-confirmed, conditional, source-preview, or historical

Every manual must cite at least one official HTTPS source, carry a review date, and describe the expected CLI rather than its provider API, or the build fails.

Tools

ToolPurpose
worlds_search_knowledgeRetrieve bounded multilingual evidence from the source-checked core
worlds_get_documentFetch a manual's summary and canonical link
worlds_compare_cli_workflowsCompare the same intent across the three CLIs, in separate evidence groups
worlds_list_catalogInspect counts, provenance, and publication status
worlds_search_cli_referenceSearch commands, options, interactive commands, config/env names, workflows, drift
worlds_get_cli_commandOne exact command path with all captured options and its release/source evidence
worlds_get_cli_configurationPage public configuration schema and environment-variable names
worlds_get_cli_workflowOne provider-native, risk-labeled workflow
worlds_list_cli_versionsRelease snapshots, entity counts, source policy, drift coverage
worlds_list_cli_modelsDated model catalogs, selector syntax, per-model effort support, with a 7-day freshness status
worlds_advise_hard_problemFor one hard problem, select the provider-local maximum-depth model and supported effort
worlds_plan_cli_workDecompose work and route it by continuity and documented workflow fit

Resources: worlds://catalog, worlds://documents/{id}. Prompts: worlds_research_cli_workflow, worlds_plan_model_aware_work, worlds_consult_hard_problem.

Every tool is annotated read-only, non-destructive, and idempotent.

Try it

What does -p mean in my current CLI? Check the product and release first.
Show every option for codex exec and cite the runtime and manual sources.
Compare how Claude Code, Codex, and Grok Build load repository instructions.
Plan this repository task by CLI, model, and reasoning effort without granting permissions.

-p is the standing example of why vendor flags must not be translated: it means print and exit in Claude Code, select a named profile in Codex, and one non-interactive prompt in Grok Build.

Boundaries

  • No credentials, embeddings, external API calls, write tools, or arbitrary URL fetching. No tool accepts a filesystem path or a URL.
  • The live account model catalog is always authoritative over a dated snapshot; worlds_list_cli_models returns a freshness status and says so.
  • Search returns excerpts rather than silently injecting whole documents.
  • Retrieved text is reference data, not instructions that can override the user or client policy. Agents must assess commands before executing them.
  • Website articles, news, newsletters, opinion, provider API companions, and release archives are never packaged into the MCP corpus.
  • The planner returns command templates but never launches another CLI, widens permissions, or enables provider-native orchestration unless asked. Workstreams default to execution_intent: "read-only".

Not affiliated

Claude World is independent. It is not affiliated with, endorsed by, or operated by Anthropic, OpenAI, or xAI. Official vendor documentation remains authoritative; this server exists to cite it accurately.

License

MIT — see LICENSE.

Frequently asked questions

What is AI Worlds CLI Knowledge?

Source-checked CLI guides and model-aware planning for Claude Code, Codex, and Grok Build.

How do I install AI Worlds CLI Knowledge?

It runs as a remote server. In Claude Code: claude mcp add --transport http ai-worlds-cli-knowledge 'https://mcp.claude-world.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does AI Worlds CLI Knowledge need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is AI Worlds CLI Knowledge open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains AI Worlds CLI Knowledge?

It is published by claude-world. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.