agentleFS
Sign inStart free
kreuzberg-devkreuzberg-dev/liter-llm/skills/liter-llm-using-the-mcp-server/SKILL.md

liter-llm-using-the-mcp-server

Skill261 starsChanged 3 months agoMITView on GitHub

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.

  • Reads credentials
  • Installs packages

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 89
  2. Distinctive:

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

    line 90

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- AI-RULEZ :: GENERATED FILE — DO NOT EDIT Content-Hash: blake3:6925dd58f9790a1cc57f093167cf3b430886393ff3792d28003f15269b5546a2 Source-Hash: blake3:084ca4c7fec33b4be004ade1f933542f40edfe39384573517678107797eb945c Schema-Version: v1 -->

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:

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:

[[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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free