zio-ella
Here are a few possible translations of "MCP framework for ZIO HTTP", depending on the specific nuance you want to convey. I'll provide explanations to help you choose the best fit: **1. (Most Literal, General): 用于 ZIO HTTP 的 MCP 框架** * **用于 (yòng yú):** Used for, for * **ZIO HTTP:** (Keeps the English name, as it's a specific library) * **的 (de):** Possessive particle (of) * **MCP 框架 (MCP kuàngjià):** MCP framework (Keeps the English name, as it's likely a specific framework) This is the safest and most straightforward translation. It's suitable if your audience is familiar with the terms "ZIO HTTP" and "MCP framework" or if you want to avoid any potential misinterpretations by translating them. **2. (Slightly More Descriptive): 基于 ZIO HTTP 的 MCP 框架** * **基于 (jī yú):** Based on, built upon * **ZIO HTTP:** (Keeps the English name) * **的 (de):** Possessive particle (of) * **MCP 框架 (MCP kuàngjià):** MCP framework (Keeps the English name) This emphasizes that the MCP framework *relies* on ZIO HTTP. It's a subtle difference, but it might be more appropriate if the framework is tightly integrated with ZIO HTTP. **3. (If "MCP" is an acronym and you know what it stands for, and it's commonly translated): 用于 ZIO HTTP 的 [Translated Acronym] 框架** * **用于 (yòng yú):** Used for, for * **ZIO HTTP:** (Keeps the English name) * **的 (de):** Possessive particle (of) * **[Translated Acronym] 框架 ([Translated Acronym] kuàngjià):** Replace `[Translated Acronym]` with the Chinese translation of what "MCP" stands for. For example, if MCP stood for "Message Control Protocol" and the Chinese translation of that was "消息控制协议 (xiāo xī kòng zhì xié yì)", then this would be: `用于 ZIO HTTP 的 消息控制协议 框架` **Important:** Only use this if you *know* the meaning of the acronym and there's a standard or widely accepted Chinese translation. Otherwise, stick with the English acronym. **4. (If you want to explain what MCP does in the context of ZIO HTTP): 用于 ZIO HTTP 的 [Description of MCP Functionality] 框架** * **用于 (yòng yú):** Used for, for * **ZIO HTTP:** (Keeps the English name) * **的 (de):** Possessive particle (of) * **[Description of MCP Functionality] 框架 ([Description of MCP Functionality] kuàngjià):** Replace `[Description of MCP Functionality]` with a brief description of what the MCP framework *does* in relation to ZIO HTTP. This is the most complex option and requires understanding the framework's purpose. For example, if the MCP framework is for managing request routing, you might say: `用于 ZIO HTTP 的 请求路由管理 框架` (qǐng qiú lù yóu guǎn lǐ kuàngjià - Request Routing Management Framework). **Recommendation:** Start with option **1 (用于 ZIO HTTP 的 MCP 框架)**. If you have more context about what "MCP" stands for and its function, consider options 3 or 4. Option 2 is a good alternative if the framework is tightly coupled with ZIO HTTP. To give you the *best* translation, please provide more information about what "MCP" stands for and what the framework does.
otobrglez
README
zio-ella
zio-ella 是一个使用 Scala 3 和 ZIO 以及 zio-http
为现代 AI 平台编写 MCP (模型上下文协议) 服务器的框架。
⚠️ 该项目处于早期阶段,并且会快速变化。欢迎随时提出想法和用例。
服务中的示例功能和工具定义可能如下所示:
import zio.ZIO
import zio.dev.ella.*
object MyService:
val capabilities = Capabilities(
// 仅返回当前服务器时间的工具
Tool("get-time") -> { _ =>
zio.Clock.instant.map(_.toString)
},
// 示例工具,用于获取我们接受城市作为参数的天气信息。
Tool("get-weather", ArgDef.string("city")) -> {
_.string("city").flatMap(city => ZIO.succeed(s"Weather in $city is sunny!"))
}
)
def run = MCPServer(capabilities).run
与 ZIO Stack 的集成如下:
object Main extends ZIOAppDefault:
def program = for
_ <- logInfo("启动中...")
_ <- MyService.run
yield ()
def configuredServer: TaskLayer[Server] =
ZLayer
.fromZIO(ZIO.config(Config.int("port")).tap(port => logInfo(s"在端口 $port 上启动服务器")))
.flatMap(portEnv => Server.defaultWithPort(portEnv.get))
def run = program.provide(configuredServer)
资源
推荐服务器
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
MCP Package Docs Server
促进大型语言模型高效访问和获取 Go、Python 和 NPM 包的结构化文档,通过多语言支持和性能优化来增强软件开发。
Claude Code MCP
一个实现了 Claude Code 作为模型上下文协议(Model Context Protocol, MCP)服务器的方案,它可以通过标准化的 MCP 接口来使用 Claude 的软件工程能力(代码生成、编辑、审查和文件操作)。
@kazuph/mcp-taskmanager
用于任务管理的模型上下文协议服务器。它允许 Claude Desktop(或任何 MCP 客户端)在基于队列的系统中管理和执行任务。
mermaid-mcp-server
一个模型上下文协议 (MCP) 服务器,用于将 Mermaid 图表转换为 PNG 图像。
Jira-Context-MCP
MCP 服务器向 AI 编码助手(如 Cursor)提供 Jira 工单信息。

Linear MCP Server
一个模型上下文协议(Model Context Protocol)服务器,它与 Linear 的问题跟踪系统集成,允许大型语言模型(LLM)通过自然语言交互来创建、更新、搜索和评论 Linear 问题。

Sequential Thinking MCP Server
这个服务器通过将复杂问题分解为顺序步骤来促进结构化的问题解决,支持修订,并通过完整的 MCP 集成来实现多条解决方案路径。
Curri MCP Server
通过管理文本笔记、提供笔记创建工具以及使用结构化提示生成摘要,从而实现与 Curri API 的交互。