mcp-computeflux
Related Servers
Alternatives to mcp-computeflux
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA local MCP server exposing the OpenAI platform REST API as tools for file management, fine-tuning, inference, images, audio, batch processing, and organization usage/costs.-
- AlicenseNot gradedqualityCmaintenanceExposes local LM Studio language models as MCP tools, enabling chat completions and model listing through a local OpenAI-compatible API without requiring API keys.MIT
- AlicenseAqualityBmaintenanceEnables LLM chat with routing and failover, balance checking, and model listing via MCP.3Academic Free v1.1
- FlicenseNot gradedqualityDmaintenanceLocal MCP server that exposes fixed tools for GPT, Claude, and Gemini while routing to any OpenAI-compatible chat completions backend with independent configuration per target.1-
- -licenseCqualityNot gradedmaintenanceEnables interaction with OpenAI-compatible APIs (like Ollama) through MCP tools. Provides access to chat completions, model listings, and embeddings generation from local or remote OpenAI-style endpoints.3-
- AlicenseAqualityCmaintenanceProxies LLM completion requests to OpenAI-compatible providers via MCP tools.2MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: listing available models versus sending a chat completion request. There is no overlap in functionality or ambiguous selection risk.
Both tools share the same 'computeflux_' prefix and use snake_case, which is consistent. The only minor deviation is that one name is a plural noun and the other is a verb-like action, but the pattern remains readable.
Two tools is slightly under the typical 3–15 range, but for a narrow OpenAI-compatible wrapper covering model listing and chat completions, each tool earns its place. The surface is minimal but reasonable for the stated purpose.
Core chat functionality and model listing are present, but an OpenAI-compatible endpoint often includes other common operations such as embeddings, completions, or audio. These gaps are notable, though agents could still perform basic chat workflows.