You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 62f2da8
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -616,6 +616,10 @@ The following sets of tools are available:
616
616
617
617
## Tools
618
618
619
+
Repository tools expose output schemas and typed `structuredContent` to clients using MCP protocol `2026-07-28` or later. Older clients, or clients with an unknown protocol version, receive the existing content without an output schema or structured output.
620
+
621
+
For `get_file_contents`, directory results (including field projections) are structured arrays. File downloads and metadata-only responses use a `content` array of typed text, embedded-resource, or resource-link blocks, preserving status messages, text, base64 blobs, empty files, and download links. Text-only repository mutations such as starring and deletion also return a structured `message`; fork responses distinguish a repository reference from an in-progress message. Repository deletion still requires its existing confirmation flow before returning a completed result.
622
+
619
623
The issue metadata (`list_issue_types`, `list_issue_fields`), comment (`add_issue_comment`, `update_issue_comment`), dependency (`issue_dependency_read`, `issue_dependency_write`), and duplicate-detection (`find_duplicate`) tools provide typed `outputSchema` and `structuredContent` for protocol `2026-07-28` and newer. Older or unknown protocol versions retain the same text responses without these fields. Tool errors do not return structured content. Dependency and duplicate-detection tools retain their existing feature gates.
"description": "Create or update a single file in a GitHub repository. \nIf updating, you should provide the SHA of the file you want to update. Use this tool to create or update a file in a GitHub repository remotely; do not use it for local file operations.\n\nTo obtain the current blob SHA before updating, call the get_file_contents tool with the same owner, repo, and path, and set its ref parameter to this tool's branch value. The first text result reports the blob SHA for the requested path.\n\nSHA MUST be provided for existing file updates.\n",
"description": "Set true to update a symbolic link itself; content must be its new target path.",
25
+
"type": "boolean"
26
+
},
27
+
"branch": {
28
+
"description": "Branch to create/update the file in",
29
+
"type": "string"
30
+
},
31
+
"content": {
32
+
"description": "Content of the file, exactly as it should appear once written. Do not base64-encode it; this server does that before calling the REST API.",
33
+
"type": "string"
34
+
},
35
+
"message": {
36
+
"description": "Commit message",
37
+
"type": "string"
38
+
},
39
+
"owner": {
40
+
"description": "Repository owner (username or organization)",
41
+
"type": "string",
42
+
"x-mcp-header": "owner"
43
+
},
44
+
"path": {
45
+
"description": "Path where to create/update the file",
46
+
"type": "string"
47
+
},
48
+
"repo": {
49
+
"description": "Repository name",
50
+
"type": "string",
51
+
"x-mcp-header": "repo"
52
+
},
53
+
"sha": {
54
+
"description": "The blob SHA of the file being replaced. Required if the file already exists. Retrieve it with get_file_contents using the same owner, repo, and path, with ref set to this tool's branch value.",
0 commit comments