메뉴
Use when calling LLM APIs through the liter-llm MCP server's 22 tools, and to decide when MCP beats the CLI or SDK. Covers the tool surface, the auto-installing launcher, and authentication.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Use when extracting a page needs scripted interaction first — click, type, press a key, scroll, wait, screenshot, or run JS before capturing the DOM. Covers `crawlberg interact <url> --actions` with the real action schema, result shape, limits, and external-CDP options.
Crawl, scrape, and convert websites to Markdown using the local crawlberg CLI and its MCP server. Use when the user wants to fetch a page, follow links across a domain, enumerate URLs, or drive a real browser. Covers installation, the subcommands (scrape, crawl, map, interact, mcp, serve), output formats (JSON + Markdown), browser fallback, and when to prefer the MCP server over shelling out.
Use when the user wants to follow links across a domain and capture every reachable page as Markdown. Covers `crawlberg crawl` with depth, page caps, concurrency, rate limiting, domain scoping, robots, and output selection.
Use when a static fetch returns nothing useful and the page needs a real browser. Covers `--browser-mode auto|always|never`, external CDP via `--browser-endpoint`, symptoms of JS-only pages and WAF blocks, and the performance cost.
Use when the user wants the list of URLs on a site rather than the page content — sitemap analysis, link planning, or seeding another tool. Covers `crawlberg map <url>` with `--limit`, `--search`, robots, output, and how it differs from a full crawl.
Use when the user wants a single page rendered as clean Markdown plus structured metadata. Covers `crawlberg scrape <url>`, JSON vs Markdown output, what metadata is returned, and how to handle JS-heavy pages.
| name | using-the-mcp-server |
| description | Use when calling LLM APIs through the liter-llm MCP server's 22 tools, and to decide when MCP beats the CLI or SDK. Covers the tool surface, the auto-installing launcher, and authentication. |
The liter-llm MCP server exposes 22 tools that mirror the proxy's REST
endpoints, so an MCP-compatible client (Claude Code, Claude Desktop) can call
143 LLM providers as tools with no glue code.
The plugin auto-registers the server. Its command is the bundled launcher
scripts/mcp-launch.sh, which execs liter-llm mcp --transport stdio. On first
run the launcher resolves a liter-llm binary: it reuses one on PATH, then
tries npx/uvx, then Homebrew, then downloads a checksum-verified prebuilt
from the tool's latest GitHub release. Override with
LITER_LLM_LAUNCHER=auto|npx|uvx|brew|download.
To run it manually:
liter-llm mcp --transport stdio # for Claude Code / Claude Desktop
liter-llm mcp --transport http --port 3001
Modality tools: chat, embed, generate_image, speech, transcribe,
moderate, rerank, search, ocr.
Model listing: list_models.
File operations: create_file, list_files, retrieve_file, delete_file,
file_content.
Batch operations: create_batch, list_batches, retrieve_batch,
cancel_batch.
Responses API: create_response, retrieve_response, cancel_response.
stdio has no per-request auth headers, so the server binds auth once at startup
via [mcp] config: set mcp.stdio_key_id to bind a specific virtual key, or
mcp.stdio_trust_local = true for fully trusted local environments. Provider
keys still come from env vars.