mongodb-js/mongodb-mcp-server

[Bug]: no tools enabled

Closed this issue · 5 comments

Version

latest

App

  • Cursor
  • Windsurf
  • VSCode
  • VSCode Insiders
  • Claude Desktop
  • Other

Affected Models (if applicable)

  • Claude 3.5 Sonnet
  • Claude 3.7 Sonnet
  • GPT-4a
  • o4-mini
  • Other

Bug Description

when trying to connect {
"mcpServers": {
"Figma": {
"url": "http://127.0.0.1:3845/sse"
},
"MongoDB": {
"command": "npx",
"args": ["-y", "mongodb-mcp-server"],
"env": {
"MDB_MCP_CONNECTION_STRING": "mongodb://localhost:27017/kenco_development"
}
}
}
}

blva commented

hey @inampersan , the MCP server usually fails when the connection string is invalid. Are you able to grab the logs from the server to help figure out what's happening? I also suggest checking if you're able to connect to this connection string with other tools to validate it, e.g. mongosh.

Have the same issue. The connection string (copy-pasted) works fine with mongosh

We are unfortunately not able to reproduce the problem just by having a mongodb connection string provided as an environment variable.

@inampersan It would be really helpful if you could provide:

  1. logs from your mongodb server, perhaps the new ones, once your MCP client in cursor attempts to connect and fail
  2. MCP logs from your Cursor. These can generally be accessed via the Output panel (Menu bar -> View -> Output) and then selecting "MCP Logs" from the dropdown (all the way to the top right of the panel). There might be something useful logged there.

@dhammma in addition to the points above could you share how you are setting your MCP server and what application are you using to set it up?

This issue has gone 30 days without any activity and meets the project's definition of "stale". This will be auto-closed if there is no new activity over the next 30 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!