LMX Cloud LLM Inference

io.lmxcloudPublished by lmxcloud.ioOfficial publisherv0.1.0Updated Oct 24, 2026

OpenAI-compatible LLM MCP (7 tools); chat via balance key or x402 USDC on Base

VerifiedStreamable HTTPWeb executableAI & ML

Overview

AI-generated overview

Remote MCP endpoint that gives an assistant OpenAI-compatible LLM chat tools, paid either with a balance key or USDC on Base.

What you can do
A remote, OpenAI-compatible LLM inference service exposed over MCP with seven tools. It lets an assistant send chat requests to hosted models through the LMX Cloud endpoint. Access is paid either from a prepaid balance key or per request with USDC on the Base network.
When to use it
Worth adding when an assistant needs an OpenAI-compatible chat model reachable over a remote MCP endpoint, and you are willing to fund calls through a balance key or on-chain USDC payments.
Requirements
A remote MCP client connecting to the LMX Cloud endpoint over streamable HTTP. Either a balance key or a crypto wallet able to pay USDC on Base. No packages, environment variables, or headers are declared.
Before you install
Calls are paid: either a balance key is drawn down or USDC is spent on Base, so usage can cost money. The manifest declares no authentication, so verify how the balance key or wallet is supplied before connecting. Chat content is sent to a third-party inference provider.

Installation

In SourceWeft

  1. Open LMX Cloud LLM Inference in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.lmxcloud%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lmx-cloud-llm-inference": {
      "type": "http",
      "url": "https://mcp.lmxcloud.io/mcp"
    }
  }
}

Tools

9

get_pricing

Fetch current LMX Cloud per-call pricing catalog.

Parametersapi_key

quote_price

Estimate USDC cost for a single model call. Uses GET /v1/pricing with model and token params.

Parametersmodelrequiredapi_keymax_tokensprompt_tokens

list_models

List currently supported LMX model aliases and providers.

Parametersapi_key

get_status

Fetch LMX Cloud provider health, fallback chain, and anchoring status.

Parametersapi_key

get_balance

Fetch USD credit balance for the caller API key. Requires authentication.

Parametersapi_key

get_usage

Fetch request and token usage totals for the caller API key. Requires authentication.

Parametersapi_key

extract_pdf

Extract text and light structure (title, headings, page count) from a PDF via LMX pdf-extract. Provide file_url and/or file_base64. Requires a real LMX API key (same gate as web_search).

Parametersapi_keyfile_urlfile_base64

chat_completion

Call LMX Cloud OpenAI-compatible chat completions. Prefers a pre-funded API key (Bearer / api_key); when omitted and x402 is enabled, requires a USDC pay-per-call payment. Optional image_url / images enable vision input (OpenAI content-parts format) — use a vision model such as llama-3.2-90b-vision, qwen-3.6-35b, or qwen-3.5-35b.

Parametersmodelimagespromptrequiredapi_keyimage_urlmax_tokenstemperature

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.