xberg-io/liter-llm / plugin/.ai-rulez/skills/liter-llm-using-the-mcp-server
liter-llm-using-the-mcp-server
VerifiedUse 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.
SKILL.md
View on GitHub---
type: Playbook
title: 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.
x-ai-rulez:
kind: skill
id: liter-llm-using-the-mcp-server
metadata:
name: liter-llm-using-the-mcp-server
---
# 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
174 LLM providers as tools with no glue code.
## Standalone skill installation
Installing this skill alone does not register an MCP server or include the plugin launcher.
Install the CLI (for example, `brew install xberg-io/tap/liter-llm`), then configure your MCP client with
`liter-llm mcp --transport stdio` as its stdio command. The full product plugin supplies registration where
the runtime supports MCP.
## 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 prebuilt
from the tool's latest GitHub release. Override with
`LITER_LLM_LAUNCHER=auto|npx|uvx|brew|download`.
To run it manually:
```bash
liter-llm mcp --transport stdio # for Claude Code / Claude Desktop
liter-llm mcp --transport http --port 3001
```
## Configure model routing
Provider-backed tools use the proxy model registry. Create `liter-llm-proxy.toml` in the
working directory, or pass `--config /absolute/path/liter-llm-proxy.toml` when launching:
```toml
[[models]]
name = "gpt-4o"
provider_model = "openai/gpt-4o"
```
Supply `OPENAI_API_KEY` in the MCP process environment, then call `chat` using the
configured name `gpt-4o`. `list_models` shows configured names; an unknown model is a
request error. Missing credentials are also reported on provider-backed requests.
Gemini filters host credentials: install with `--skip-settings` and configure the selected
provider through `gemini extensions config liter-llm "OpenAI key"`. Local stdio does not
need a separate proxy virtual key.
## 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
Local stdio trusts the invoking local client by default, so the registered command starts
without extra proxy authentication configuration. Provider API keys still come from environment
variables and are needed for provider-backed requests.
To apply a restricted virtual key, configure `mcp.stdio_key_id`; an unknown key fails startup.
Set `mcp.stdio_trust_local = false` to require an explicit virtual key. HTTP transport retains
its authentication policy; the local stdio default does not disable HTTP authorization.
## 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |