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
Copy file name to clipboardExpand all lines: README.md
+14-1Lines changed: 14 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1118,7 +1118,7 @@ The following sets of tools are available:
1118
1118
3. get_status - Get combined commit status of a head commit in a pull request.
1119
1119
4. get_files - Get the list of files changed in a pull request. Use with pagination parameters to control the number of results returned.
1120
1120
5. get_review_comments - Get review threads on a pull request. Each thread contains logically grouped review comments made on the same code location during pull request reviews. Returns threads with metadata (isResolved, isOutdated, isCollapsed) and their associated comments. Use cursor-based pagination (perPage, after) to control results.
1121
-
6. get_reviews - Get the reviews on a pull request. When asked for review comments, use get_review_comments method.
1121
+
6. get_reviews - Get the reviews on a pull request. When asked for review comments, use get_review_comments method. Use with pagination parameters to control the number of results returned.
1122
1122
7. get_comments - Get comments on a pull request. Use this if user doesn't specifically want review comments. Use with pagination parameters to control the number of results returned.
1123
1123
8. get_check_runs - Get check runs for the head commit of a pull request. Check runs are the individual CI/CD jobs and checks that run on the PR.
1124
1124
(string, required)
@@ -1274,6 +1274,14 @@ The following sets of tools are available:
1274
1274
-`perPage`: Results per page for pagination (min 1, max 100) (number, optional)
1275
1275
-`repo`: Repository name (string, required)
1276
1276
1277
+
-**list_repository_collaborators** - List repository collaborators
1278
+
-**Required OAuth Scopes**: `repo`
1279
+
-`affiliation`: Filter by affiliation. Can be one of: 'outside' (outside collaborators), 'direct' (all with permissions regardless of org membership), 'all' (all collaborators). Default: 'all' (string, optional)
1280
+
-`owner`: Repository owner (string, required)
1281
+
-`page`: Page number for pagination (default 1, min 1) (number, optional)
1282
+
-`perPage`: Results per page for pagination (default 30, min 1, max 100) (number, optional)
1283
+
-`repo`: Repository name (string, required)
1284
+
1277
1285
-**list_tags** - List tags
1278
1286
-**Required OAuth Scopes**: `repo`
1279
1287
-`owner`: Repository owner (string, required)
@@ -1431,6 +1439,11 @@ The following sets of tools are available:
1431
1439
1432
1440
<summary>Copilot Spaces</summary>
1433
1441
1442
+
-**Authentication note**
1443
+
- Fine-grained PATs are not hidden by classic PAT scope filtering, so these tools may still appear even when the token cannot use them.
1444
+
- For org-owned spaces, fine-grained PATs must be installed on the owning organization and include `organization_copilot_spaces: read`.
1445
+
- If an org-owned space contains repository-backed resources, the token must also have access to every referenced repository or the space may be treated as not found.
1446
+
1434
1447
-**get_copilot_space** - Get Copilot Space
1435
1448
-`owner`: The owner of the space. (string, required)
1436
1449
-`name`: The name of the space. (string, required)
Copy file name to clipboardExpand all lines: docs/installation-guides/install-claude.md
+69-1Lines changed: 69 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -164,7 +164,75 @@ Add this codeblock to your `claude_desktop_config.json`:
164
164
165
165
---
166
166
167
-
## Troubleshooting
167
+
## Xcode (Claude Agent)
168
+
169
+
Xcode's Claude Agent uses the same `.claude.json` configuration format as the Claude Code CLI, but reads it from an Xcode-specific directory rather than the global config location.
> Configurations placed here only affect Claude Agent when launched from Xcode. See [Apple's documentation](https://developer.apple.com/documentation/xcode/setting-up-coding-intelligence#Customize-the-Claude-Agent-and-Codex-environments) for more details.
178
+
179
+
### Remote Server Setup (Recommended)
180
+
181
+
Run the following command in Terminal to add the remote GitHub MCP server:
182
+
183
+
```bash
184
+
claude mcp add-json github '{"type":"http","url":"https://api.githubcopilot.com/mcp/","headers":{"Authorization":"Bearer YOUR_GITHUB_PAT"}}' --config ~/Library/Developer/Xcode/CodingAssistant/ClaudeAgentConfig/.claude.json
185
+
```
186
+
187
+
Or open the file in a text editor and add the `mcpServers` block manually:
188
+
189
+
```json
190
+
{
191
+
"mcpServers": {
192
+
"github": {
193
+
"type": "http",
194
+
"url": "https://api.githubcopilot.com/mcp/",
195
+
"headers": {
196
+
"Authorization": "Bearer YOUR_GITHUB_PAT"
197
+
}
198
+
}
199
+
}
200
+
}
201
+
```
202
+
203
+
### Local Server Setup (Docker)
204
+
205
+
> **macOS note**: Xcode runs with a minimal `PATH` that typically excludes `/usr/local/bin` (Intel) and `/opt/homebrew/bin` (Apple Silicon). Use the full path to `docker` to ensure it can be found. Run `which docker` in Terminal to find the correct path on your system.
206
+
207
+
```json
208
+
{
209
+
"mcpServers": {
210
+
"github": {
211
+
"command": "/usr/local/bin/docker",
212
+
"args": [
213
+
"run",
214
+
"-i",
215
+
"--rm",
216
+
"-e",
217
+
"GITHUB_PERSONAL_ACCESS_TOKEN",
218
+
"ghcr.io/github/github-mcp-server"
219
+
],
220
+
"env": {
221
+
"GITHUB_PERSONAL_ACCESS_TOKEN": "YOUR_GITHUB_PAT"
222
+
}
223
+
}
224
+
}
225
+
}
226
+
```
227
+
228
+
### Setup Steps
229
+
1. Create or open `~/Library/Developer/Xcode/CodingAssistant/ClaudeAgentConfig/.claude.json`
230
+
2. Add the configuration block above
231
+
3. Replace `YOUR_GITHUB_PAT` with your actual token
Xcode currently supports two built-in coding agents: **Codex** (powered by OpenAI) and **Claude Agent** (powered by Anthropic). Follow the standard installation guide for each agent, with one important difference: Xcode uses its own isolated configuration directories for each agent, separate from your global config.
4
+
5
+
> Configurations placed in these directories only affect agents when launched from Xcode. See [Apple's documentation](https://developer.apple.com/documentation/xcode/setting-up-coding-intelligence#Customize-the-Claude-Agent-and-Codex-environments) for more details.
Xcode runs with a minimal `PATH` that typically excludes common binary locations. If you are using a local STDIO server (e.g. Docker or a pre-built binary), use the **full path** to the command in your config. Run `which docker` (or `which github-mcp-server`) in Terminal to find the correct path on your system. Common locations:
| Tools not loading | Config placed in wrong directory | Ensure config is in the Xcode-specific path above, not `~/.codex/` or `~/.claude.json`|
37
+
| Command not found (STDIO) | Xcode's PATH excludes binary location | Use the full path (e.g. `/usr/local/bin/docker` or `/opt/homebrew/bin/docker`); run `which docker` in Terminal to confirm |
38
+
| Docker not found | Docker not running | Start Docker Desktop and restart Xcode |
39
+
| Authentication failed | Invalid or expired PAT | Regenerate PAT and update config |
40
+
41
+
## References
42
+
43
+
-[Apple Developer Documentation — Setting up coding intelligence](https://developer.apple.com/documentation/xcode/setting-up-coding-intelligence#Customize-the-Claude-Agent-and-Codex-environments)
"description": "List collaborators of a GitHub repository. Results are paginated; the response includes `nextPage`, `prevPage`, `firstPage`, and `lastPage` fields. To get the next page, use the `nextPage` value as the `page` parameter.",
7
+
"inputSchema": {
8
+
"properties": {
9
+
"affiliation": {
10
+
"description": "Filter by affiliation. Can be one of: 'outside' (outside collaborators), 'direct' (all with permissions regardless of org membership), 'all' (all collaborators). Default: 'all'",
11
+
"enum": [
12
+
"outside",
13
+
"direct",
14
+
"all"
15
+
],
16
+
"type": "string"
17
+
},
18
+
"owner": {
19
+
"description": "Repository owner",
20
+
"type": "string"
21
+
},
22
+
"page": {
23
+
"description": "Page number for pagination (default 1, min 1)",
24
+
"minimum": 1,
25
+
"type": "number"
26
+
},
27
+
"perPage": {
28
+
"description": "Results per page for pagination (default 30, min 1, max 100)",
Copy file name to clipboardExpand all lines: pkg/github/__toolsnaps__/pull_request_read.snap
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@
7
7
"inputSchema": {
8
8
"properties": {
9
9
"method": {
10
-
"description": "Action to specify what pull request data needs to be retrieved from GitHub. \nPossible options: \n 1. get - Get details of a specific pull request.\n 2. get_diff - Get the diff of a pull request.\n 3. get_status - Get combined commit status of a head commit in a pull request.\n 4. get_files - Get the list of files changed in a pull request. Use with pagination parameters to control the number of results returned.\n 5. get_review_comments - Get review threads on a pull request. Each thread contains logically grouped review comments made on the same code location during pull request reviews. Returns threads with metadata (isResolved, isOutdated, isCollapsed) and their associated comments. Use cursor-based pagination (perPage, after) to control results.\n 6. get_reviews - Get the reviews on a pull request. When asked for review comments, use get_review_comments method.\n 7. get_comments - Get comments on a pull request. Use this if user doesn't specifically want review comments. Use with pagination parameters to control the number of results returned.\n 8. get_check_runs - Get check runs for the head commit of a pull request. Check runs are the individual CI/CD jobs and checks that run on the PR.\n",
10
+
"description": "Action to specify what pull request data needs to be retrieved from GitHub. \nPossible options: \n 1. get - Get details of a specific pull request.\n 2. get_diff - Get the diff of a pull request.\n 3. get_status - Get combined commit status of a head commit in a pull request.\n 4. get_files - Get the list of files changed in a pull request. Use with pagination parameters to control the number of results returned.\n 5. get_review_comments - Get review threads on a pull request. Each thread contains logically grouped review comments made on the same code location during pull request reviews. Returns threads with metadata (isResolved, isOutdated, isCollapsed) and their associated comments. Use cursor-based pagination (perPage, after) to control results.\n 6. get_reviews - Get the reviews on a pull request. When asked for review comments, use get_review_comments method. Use with pagination parameters to control the number of results returned.\n 7. get_comments - Get comments on a pull request. Use this if user doesn't specifically want review comments. Use with pagination parameters to control the number of results returned.\n 8. get_check_runs - Get check runs for the head commit of a pull request. Check runs are the individual CI/CD jobs and checks that run on the PR.\n",
Copy file name to clipboardExpand all lines: pkg/github/__toolsnaps__/update_issue_type.snap
+5Lines changed: 5 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,11 @@
20
20
"description": "Repository owner (username or organization)",
21
21
"type": "string"
22
22
},
23
+
"rationale": {
24
+
"description": "One concise sentence explaining what specifically about the issue led you to choose this type. State the concrete signal (e.g. 'Reports a crash when saving' → bug, 'Asks for dark mode support' → feature).",
0 commit comments