Skip to content

[Feedback][VS2026] IDE "always allow" for tools seems to be adding wrong tool name Entries which could potentially cause MCP tool call issues #126

@DevTKSS

Description

@DevTKSS

Current behavior

I did just notice this, as I was tired of configuring this per tool call drop down, therefore I was adding the tool names manually in VS2026 Options > GitHub > Copilot where I seen this strange thing:

Image Image Image

I would not think, that your Uno MCP docs are stating the wrong name, so this defintly seems to be a issue in my opinion!

manually added tool names are untouched

Image

while removing the "wrong" named tools + restarting VS2026 IDE, resets the setting in copilot pane to "Always ask" 👀

Image

(applyes to all nested tools the same, just took one screenshot)

Expected behavior

Should have been:

  • uno_app_get_screenshot
  • uno_app_get_runtime_info
  • uno_platform_docs_search
  • ...

Which tool(s) are affected?

All Uno MCP Tools

How to reproduce it (as minimally and precisely as possible)

I don't know, if this is (still) reproducable or maybe a past VS issue, which might have been solved by now (before adding them now Manually):

  1. Be in the regular Copilot Chat pane and ask copilot for something it should be using one of the Uno MCP Tools for
  2. It (should) be prompting you to allow the execution of this tool and you get the drop-down to choose "One time (default) / "In this Solution" (or similar) / "Always"
  3. I did first times choose first and second option, but in the end click on "Always" (dont know if this changes the outcome for the bug)

Workaround

add them manually - doing this now on my side

Renderer

  • Skia
  • Native

Affected platforms

No response

Uno.Sdk version

6.4.42

IDE used

Visual Studio 2022

IDE version

VS 2026 18.1.1

Uno Platform Extension version

6.4.20.20

Relevant plugins

No response

Anything else we need to know?

The Report Template doesn't provide the VS 2026 IDE then only 2022! Please update this

Possibly this wrong tool-name adding from the copilot pane is resulting in the uno-app MCP is rarely showing up on my side 🤔 but not sure! Could someone investigate why this is happening? not happening with the normal uno mcp 👍

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions