A simply MCP server connection issue

[fahadshery]

Hi,

I have been asked to ask questions here.
Here is the issue: #683

I did the following as per the recommendation:

❯ llxprt mcp add filesystem npx -- "@modelcontextprotocol/server-filesystem" "/tmp"
MCP server "filesystem" is already configured within project settings.
MCP server "filesystem" updated in project settings.

then

llxprt

If I try to see the MCP server I get the following:

can any one give step by step guide on how to add an MCP?

Mind you that these MCPs are working without any issues in the original gemini-cli tool

[e2720pjk]

Hi~ This has been confirmed as an issue in the new version
If you need to use it urgently, please switch to v0.5.0
Its usage is stable and does not differ from gemini-cli
A fix is in progress on PR: #691, so kindly wait for the upcoming update.🙏

[e2720pjk]

The fix has already been released in the latest version. Feel free to give it a try😌

npm install -g @vybestack/llxprt-code@v0.6.1-nightly.251130.1e208436b

[fahadshery]

I can confirm that the MCP's are registering and working :)

However, you still have problem with the /ide extension.

I get the following in the VScode:

[LittleYe233]

I tried the branch of #704 and seemed that llxprt could connect to IDE extension (also need to package the latest vsix extension and manually install it in VS Code), but failed to make MCP work:

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'keytar' imported from /usr/lib/llxprt/llxprt.js
    at Object.getPackageJSONURL (node:internal/modules/package_json_reader:316:9)
    at packageResolve (node:internal/modules/esm/resolve:768:81)
    at moduleResolve (node:internal/modules/esm/resolve:858:18)
    at defaultResolve (node:internal/modules/esm/resolve:990:11)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:712:20)
    at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:729:38)
    at ModuleLoader.resolveSync (node:internal/modules/esm/loader:758:52)
    at #resolve (node:internal/modules/esm/loader:694:17)
    at ModuleLoader.getOrCreateModuleJob (node:internal/modules/esm/loader:614:35)
    at onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:643:32) {
  code: 'ERR_MODULE_NOT_FOUND'
}
Error during discovery for server 'context7': Connection failed for 'context7': Token file does not exist

I am not sure if there is anything wrong here.

[acoliver]

@LittleYe233 created this issue #770 - will fix in 0.7.0 (probably days away) or probably tomorrow's nightly.

[LittleYe233]

@acoliver Seems that the newest nightly version works. Thank you all!

[acoliver]

Humm I didnt fix it yet 😅

[LittleYe233]

So maybe there is really something wrong in my environment and nothing wrong in the codebase... At least the current version works well.