mcp-computeflux

mcp-computeflux

Zero-dependency MCP (Model Context Protocol) server. Give any MCP host — Cursor, Claude Desktop, Windsurf, any MCP client — one OpenAI-compatible endpoint, and call models on ComputeFlux as plain tools: list what's available, then run a chat completion.

Your MCP agents hit flash-tier models over one OpenAI-compatible endpoint.

• ~175 lines of Node 18+, no `npm install` to run the server (only the optional client/ e2e harness pulls SDK deps).
• Backend-agnostic: point it at *any* OpenAI-compatible API — ComputeFlux is the default, not the only target.
• ComputeFlux is an OpenAI-compatible, TEE-verifiable multi-model inference gateway deployed on the Polkadot testnet.

Tools

Configuration (env)

export COMPUTEFLUX_API_KEY="your_c***_key"

export COMPUTEFLUX_BASE_URL="https://your-openai-compat-host/v1" # optional

Install

Published on the official MCP Registry (.mcpb bundle, no npm step):

io.github.computeflux2026isgod/mcp-computeflux — listed on the official MCP Registry (search by this name).

Any MCP client / agent that supports registry install (mcp add, Cursor, Claude Desktop, Claude Code) can pull it by name. Direct git-clone quickstart:

git clone https://github.com/computeflux2026isgod/mcp-computeflux

export COMPUTEFLUX_API_KEY="your_...key" node /path/to/mcp-computeflux/server.mjs # stdio JSON-RPC

mcpServers snippet:

{

"mcpServers": { "computeflux": { "command": "node", "args": ["/path/to/mcp-computeflux/server.mjs"], "env": { "COMPUTEFLUX_API_KEY": "your_c***_key" } } } }

Local e2e (optional)

client/ contains a tiny harness using the official MCP SDK — the exact path Cursor / Claude Desktop use. It spawns the server over stdio, lists tools, and runs one chat completion with a unique-token round-trip fidelity check.

cd client && npm install && npm run e2e   # expects COMPUTEFLUX_API_KEY in the .env it points to

Transport

Newline-delimited JSON-RPC 2.0 over stdio. Only protocol messages are written to stdout; logs go to stderr.

License

MIT