It would be great if Jan.ai didn't require an internet connection to use local tools/MCP

[wh33t]

As of right now, it's taken me a while to troubleshoot this specific issue, but I have noticed that if I am offline and I try to enable filesystem tool it fails with an error message. If I connect and go online, then enable it, it enables correctly, and going back offline permits the tool use to work offline.

In other words, Jan.ai must connect to the internet at least once per session otherwise the filesystem mcp tool cannot function. I don't personally understand why it works this way, but if it doesn't have to, it would be a hugely appreciated.

I am generally not permitted to have Jan.ai connected to the internet while working on company IP or sensitive records.

[morvayo]

if your filesystem server uses the default npx -y @modelcontextprotocol/server-filesystem launcher then the package launcher can need the registry even though the server itself only reads local files default config preinstall a fixed version of that server and its dependencies in your approved environment then configure Jan to run its local entry point with an absolute path to node instead of npx that removes package resolution from each startup if your command is already a local executable the startup error would help identify a different cause

[wh33t]

preinstall a fixed version of that server and its dependencies in your approved environment then configure Jan to run its local entry point with an absolute path to node instead of npx that removes package resolution from each startup if your command is already a local executable the startup error would help identify a different cause

I am not sure how to do that, but I'll give it a go, I bet Jan.ai itself can tell me the steps. I'll report back.

[wh33t]

if your filesystem server uses the default npx -y @modelcontextprotocol/server-filesystem launcher then the package launcher can need the registry even though the server itself only reads local files default config preinstall a fixed version of that server and its dependencies in your approved environment then configure Jan to run its local entry point with an absolute path to node instead of npx that removes package resolution from each startup if your command is already a local executable the startup error would help identify a different cause

I sat down to try and make these changes and seen that a new version of Jan.ai was released. The issue appears to be fixed and requires no effort on my part. Cheers.