Cannot see tools?

[TotalLag]

First off, great project! I'm just starting my Ionic journey so this was awesome to find.

I'm running into a bit of a weird problem. When I run the npx command manually, I can see all the tools listed. However, when I add the MCP server to KiloCode (VSCode) the server shows that it's green and connected, but I'm not seeing any of the tools listed. The logs show that it is indeed reaching out to Github:

Loaded 82 CapGo plugins from GitHub
today at 5:50 PM
Loaded 31 Capacitor Community plugins from GitHub
today at 5:50 PM
Loaded 66 CapAwesome plugins from capawesome.io. Insider plugins: 21
today at 5:50 PM
Loaded 34 official Capacitor plugins
today at 5:49 PM
Loaded 95 Core Ionic UI components from JSON. Ionic version: 8.7.14
today at 5:49 PM
Ionic MCP Server is running
today at 5:49 PM

My config:

{
  "awesome-ionic-mcp": {
    "command": "npx",
    "args": [
      "-y",
      "awesome-ionic-mcp@latest"
    ],
    "env": {
      "GITHUB_TOKEN": "<redacted>"
    },
    "alwaysAllow": [
      "get_ionic_component_definition",
      "get_all_ionic_components",
      "get_component_api",
      "get_all_official_plugins",
      "get_official_plugin_api"
    ],
    "disabled": false,
    "type": "stdio"
  }
}

[Tommertom]

Thanks for reporting. I am looking into it

[Tommertom]

Vscode shows me this, so the tools seem visible. I did publish an update but did not explicitly addressed your issue.

I can have an agent give you debugging suggestions? Or you want to try yourself?

[hkng]

same problem. @Tommertom, can you use following tool to test your tool

npx -y @modelcontextprotocol/inspector npx -y awesome-ionic-mcp@latest

[ValderramaCode]

First off, thank you @Tommertom for the great tool here—it has saved me a lot of time and effort 🚀 😃

I ran into the same issue when using with npx. Weirdly, when I tried running it locally, I couldn't reproduce it.

After comparing the lockfiles from the NPX environment and my local installation, I found that the @modelcontextprotocol/sdk package is resolved to an older version in the NPX environment. In the screenshot below, the left side shows the published package's lockfile, while the right side shows the local lockfile:

I should add that I also tried using this older SDK version locally, and it worked as well. So I don't know the exact cause of the issue—this is simply the only meaningful difference I was able to find.

Anyway, @Tommertom, could you try republishing the package?

Before doing so, I would suggest deleting node_modules, removing @modelcontextprotocol/sdk from package.json, running npm install, then adding the dependency back and running npm install again. This should ensure that the latest SDK version is resolved and included in the published package.

PS: Forgot to mention. Using Opencode or the inspector, both of them worked when running locally. But, both failed to retrieve the tools when using the one from NPX environment.