Skein Toolkit MCP Server

Skein Toolkit MCP Server

A local MCP SSE server that proxies Cloudflare Workers AI and provides multi-step task orchestration, integrating with LiteLLM to enable AI-assisted development workflows.

Category
访问服务器

README

Skein Toolkit

A repo-agnostic clone of the AI development toolchain originally built inside Electron-Splines: a Cloudflare Workers AI proxy, a multi-step task orchestrator, and a local agentic MCP server, fronted by a unified LiteLLM proxy.

This repo is the result of the "LLM Tech Stack Standalone Repository" spin-off (see architecture-docs/global/ai-task-queue.md, AT-1116-1139, in the Electron-Splines repo for the full task history and rationale). Further refinement of this agentic system happens here, not in Electron-Splines.

What's in here

Path Purpose
mcp-server/local-mcp.py The core: a local MCP SSE server (port 3100) that also proxies/instruments Cloudflare Workers AI requests at /cfproxy/{account_id}/..., including a multi-step task orchestrator with bounded-ambiguity escalation.
mcp-server/devserver-mcp.py A lighter MCP server variant for a remote GPU devserver.
mcp-server/litellm_config.yaml + litellm.env.example LiteLLM unified proxy config routing local/CF/Groq/DeepSeek/Anthropic/OpenAI models.
mcp-server/run-cline.ps1, resume-orchestrator-run.ps1, toolchain-doctor.ps1, start-litellm.ps1 Launcher/diagnostic scripts for running Cline against this stack on Windows.
cloudflare/README.md Cloudflare Workers AI configuration (env-var only -- no zone/firewall config).
docker-compose.yml, docker-compose.override.yml, docker/ Containerized mcp-server + LiteLLM stack.

Quick start (local, Windows)

  1. Create a Python virtualenv at the repo root and install dependencies:
    python -m venv .venv
    .venv\Scripts\pip install -r mcp-server\requirements.txt
    
  2. Copy mcp-server\litellm.env.example to mcp-server\litellm.env and fill in your API keys (see cloudflare/README.md for the Cloudflare token).
  3. Run mcp-server\toolchain-doctor.ps1 to diagnose and (where possible) auto-start LiteLLM and local-mcp.py.
  4. Run mcp-server\run-cline.ps1 -Task "..." to launch Cline against the configured model.

By default, local-mcp.py operates on the parent of the mcp-server/ directory (i.e. this repo's checkout). Set WORKSPACE_ROOT to point it at a different project checkout instead.

Quick start (Docker)

cp docker/.env.example docker/.env   # fill in API keys
docker compose up --build

This starts mcp-server (port 3100) and litellm (port 4000, dashboard at /ui). By default mcp-server operates on ./workspace -- use docker-compose.override.yml to mount a different project checkout.

Environment variables

Variable Default Purpose
WORKSPACE_ROOT parent of mcp-server/ Project checkout local-mcp.py reads/writes/runs commands in.
CF_API_BASE / CF_API_KEY -- Cloudflare Workers AI proxy target + token. See cloudflare/README.md.
CF_PROXY_OQ_LEDGER_PATH architecture-docs/global/architect-open-questions.md Path (relative to WORKSPACE_ROOT) to an "open questions" ledger the orchestrator appends bounded-ambiguity rows to. If the consuming project has no such ledger, leave the default -- failures to read/write it are logged and degrade to "ambiguity surfaced inline", not a crash.
CF_PROXY_USD_TO_AUD_RATE, CF_PROXY_MONTHLY_BUDGET_AUD, CF_PROXY_DAILY_REVIEW_THRESHOLD_USD 1.42, 100.00, derived CF spend-review accounting (optional).

Status

This is an early-stage clone (Phase 1 of the migration plan in planning_document.md): the toolchain runs standalone, but the orchestrator's "open questions" / "actionable tasks" governance integration (CF_PROXY_OQ_LEDGER_PATH and friends) still assumes an Electron-Splines-style architecture-docs/ layout when enabled. Generalizing that integration into reusable create_open_question / create_actionable_task MCP tools is tracked as AT-1137-1139 in the source repo.

Full mirroring of the consuming project's app/, engine/, and scripts/ directories (AT-1117/1118/1119) has not been done here -- this clone currently contains only the AI-toolchain pieces (MCP server, orchestrator, LiteLLM, Cloudflare/Docker config). If the original AT-1117/1118 scope (mirroring the entire Electron-Splines app and engine source trees into this repo) is still wanted, that is a separate, much larger effort and should be re-scoped with the architect first.

License

Licensed under the Apache License, Version 2.0 -- see LICENSE and NOTICE. This is a deliberate relaxation from the proprietary Electron-Splines source repository's license, applying only to this standalone toolkit: the goal is to let other projects and contributors adopt and extend the MCP server/orchestrator/CF-proxy toolchain, and to make it mergeable into complementary open-source projects (e.g. Odysseus, AGPL-3.0 -- permissively licensed code can be incorporated into an AGPL project).

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选