SEP-2640: Skills Extension

Offen

#1,140 erstellt am 22.9.2026 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit: 4/5
Geschätzter Aufwand: 3-5 Tage
Anfängerfreundlichkeit: 40/100

Issue-Typ: Feature
Klarheit: Klar beschrieben
Aktivitätsstatus: Aktiv
Tech-Stack: java
Bereich: api, backend

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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:

Python SDK: python-sdk#3485
C# SDK: csharp-sdk#1856
Go SDK: go-sdk#1238

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.

Vorherrschende Sprache: Java
Sterne: 3.7k
Forks: 1.1k
Ø Merge: 1 T. 15 Std.
Gemergte PRs (30 T.): 9

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
Forken Sie das Repository und arbeiten Sie in einem Branch.
Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus modelcontextprotocol/java-sdk

SSE client silently truncates a data: line at U+2028/U+2029/U+0085, then fails with "Error parsing JSON-RPC message" Offen

area/transport bug P2

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100

modelcontextprotocol/java-sdk#1136 · Erstellt am 18.9.2026
Client request handlers that complete empty send no JSON-RPC response Offen

area/client bug P2

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100

modelcontextprotocol/java-sdk#1124 · 1 Kommentar · Erstellt am 03.9.2026
ServerCapabilities.logging is added unconditionally, overriding the caller's explicit capabilities Offen

bug P2 ready for work

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100

modelcontextprotocol/java-sdk#1086 · 1 Kommentar · Erstellt am 11.8.2026
Reject listRoots if not supported by client, without sending any request Offen

enhancement good first issue P3

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100

modelcontextprotocol/java-sdk#1067 · Erstellt am 19.7.2026
StdioClientTransport missing explicit UTF-8 charset in InputStreamReader (same issue as #295, but on client side) Offen

bug P2 ready for work

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100

modelcontextprotocol/java-sdk#898 · 1 Kommentar · Erstellt am 02.4.2026

Alle Issues in modelcontextprotocol/java-sdk