mongodb-js/mongodb-mcp-server

[Bug]: Warp MPC Client Config Error

Closed this issue · 2 comments

ncbooth commented

Version

0.1.2

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

Whenever attempting to connect via the Warp MPC feature I receive a response indicating missing config.

2025-06-28 23:21:50.921 | [info] MCP CLI: Spawned MCP server with pid 50866
2025-06-28 23:21:50.921 | [info] MCP CLI: Sending request: {"jsonrpc":"2.0","id":47,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"warp","version":"1.0.0"}}}
2025-06-28 23:21:51.340 | [info] MCP CLI: Received response: {"result":{"protocolVersion":"2024-11-05","capabilities":{"logging":{},"tools":{"listChanged":true},"resources":{"listChanged":true},"completions":{}},"serverInfo":{"name":"MongoDB MCP Server","version":"0.1.2"}},"jsonrpc":"2.0","id":47}

2025-06-28 23:21:51.340 | [info] MCP CLI: Sending notification: "{"jsonrpc":"2.0","method":"notifications/initialized"}"
2025-06-28 23:21:51.340 | [info] MCP CLI: Sending request: {"jsonrpc":"2.0","id":48,"method":"resources/list","params":{}}
2025-06-28 23:21:51.345 | [info] MCP CLI: Received response: {"result":{"resources":[{"uri":"config://config","name":"config","description":"Server configuration, supplied by the user either as environment variables or as startup arguments"}]},"jsonrpc":"2.0","id":48}

The connection string I'm passing works in mongosh and compass, and if i mangle the protocol I get a schema error so I know I'm passing the connection string correctly.

The database is an atlas cluster running 8.1.1, so I've tried +svr and old style connection strings. It seems to have the same behavior in Docker or npx.

himanshusinghs commented

Hi @ncbooth! Thanks for reporting this.

From the logs it seems warp is not sending any other request after requesting a list of the resources. I tested the warp mcp setup myself as well and even after several retries, warp mcp client always marks the server failed to start right after requesting the list of the resources.

But the server seems to be running fine (verified that using docker run method). Additionally, the MCP configuration that Warp fails to work with, works fine with other clients (tested VSCode, Cursor and Claude Desktop).

I would say that its a bug in how Warp tries to initialise their MCP connections so I would advice raising an issue on their issue board. Feel free to cross reference this issue over there as well for added context.

Let me know if I missed out on something crucial but otherwise I think you should go with the suggested approach, raise an issue on Warp's Issue board. Thanks :)

github-actions commented

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!