[
    {
        "role": "user",
        "content": "in%20vs%20code%2C%20when%20doing%20ctrl%2Bshift%2Bm%20to%20check%20syntax%2C%20I%20get%20this%20error%3AWarning%3A%20Unknown%20tool%20%27github%2Fissue_read%27.%20at%20line%208%20and%20character%2051"
    },
    {
        "role": "assistant",
        "content": "It looks like you're running into a problem where you try to use `Ctrl+Shift+M` in VS Code (which normally opens the **Problems** panel or checks syntax via an extension) and you see this error:\n\n```\nWarning: Unknown tool 'github/issue_read'. at line 8 and character 51\n```\n\nTo help you better, I need to understand a few details\u2014but meanwhile, here are the most likely causes and solutions.\n\n---\n\n## What this error suggests\n\n- **\u201cUnknown tool \u2018github/issue_read\u2019\u201d** means something is referring to a tool called `github/issue_read`, but whatever is trying to use it (a VS Code extension, linter, or an agent) doesn't recognize that tool.\n- `issue_read` is part of **GitHub MCP (Model Context Protocol)** tools. These tools let AI agents or extensions access GitHub data (issues, pull requests, file contents, etc.) in a structured way. ([github.blog](https://github.blog/changelog/2025-12-10-the-github-mcp-server-adds-support-for-tool-specific-configuration-and-more/?utm_source=openai))\n\n---\n\n## Why you\u2019re seeing it when pressing Ctrl+Shift+M\n\n`Ctrl+Shift+M` in VS Code opens the **Problems** view, showing syntax or compilation errors reported by your configured tools (like linters or compiler diagnostics). If you have an extension or configuration that integrates with GitHub MCP tools (e.g. an AI assistant, Copilot plugin, etc.), it might be trying to use `issue_read` during its checks. If the tool isn\u2019t properly enabled or configured, you\u2019ll get that \u201cUnknown tool\u201d error.\n\n---\n\n## Possible reasons & what to check\n\nHere are some likely causes and how to troubleshoot them:\n\n1. **Missing or misconfigured GitHub MCP server / tools**  \n   - The tool `github/issue_read` must be enabled in your MCP setup. If it\u2019s not in the `toolsets` or `tools` list, the server won\u2019t acknowledge it. ([trendshift.io](https://trendshift.io/admin/repository/ask-ai/14049?utm_source=openai))  \n   - Make sure your environment variables or config (`GITHUB_TOOLSETS`, `GITHUB_TOOLS`) include `issues` or `issue_read` specifically. ([trendshift.io](https://trendshift.io/admin/repository/ask-ai/14049?utm_source=openai))\n\n2. **Version mismatch**  \n   - The MCP server may have been updated and certain tools renamed or consolidated. For example, GitHub MCP v0.20.0 recently consolidated several issue-related tools into `issue_read`, with multiple methods like `get`, `get_comments`, etc. If your client is referring to an old name, you'll get the error. ([newreleases.io](https://newreleases.io/project/github/github/github-mcp-server/release/v0.20.0?utm_source=openai))\n\n3. **Extension not using updated MCP schema**  \n   - The extension or plugin in VS Code you're using might expect an older schema or use deprecated names, so it tries calling something like `github/issue_read` incorrectly.  \n\n4. **Permissions or access issues**  \n   - Even if the tool is enabled, sometimes lacking permissions (GitHub token scopes, server read-only mode, etc.) can cause a tool to be inaccessible. But typically that gives a different error message, not \u201cunknown tool\u201d.\n\n---\n\n## What you can do\n\nHere are steps to fix this:\n\n1. **Inspect your MCP configuration**\n\n   - If you're using a local or remote GitHub MCP server, check the settings. Look for `GITHUB_TOOLSETS` and `GITHUB_TOOLS`. Ensure that `issues` are in the toolsets, or that `issue_read` is explicitly included. Example:\n     ```\n     GITHUB_TOOLSETS=\"repos,issues,users\"\n     GITHUB_TOOLS=\"get_file_contents,issue_read\"\n     ```\n   - Or, if using command-line flags / `mcp.json`, ensure it\u2019s correctly declared. ([trendshift.io](https://trendshift.io/admin/repository/ask-ai/14049?utm_source=openai))\n\n2. **Check version compatibility**\n\n   - Check which version of GitHub MCP Server you\u2019re running. If it\u2019s older, it may not support the newer `issue_read` naming. Or the client tool might be ahead. Upgrading both to compatible versions usually helps. ([newreleases.io](https://newreleases.io/project/github/github/github-mcp-server/release/v0.20.0?utm_source=openai))\n\n3. **Inspect the plugin/extension**\n\n   - If a VS Code extension (like Copilot, an AI agent, or something custom) is making the call, see its configuration or logs. Ensure it refers to `issue_read` instead of older deprecated names.\n   - Also verify that your GitHub token or credentials give enough permissions, and that any server settings (read-only, lockdown) are suitable. ([apigene.ai](https://apigene.ai/mcp/official/github?utm_source=openai))\n\n4. **Check line 8, character 51**\n\n   - The error points to a specific location (\u201cline 8, char 51\u201d)\u2014likely in a config file. Open that file and see what reference is there. Maybe a typo, wrong path, or using `github/issue_read` instead of the correct identifier expected by the MCP server.\n\n---\n\nIf you tell me:\n\n- which extensions/plugins you\u2019ve installed that use GitHub or AI agent functionality  \n- how you have `toolsets` / `tools` configured (or what your `mcp.json` / environment variables look like)  \n- the version of the GitHub MCP Server you're using\n\nI can walk you through a precise fix. Do you want me to help with that?"
    }
]