Addressing GitHub MCP's Key Issues: Token Scopes, Verbose Prompts, and Lack of Project Context

I’d like to share some practical difficulties I’ve encountered while using GitHub MCP, which affect both usability and workflow efficiency:

1. **Restricted Token Scope in Private Repos**
Even when invited to a private repository, my GitHub MCP token could not be used to access issues or pull requests within that project. This seems like a token permission issue and has been reported as a potential token-scope limitation.

2. **Overly Redundant and LLM-Unfriendly Prompts**
The prompts generated by GitHub MCP are often unnecessarily verbose and repetitive, making it difficult for LLMs to interact with it smoothly. This results in slower, less precise responses in agentic workflows.

3. **No Built-in “Current Project” Focus**
GitHub MCP lacks a sense of contextual focus on the specific repository I’m working in. I’d prefer a tool that automatically centers on the current project’s issues and pull requests—similar to how `gh` CLI operates within a local Git context.

These limitations make me wonder whether a solution like **opencode** could be designed to offer more targeted, context-aware interaction—essentially combining the directness of `gh` with the extensibility of an agent-friendly SDK.

Has there been any discussion about enabling opencode to handle repository-scoped issues/PRs with the kind of focused, lightweight interaction that GitHub MCP currently lacks?