Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

SEP-2640: Skills Extension

未关闭
#1,140 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
40/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
java
领域
api, backend

调研方向

Review the SEP-2640 specification and the linked pull requests in other SDKs (Python, C#, Go) to understand the required schema types, client APIs, and server APIs. The work involves adding new classes for skills handling, updating capability negotiation, and implementing the required endpoints. Start by examining the existing SDK structure for extensions and the MCP protocol handling code. 'Done' means the SDK fully supports the skills/list, skills/get, and optional resources/directory/read methods with proper capability negotiation.

由索引模型根据 Issue 内容生成。

描述

extensions P3

Expected Behavior

The Java SDK should support the SEP-2640 Skills extension, enabling MCP clients to discover and retrieve Agent Skills exposed by MCP servers.

The SDK should provide:

  • Schema types and method constants for skills/list, skills/get, and the optional resources/directory/read.
  • Client APIs to list skills, retrieve a skill entry by its SKILL.md URI, read skill resources, and—when advertised—read directory resources.
  • Stateless server APIs to register skills and expose the required endpoints.
  • Support for io.modelcontextprotocol/skills capability negotiation, including the optional directoryRead setting.

Current Behavior

The SDK does not yet support the SEP-2640 Skills extension.

Context

This change adds support for the SEP-2640 Skills extension to the Java SDK, aligning it with the following implementations in other MCP SDKs:

I implemented this before realizing that non-trivial changes should be discussed with maintainers first. I would appreciate feedback on the proposed scope and API design, and I am happy to revise the implementation accordingly.

主要语言
Java
星标
3.7k
派生
1.1k
平均合并
1 天 15 小时
30 天内合并 PR
9

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

modelcontextprotocol/java-sdk 的其他 Issue

查看 modelcontextprotocol/java-sdk 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。