MCP server not working

Help Something Else
1

Hi Team,
I have created MCP server it was working fine previously but from yesterday its not working i tried with different MCP but i think there is some issue with UiPath side
for reference attaching screenshot

image
image1169×704 73.2 KB

image
image1166×686 54.7 KB

Anyone know why this happening?

2

@akash-revansiddh.javaleka

Try logout and login from assistant and orchestrator.

Let me know if this works

Happy Automation

3

Already did isuse is with npm package from UiPath side i belive

4

@akash-revansiddh.javaleka

Try creating another sample MCP server and deploying. If that also don’t work, then it could be from UiPath side.

5

Tried that as well same issue

6

@loginerror could you please redirect this to correct point of contact in this case?

@akash-revansiddh.javaleka meanwhile please share all the logs you can share also the UiPath organisation name, tenant etc which will be helpful to team to troubleshoot this.

7

Hey @akash-revansiddh.javaleka

I will check with the team, I think it is indeed a bug.

In the meantime, one thing you might want to just give a shot (no promises), is to try to override the bad env variable via the env config of your MCP server:

  "env": {
    "NPM_CONFIG_IGNORE_SCRIPTS": "false",   // the likely real fix
    "NPM_CONFIG_MIN_RELEASE_AGE": "",       // silences the invalid-config warning
    "NPM_CONFIG_ALLOW_GIT": "true"          // only if a dependency uses a git: spec
  }

It’s a Claude Code suggestion, but I didn’t want to leave you without anything in the meantime.

9

Also, @akash-revansiddh.javaleka, would you mind sharing with me the /tmp/home/.npm/_logs/…debug-0.log log file? It might speed things up.

10

Thanks for the quick reply please find the logs from orchestrator
Error_Logs.txt (11.2 KB)

11

I tried this approach but still getting same error.
Let me know if you have any other workaround

Thanks

12

Hi @akash-revansiddh.javaleka

Good news, the team found and fixed the issue and it will be hot fixed.

If you are really impatient, I have another suggestion that might allow you to skip the wait time for that deployment:

Change the MCP server definition from command: npx to a shell wrapper that points npm at a different (non-existent → empty) global config, so the broken /usr/local/etc/npmrc is never parsed:

  "command": "sh",
  "args": \["-c", "exec env NPM_CONFIG_GLOBALCONFIG=/tmp/none.npmrc npx -y @modelcontextprotocol/server-filesystem /tmp"\]
13

@loginerror
That’s awesome this would really helpful let me try this approach

14

Just a proper disclaimer: this is just a hopeful stop-gap dirty workaround that should be reverted as soon as we deploy the fix :slight_smile: This is not a way to run things in production.

15

Hi @loginerror yes understoood! Actually tomorrow we have community event on MCP session for that purpose only i was looking workaround.

Thanks & Regards,
Akash Javalekar

16

It worked Thank you so much for quick support