three.ws Brain

io.github.nirholas由 GitHub 账号 nirholas 发布v0.1.4更新于 Oct 24, 2026

List LLM providers and run chat completions through the three.ws multi-provider router.

发布方自己的服务：BrainDog

已验证STDIO仅桌面开发者工具 AI 与机器学习

服务详情

标识符: io.github.nirholas/brain-mcp
传输: STDIO
运行时: Desktop only
信任: Verified
发布于: Sep 16, 2026

安全提示

MCP 服务会接收对话中的工具调用请求，并可能执行外部操作。启用前请先了解该服务能做什么，并只授予它所需的权限。

注册中心已验证此条目所属的 GitHub 账号 nirholas。这并不表明该账号就是产品方。

SourceWeft 的检查只涵盖条目是否完整、端点是否响应；不审查服务器的代码，也不审查其工具的行为。

在 README 中添加徽章

向读者展示该 MCP 服务已收录于 SourceWeft，徽章链接到本页。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.nirholas%2Fbrain-mcp.svg)](https://sourceweft.com/mcp/io.github.nirholas%2Fbrain-mcp?utm_source=readme&utm_medium=badge)

概览

AI 生成的概览

本地 stdio MCP 服务器，让助手通过 three.ws 多供应商路由列出 LLM 供应商并执行对话补全。

可以做什么: 列出可用 LLM 供应商，含标识、网络、档位、最大输出、实时可用性及是否需要密钥
通过指定供应商执行对话补全，返回回复内容、实际路由、token 用量与耗时
免费开源权重模型无需密钥，付费一线旗舰模型需 three.ws API 密钥
所选模型短暂不可用时，自动回退到镜像或免费档位
适用场景: 适合希望助手通过单一端点访问多家模型厂商、而不必逐个接入各家 SDK 的场景，也便于在 Claude、GPT、o3、Grok、Qwen、DeepSeek 与开源权重模型之间比较或路由请求。
运行要求: 通过 npx 在本机运行，需要 Node.js 20 或更高版本。需能访问 three.ws，或用 THREE_WS_BASE 指定自定义地址。可选的 THREE_WS_API_KEY（Bearer 令牌）用于解锁付费旗舰模型；可选的 THREE_WS_TIMEOUT_MS 设置单次请求超时，默认 120000 毫秒。

安装前请注意

提示词与消息会发送到 three.ws 路由并转发给第三方模型供应商，请勿提交机密内容。付费旗舰模型需要 THREE_WS_API_KEY，可能在 three.ws 账户产生费用。工具为只读，不修改平台状态，但供应商可用性与结果每次调用可能不同。

安装

在 SourceWeft 中

打开控制台中的 three.ws Brain，将其添加到工作区。
为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照仓库中的启动说明。

README

[three.ws]

@three-ws/brain-mcp

Any model, one interface — discover LLM providers and run chat completions through the three.ws multi-provider router, from any AI agent.

[npm] [license] [node] [MCP Registry] [three.ws]

A Model Context Protocol server that gives any AI assistant the three.ws multi-provider LLM router over stdio. Discover which models are available — Claude, the GPT-5.6 family, o3, Grok, Qwen, DeepSeek, NVIDIA Nemotron, IBM Granite, and more — and run a chat completion through whichever one fits, without wiring each vendor SDK yourself.

The router fronts every provider behind one endpoint and transparently falls back across mirrors and free tiers if the chosen model is briefly down. The free open-weight tiers (GPT-OSS 120B, NVIDIA NIM models) work with no key; the paid first-party flagships unlock with a three.ws API key.

Install

Or run with npx (no install):

Quick start

Claude Code, one line:

To unlock the paid flagships, pass your three.ws API key:

Claude Desktop / Cursor (claude_desktop_config.json or mcp.json):

json

{	"mcpServers": {		"brain": {			"command": "npx",			"args": ["-y", "@three-ws/brain-mcp"],			"env": { "THREE_WS_API_KEY": "sk_live_…" }		}	}}

{	"mcpServers": {		"brain": {			"command": "npx",			"args": ["-y", "@three-ws/brain-mcp"],			"env": { "THREE_WS_API_KEY": "sk_live_…" }		}	}}

Inspect the surface with the MCP Inspector:

Tools

Tool	Type	What it does
`list_providers`	read-only	List every LLM the router can reach — key, network, tier, max output, live availability, and whether it needs auth.
`chat`	read-only	Run a chat completion through the chosen provider; returns the full reply, the route taken, token usage, and timing.

Both tools read live data — the provider set and completions vary between calls, so neither is idempotent. chat does not mutate any platform state, so it is annotated read-only.

Input parameters

list_providers — no parameters.

chat — messages (required: 1–100 turns of { role: "user" | "assistant", content }, content ≤ 16,000 chars), provider (provider key from list_providers, default gpt-oss-120b), system (optional system prompt, ≤ 8,000 chars), maxTokens (optional, 64–16384, default 4096, clamped to the model's ceiling).

Example

Both responses below are shape illustrations — the live provider set and generations will differ.

jsonc

// list_providers (example response)> {}{  "ok": true,  "count": 34,  "available": 33,  "default_provider": "gpt-oss-120b",  "providers": [    { "key": "gpt-oss-120b", "label": "GPT-OSS 120B", "network": "OpenAI · OpenRouter", "tier": "balanced", "maxOutput": 8192, "description": "Open-weight 120B from OpenAI. Fast, capable, free tier. Platform default.", "available": true, "requiresAuth": false },    { "key": "claude-sonnet-5", "label": "Claude Sonnet 5", "network": "Anthropic", "tier": "balanced", "maxOutput": 16384, "description": "Near-Opus quality on coding and agentic work at Sonnet cost. Best for most tasks.", "available": true, "requiresAuth": true },    { "key": "deepseek-r1", "label": "DeepSeek R1", "network": "DeepSeek", "tier": "reasoning", "maxOutput": 8192, "description": "Open reasoning model. Strong at math and code.", "available": true, "requiresAuth": true }    /* … */  ]}

// list_providers (example response)> {}{  "ok": true,  "count": 34,  "available": 33,  "default_provider": "gpt-oss-120b",  "providers": [    { "key": "gpt-oss-120b", "label": "GPT-OSS 120B", "network": "OpenAI · OpenRouter", "tier": "balanced", "maxOutput": 8192, "description": "Open-weight 120B from OpenAI. Fast, capable, free tier. Platform default.", "available": true, "requiresAuth": false },    { "key": "claude-sonnet-5", "label": "Claude Sonnet 5", "network": "Anthropic", "tier": "balanced", "maxOutput": 16384, "description": "Near-Opus quality on coding and agentic work at Sonnet cost. Best for most tasks.", "available": true, "requiresAuth": true },    { "key": "deepseek-r1", "label": "DeepSeek R1", "network": "DeepSeek", "tier": "reasoning", "maxOutput": 8192, "description": "Open reasoning model. Strong at math and code.", "available": true, "requiresAuth": true }    /* … */  ]}

jsonc

// chat (example response)> {    "provider": "claude-sonnet-5",    "system": "You are terse.",    "messages": [{ "role": "user", "content": "Name three Solana RPC methods." }]  }{  "ok": true,  "provider": "claude-sonnet-5",  "model": "Claude Sonnet 5",  "network": "Anthropic",  "tier": "balanced",  "routed_via": null,  "content": "getBalance, getAccountInfo, getSignaturesForAddress.",  "usage": { "input_tokens": 24, "output_tokens": 14, "total_tokens": 38 },  "timing_ms": { "first_token": 412, "total": 980 }}

// chat (example response)> {    "provider": "claude-sonnet-5",    "system": "You are terse.",    "messages": [{ "role": "user", "content": "Name three Solana RPC methods." }]  }{  "ok": true,  "provider": "claude-sonnet-5",  "model": "Claude Sonnet 5",  "network": "Anthropic",  "tier": "balanced",  "routed_via": null,  "content": "getBalance, getAccountInfo, getSignaturesForAddress.",  "usage": { "input_tokens": 24, "output_tokens": 14, "total_tokens": 38 },  "timing_ms": { "first_token": 412, "total": 980 }}

routed_via is null when the requested provider answered directly; otherwise it names the mirror or free-tier route the router fell back to (so you always get an answer even if the first choice is briefly down).

Model availability is dynamic. Always call list_providers first rather than hardcoding a key. The current Claude ids are claude-fable-5, claude-opus-5, claude-sonnet-5, claude-opus-4-7, claude-sonnet-4-6, and claude-haiku-4-5, but the live list is the source of truth.

Authentication

Model class	Needs a key?
Free open-weight tiers (GPT-OSS 120B, and the NVIDIA NIM set: Nemotron 3 Super / Nemotron Super 49B / Nemotron Nano / DeepSeek V4 / Kimi K2 / Llama 4 Maverick / MiniMax M2)	No
Paid first-party flagships (Claude, GPT-5.6, o3, Qwen Plus, DeepSeek, …)	Yes — set `THREE_WS_API_KEY`

Create an API key at three.ws/dashboard/developers. Without it, paid models return a sign-in error and list_providers flags them with requiresAuth: true.

Requirements

Node.js >= 20.
Network access to https://three.ws (or your own THREE_WS_BASE).

Environment variables

Variable	Required	Default	Purpose
`THREE_WS_BASE`	no	`https://three.ws`	API base URL (override to self-host or target a preview).
`THREE_WS_API_KEY`	no	—	Bearer credential that unlocks the paid first-party flagships.
`THREE_WS_TIMEOUT_MS`	no	`120000`	Per-request timeout (completions stream server-side).

Errors

A failed tool call returns an MCP error result (isError: true) whose text is a single JSON object — { "ok": false, "error": "<code>", "message": "…" }, plus status and detail on upstream rejections:

`error`	Meaning	Recovery
`upstream_error`	The router rejected the request — `status` carries the real HTTP code: `400` (bad arguments or an unknown provider key), `401` (paid model without a valid `THREE_WS_API_KEY`), `429` (rate-limited), `502` (the model's stream failed before producing output).	Act on `status`; for `401` set a key, for an unknown key re-run `list_providers`.
`timeout`	No complete response within `THREE_WS_TIMEOUT_MS`. Long flagship generations can be slow — the default 120 s matches the router's own ceiling.	Retry, lower `maxTokens`, or pick a `fast`-tier provider.
`network_error`	The request never reached the router (DNS, offline, TLS).	Check connectivity / `THREE_WS_BASE`.
`bad_config`	`THREE_WS_TIMEOUT_MS` is not a positive number (thrown at startup).	Fix the env var.

If the requested provider fails mid-flight the router transparently falls back to a mirror or free tier and the reply's routed_via names the route taken — you only see an error when every route is exhausted.