crowllm-mcp
OfficialRelated Servers
Alternatives to crowllm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to discover and inspect available open models, estimate token costs, and run chat completions through an OpenAI-compatible inference endpoint, with optional bearer-key authentication for billed calls.Apache 2.0
- AlicenseAqualityCmaintenanceEnables MCP clients to list available models with public metadata and pricing, and to send a single text chat completion request using the user's own API key.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to browse and compare model catalogs, pick models by budget or context window, and run completions metered to the caller's own API key.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to list available models, run non-streaming chats with token usage and timing, and probe any OpenAI-compatible gateway for authentication, streaming, and error-shape compatibility.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to browse a live catalog of 100+ models with pricing, rankings and measured uptime, check credits and spend, and send chat completions through an OAuth-authenticated, per-connection key capped by a spend limit. Read tools are free, and paid calls are priced and approved before any credit is used.MIT
- FlicenseAqualityDmaintenanceEnables LLM chat with routing and failover, balance checking, and model listing via MCP.3-
TDQS
Scored across 3 tools
Each tool maps to a distinct stage of the workflow: discovering models (search_models), comparing cost (get_pricing), and actually running inference (chat). Search and pricing both touch the model catalog, but the descriptions make the split clear (ids vs. USD per 1M tokens). No plausible misselection.
search_models and get_pricing follow a clean verb_noun snake_case pattern, and chat is a single word that fits naturally. Minor deviation only: chat lacks a noun object, but it is unambiguous in context.
Three tools is on the lean side but proportionate to a thin LLM gateway surface: discover, price, invoke. Nothing feels padded, though the set is small enough that a little more breadth would be welcome.
The core loop of finding a model, checking its price, and chatting is fully covered. Gaps are minor and workaroundable: no embeddings/completions-only endpoint, no account balance or usage-history lookup, and no way to fetch a single model's full metadata beyond what search returns.