Skip to main content
Glama
UplinkSwitch MCP server

UplinkSwitch MCP server

Official
by uplinkswitch

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
UPLINKSWITCH_API_KEYNoAPI key for UplinkSwitch. Only needed for the `chat` tool; the catalog tools work without a key. Keys come from https://uplinkswitch.ai/console.
UPLINKSWITCH_BASE_URLNoPoints the server at another host on the same network. Default is https://api.uplinkswitch.com/v1.https://api.uplinkswitch.com/v1

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
list_modelsA

List the models on the UplinkSwitch catalog with their price per million tokens. Needs no API key. Filter by a case-insensitive query across the id, display name and developer, and optionally by type.

modelA

Get one model's full catalog entry: context window, output limit, supported parameters, endpoints and exact pricing. Needs no API key.

compare_pricesB

Compare price per million tokens across models, cheapest input first, so an agent can pick the least expensive model that does the job. Needs no API key.

chatA

Send a conversation to any chat model id and return the answer with the token usage and the cost of the request. Needs UPLINKSWITCH_API_KEY in the environment. OpenAI and Anthropic models both work on the same key and base URL.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 4 tools

Disambiguation4/5

Each tool has a distinct purpose: single model lookup, chat completion, filtered catalog listing, and price comparison. However, list_models and compare_prices both surface pricing information and could be confused by an agent deciding which to call for cost data, and the bare name 'model' is less self-explanatory than the others.

Naming Consistency3/5

Two tools follow a verb_noun pattern (list_models, compare_prices) while the other two are bare nouns (model, chat), and 'model' is a particularly vague name for a getter. The set is readable but mixes conventions without a clear rule.

Tool Count4/5

Four tools is a tight, purposeful set for an LLM gateway: discovery, pricing comparison, and chat execution all earn their place. It sits at the thin end of the ideal range but nothing is redundant.

Completeness3/5

Core workflows (find a model, compare cost, run a chat) are covered with no dead ends, but obvious gateway operations are absent — no way to check account balance/credits or limits despite cost-returning chat, and no embeddings or streaming-specific entry point. Agents can work around these but will hit the gap on billing or non-chat use cases.