Skip to main content
Glama
crowllm-mcp

crowllm-mcp

Official
by crowwdev

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CROWLLM_API_KEYNoCrowLLM API key created at crowllm.com. Required for the chat tool; optional for search_models and get_pricing.
CROWLLM_BASE_URLNoOptional base URL for CrowLLM. Defaults to https://crowllm.com.https://crowllm.com

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_modelsB

Search the live CrowLLM catalog (GET /v1/models). Optionally return only zero-rated ':free' ids.

get_pricingB

List CrowLLM list prices in USD per 1M tokens. Input = 2 x model_ratio; output = input x completion_ratio.

chatB

Send a prompt to any CrowLLM model (POST /v1/chat/completions) and return the reply with token usage.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 3 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count4/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues