mcp-computeflux
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMPUTEFLUX_API_KEY | Yes | Bearer key for the ComputeFlux endpoint. | |
| COMPUTEFLUX_BASE_URL | No | Any OpenAI-compatible base URL. | https://api.computeflux.ai/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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| computeflux_modelsB | List the models available on the ComputeFlux (OpenAI-compatible) endpoint. |
| computeflux_chatB | Send a chat completion request to the ComputeFlux (OpenAI-compatible) endpoint. Returns the assistant message text plus usage. Use model like "CAO/deepseek-flash". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.