using-the-mcp-server

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.

跳到安装

仓库: xberg-io/plugins
最近来源活动: 2026年7月12日 05:08
检测到的 SKILL.md 语言: 英语
星标: 27
分支: 2

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/xberg-io/plugins --skill using-the-mcp-server

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

xberg

Extract text, tables, metadata, and images from 98+ document formats (PDF, Office, images, HTML, email, archives, academic) using Xberg. Use when writing code that calls Xberg APIs in Python, Node.js/TypeScript, Rust, or CLI. Covers installation, extraction (sync/async), configuration (OCR, chunking, output format), batch processing, error handling, and plugins.

2026-07-27

automating-the-browser

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.

2026-07-12

crawlberg

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, batch-scrape, batch-crawl, download, citations, version, mcp, serve), output formats (JSON + Markdown), browser fallback, and when to prefer the MCP server over shelling out.

2026-07-12

查看这个仓库的全部 Skills

Using the MCP Server

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.

How it runs in this plugin

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

The 22 tools

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.

Authentication

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.

When to prefer MCP over the CLI or SDK

Prefer MCP inside an agent session: the agent invokes tools directly, with no code to write or process to manage.

Prefer the SDK when building application software in a specific language.

Prefer the proxy when many apps or teams need a shared OpenAI-compatible endpoint with keys, budgets, and rate limits.

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.