Recommended client except Claude Desktop

[morinies]

I've attempted to configure MongoDB Lens with multiple clients:

• goose-cli
• goose-desktop
• continue.dev

Both npx and Docker setup approaches

The MongoDB Lens server appears to be running correctly:

Loading config file: /root/.mongodb-lens.json
MongoDB Lens v9.1.4 starting…
Connecting to MongoDB at: mongodb://root:********@someExternalServer.com:27017
Connected to MongoDB server version: 7.0.12
Connected to MongoDB successfully, using database: someDB
Starting watchdog…
DB Operation: Set slow query threshold to 100ms
Initializing MCP server…
Registering MCP resources…
Total MCP resources: 12
Registering MCP prompts…
Total MCP prompts: 14
Registering MCP tools…
Total MCP tools: 42
Creating stdio transport…
Connecting MCP server transport…
MongoDB Lens server running....

When sending a basic "what can you do" prompt, the server logs show:

{
  "result": {
    "protocolVersion": "2024-11-05",
    "capabilities": {
      "resources": {},
      "prompts": {},
      "tools": {}
    },
    "serverInfo": {
      "name": "MongoDB Lens",
      "version": "9.1.4",
      "description": "MongoDB MCP server for natural language database interaction",
      "homepage": "https://github.com/furey/mongodb-lens",
      "license": "MIT",
      "vendor": {
        "name": "James Furey",
        "url": "https://about.me/jamesfurey"
      }
    },
    "instructions": "\nMongoDB-Lens: NL→MongoDB via MCP\n\nCAPS:\n- DB: list/create/switch/drop\n- COLL: create/rename/drop/validate\n- DOC: find/count/insert-doc/update-doc/delete\n- SCH: infer/validate/compare/analyze\n- IDX: create/analyze/optimize\n- AGG: pipeline/distinct\n- PERF: explain/analyze/monitor\n- UTIL: clear-cache/export/validate\n- ADV: text/geo/timeseries/bulk/txn/gridfs/sharding/export\n- CONN: connect-mongodb{uri|alias}/add-alias/list/connect-original\n\nPTRNS:\n- DB_NAV: databases→use-database→collections\n- QRY: find-docs/count-docs/distinct-values\n- MOD: insert-doc/update-doc/delete-doc/bulk-ops\n- SCH: collection-schema/analyze-schema/compare-schemas\n- OPT: explain-query/analyze-patterns/create-index\n- AGG: aggregate-data\n- MON: server-status/performance-metrics/watch-changes\n- CACHE: clear-cache{all|specific}\n- CONN: add-alias→connect-mongodb→db-ops→connect-original\n\nFLOWS:\n1. NAV: list-dbs→use-db→list-collections\n2. QRY: find-docs{filter,project,sort}\n3. MOD: insert-doc/update-doc\n4. SCH: analyze-schema→generate-validator\n5. PERF: explain-query→analyze-patterns→create-index\n6. AGG: aggregate-data{multi-stage}\n7. BULK: bulk-ops{batch}\n8. TXN: transaction{atomic}\n9. CONN: add-alias→connect-mongodb{uri|alias}→ops→connect-original\n10. FRESH: clear-cache→list-collections/find-docs\n\nSAFE: destructive ops require confirmation tokens\n\nDOCS: github.com/furey/mongodb-lens/blob/main/README.md\n"
  },
  "jsonrpc": "2.0",
  "id": 1
}

However, the client returns this error:

2025-04-30T15:20:14.367542Z ERROR goose::agents::agent: Error: Request failed: Unknown error (status 400 Bad Request)
  at crates/goose/src/agents/agent.rs:530

Observations

1. The server appears to be running correctly and responding to requests
2. The capabilities section in the response is empty ("capabilities":{"resources":{},"prompts":{},"tools":{}}) despite the server registering numerous resources, prompts, and tools
3. The inspector tool works correctly with the same server

Question

Could this be due to an unsupported response type or protocol version mismatch?

Any suggestions on how to resolve this integration issue would be greatly appreciated.