Skip to main content
Glama
jfdjaf

mcp-model-proxy

by jfdjaf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mcp-model-proxy

No user-submitted related servers found.

    Related Servers

    • MCP Server

      johnleider
      A
      license
      Not graded
      quality
      D
      maintenance
      A Machine Context Protocol server that enables Claude AI to interact with tools through a structured communication interface, following standard MCP patterns with server initialization and stdio transport.
      1,140 npm
      2
      MIT

    • openwebui-mcp

      vedmaka
      A
      license
      Not graded
      quality
      C
      maintenance
      Open WebUI MCP server that exposes ask and list_models tools, letting any MCP client query Open WebUI models through the full tool-calling loop (including server-side tools) via stdio, SSE, or streamable HTTP transports.
      5
      MIT

    • Test MCP Server

      mokesmokane
      F
      license
      Not graded
      quality
      D
      maintenance
      A dual-transport MCP server that exposes your API as tools to LLM clients, supporting both stdio transport for local clients like Claude Desktop and HTTP/SSE transport for remote clients like OpenAI's Responses API.
      -

    • claudecode-mcp

      trevoraspencer
      A
      license
      A
      quality
      B
      maintenance
      Local MCP server that wraps the headless Claude Code CLI as MCP tools, providing stateless access to Claude's coding capabilities through prompt-based interactions. It enables users to execute Claude Code commands with various prompt formats and structured outputs directly from MCP clients.
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'ask_model' has a clearly distinct and singular purpose, making misselection impossible.

    Naming Consistency5/5

    The single tool name 'ask_model' follows a clear verb_noun pattern, and with only one tool, consistency is inherently perfect as there are no other names to compare or deviate from.

    Tool Count2/5

    A single tool is too few for a server named 'mcp-model-proxy', which suggests a broader scope for model interactions. This minimal set feels thin and likely incomplete for typical proxy functionalities like listing models, managing configurations, or handling different API endpoints.

    Completeness2/5

    The tool surface is severely incomplete for a model proxy domain. While 'ask_model' covers a core operation, there are significant gaps such as listing available models, configuring model parameters, handling streaming responses, or managing API keys, which will likely cause agent failures in real-world scenarios.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources