René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Make `projects` toolset part of the default toolsets","articleBody":"### Describe the feature or problem you'd like to solve\n\nThe `projects` toolset is fully implemented with three tools (`projects_list`, `projects_get`, `projects_write`), but it is not included in the default toolset configuration. This means users connecting to the remote MCP server at `https://api.githubcopilot.com/mcp/` have no access to GitHub Projects v2 tools unless they know to use the `/x/projects` URL path or custom headers.\n\nThe README advertises \"Issue \u0026 PR Automation: Create, update, and manage issues and pull requests. Let AI help triage bugs, review code changes, and maintain project boards.\" — but the project board tools are not available out of the box.\n\nWhen a user asks an AI assistant to list issues on their project board (e.g., `https://github.com/orgs/myorg/projects/2/`), the assistant reports there are no tools available for GitHub Projects. This is confusing because the capability exists but is hidden behind a non-default toolset.\n\nAdditionally, Claude Desktop's connector UI (adding a server via URL) does not support custom headers or URL path modifiers, so users of that flow have no way to enable the `projects` toolset without switching to a local stdio setup.\n\n### Proposed solution\n\nMark `ToolsetMetadataProjects` with `Default: true` in `pkg/github/tools.go`, the same way `repos`, `issues`, `pull_requests`, `users`, and `context` are marked:\n\n```go\nToolsetMetadataProjects = inventory.ToolsetMetadata{\n    ID:               \"projects\",\n    Description:      \"GitHub Projects related tools\",\n    Icon:             \"project\",\n    Default:          true, // \u003c-- add this\n    InstructionsFunc: generateProjectsToolsetInstructions,\n}\n```\n\nThis would make the projects tools available by default for both the local (stdio) and remote (HTTP) server, matching the README's advertised capabilities.\n\n### Example prompts or workflows (for tools/toolsets only)\n\n1. \"List all items on my project board at https://github.com/orgs/myorg/projects/2/\"\n2. \"What issues are in the 'In Progress' column of our team project?\"\n3. \"Add issue #42 from myorg/myrepo to the team project board\"\n4. \"Update the status of the billing refactor item to 'Done' on the project board\"\n5. \"Show me the status updates for our Q2 planning project\"\n\n### Additional context\n\n- The `projects` toolset contains only 3 tools, so adding it to defaults has minimal impact on tool count.\n- The toolset has no feature flags or holdback flags gating it — it's simply not marked as default.\n- Users connecting via Claude Desktop's URL connector have no practical way to enable non-default toolsets, since the connector UI doesn't support headers or URL path parameters.\n- The workaround today requires running the local server binary with `--toolsets=default,projects` and a personal access token, which is a significant setup hurdle compared to just pasting the MCP URL.","author":{"url":"https://github.com/yani-","@type":"Person","name":"yani-"},"datePublished":"2026-03-31T02:32:21.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/2275/github-mcp-server/issues/2275"}