Unable to get server running on Windows 11

[JustTryAI]

I can't get the server running on Windows 11 machine

Followed Installation instructions, running

\Projects> git clone https://github.com/cyanheads/atlas-mcp-server.git

Cloning into 'atlas-mcp-server'...
remote: Enumerating objects: 850, done.
remote: Counting objects: 100% (155/155), done.
remote: Compressing objects: 100% (96/96), done.
remote: Total 850 (delta 66), reused 123 (delta 50), pack-reused 695 (from 1)
Receiving objects: 100% (850/850), 647.55 KiB | 6.47 MiB/s, done.
Resolving deltas: 100% (388/388), done.

\Projects> cd atlas-mcp-server

\Projects\atlas-mcp-server> npm install

npm warn deprecated @types/winston@2.4.4: This is a stub types definition. winston provides its own type definitions, so you do not need this installed.
npm warn deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated npmlog@6.0.2: This package is no longer supported.
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported.
npm warn deprecated gauge@4.0.4: This package is no longer supported.

atlas-mcp-server@1.1.0 prepare
npm run build

atlas-mcp-server@1.1.0 build
tsc && node --eval "import('fs').then(fs => fs.promises.chmod('build/index.js', '755'))"

I edited package.json and changed line 14 to
"build": "tsc",

Then I try again, and don't get any errors
\Projects\atlas-mcp-server> npm install

However, if I run
\Projects\atlas-mcp-server> npm run inspector

I get the console full of the below on loop

New SSE connection
Query parameters: {
transportType: 'stdio',
command: 'dist/index.js',
args: '',
env: '{[Environment Variables]}'
}
Spawned stdio transport
Connected MCP client to backing server transport
Created web app transport
Created web app transport
Set up MCP proxy

and in the WebUI, http://localhost:5173/, I don't get a list of resources like I do with other servers

Any help would be greatly appreciated

[cyanheads]

Hi there! 👋

I've just added Windows compatibility improvements in PR #8 that should hopefully resolve the installation issues you're seeing. Can you try installing again and let me know if everything works better now?

The changes include better handling of file permissions, paths, and environment variables specifically for Windows systems.

Thanks for bringing this to my attention!

[JustTryAI]

I'll take a look and let you know, ty

[JustTryAI]

Didn't work

git clone https://github.com/cyanheads/atlas-mcp-server.git

Cloning into 'atlas-mcp-server'...
remote: Enumerating objects: 1155, done.
remote: Counting objects: 100% (460/460), done.
remote: Compressing objects: 100% (257/257), done.
remote: Total 1155 (delta 232), reused 385 (delta 174), pack-reused 695 (from 1)
Receiving objects: 100% (1155/1155), 1.18 MiB | 5.20 MiB/s, done.
Resolving deltas: 100% (554/554), done.

PS C:\Users\lloyd\OneDrive\Projects> cd atlas-mcp-server

PS C:\Users\lloyd\OneDrive\Projects\atlas-mcp-server> npm install

npm warn deprecated @types/winston@2.4.4: This is a stub types definition. winston provides its own type definitions, so you do not need this installed.
npm warn deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated npmlog@6.0.2: This package is no longer supported.
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported.
npm warn deprecated gauge@4.0.4: This package is no longer supported.

atlas-mcp-server@1.1.0 prepare
npm run build

atlas-mcp-server@1.1.0 build
tsc && node --eval "import('fs').then(fs => fs.promises.chmod('build/index.js', '755'))" && (echo '# atlas-mcp-server
' && tree -I 'node_modules|.git|.DS_Store|build' --dirsfirst -F --charset ascii) > repo-tree.md

npm error code 1
npm error path C:\Users\lloyd\OneDrive\Projects\atlas-mcp-server
npm error command failed
npm error command C:\WINDOWS\system32\cmd.exe /d /s /c npm run build
npm error A complete log of this run can be found in: C:\Users\lloyd\AppData\Local\npm-cache_logs\2024-12-24T23_24_19_364Z-debug-0.log

2024-12-24T23_24_19_364Z-debug-0.log

PS C:\Users\lloyd\OneDrive\Projects\atlas-mcp-server> node -v

v20.18.0

Using Claude I've managed a to get the server running(ish)

modified package.json
{
"scripts": {
"build": "tsc && node --eval "import('fs').then(fs => fs.promises.chmod('build/index.js', 0o755).catch(() => {}))" && node scripts/generate-tree.js",
...
}
}

generate-tree.js.txt

I got an error after running npm run build - verbose

Claude recommended a changes to tsconfig.json
tsconfig.json

then installed
npm install --save-dev @types/node
npm install zod nanoid
npm install --save-dev @types/sqlite3

after running npm start I got another error
error: Fatal error during startup {"error":{"message":"{\n "name": "ReferenceError",\n "message": "require is not defined",\n "stack": "ReferenceError: require is not defined\n at main (file:///C:/Users/lloyd/OneDrive/Projects/atlas-mcp-server/build/index.js:524:26)",\n "timestamp": 1735085138124\n}","name":"ObjectError","raw":{"message":"require is not defined","name":"ReferenceError","stack":"ReferenceError: require is not defined\n at main (file:///C:/Users/lloyd/OneDrive/Projects/atlas-mcp-server/build/index.js:524:26)","timestamp":1735085138124},"timestamp":1735085138124},"timestamp":1735085138124}

Claude recommended changes to the build/index.ts
index.js.txt

This loaded something into MCP Inspector but it's mainly just errors

[TophSV]

I had the same exact issues and Claude also recommend that I edit the build package, to which I replied "lmao I can't edit the build package dude"

[cyanheads]

I've made quite a few updates and created a centralized src/utils/platform-utils to better handle Windows compatibility in Commit 129ccdd7
Pull the latest updates and try installing again. Let me know if you continue running into issues.

[JustTryAI]

I've tried it again, and while the install and build processes are a lot smoother, it's still not working as expected. The 1st screenshot below shows what I think are errors, maybe(?), in the MCP Inspector I get errors, also attached below, however, if I list tools it appears to show them correctly.
In Claude I can request it uses Atlas but it just hangs after a few seconds, attached below

[JustTryAI]

Just a note: the process eventually completed in the Claude desktop, so it may actually be working. I'll need to test further, but I don't have the time right now.

[JustTryAI]

Just tried latest build 2025-01-03 @14:26 GMT

npm install
npm warn deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated npmlog@6.0.2: This package is no longer supported.
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported.
npm warn deprecated gauge@4.0.4: This package is no longer supported.

atlas-mcp-server@1.4.0 preinstall
mkdir -p build

atlas-mcp-server@1.4.0 prepare
husky install && node scripts/postinstall.js

husky - install command is DEPRECATED
Skipping build permissions on Windows

added 366 packages, and audited 367 packages in 10s

91 packages are looking for funding
run npm fund for details

found 0 vulnerabilities

This creates an empty -p and build folder as well as the node_modules folder.

npm run build

atlas-mcp-server@1.4.0 prebuild
mkdir -p build

A subdirectory or file -p already exists.
Error occurred while processing: -p.
A subdirectory or file build already exists.
Error occurred while processing: build.

removing the prebuild line from the package.json fixed this and I was able to npm run build without further issues
"prebuild": "mkdir -p build",

[JustTryAI]

Not sure if I should log this as a separate issue.

I received an error, I think it was when Atlas was trying to write to the filesystem