Feature Request: Allow starting MCP server standalone (without VSCode dependency)

[mickaelxd]

Currently the MCP server can only be started from within VSCode. This forces a workflow where VSCode must be opened just to launch the dbcode, even if the coding session itself is outside VSCode.

Use case:

• I use another coding tool that supports mcp and prefer to run everything from the CLI.
• At the moment, I open VSCode solely to start the MCP server, then minimize it.
• This adds unnecessary overhead and context switching.

Proposed feature:

• Provide a way to run the MCP server as a standalone process, outside of VSCode.
• Possibly add a lightweight wrapper or CLI entrypoint that replicates what VSCode surfaces (confirmation prompts, role enforcement, etc.), but independent of the editor.

Benefits:

• Enables workflows that don’t rely on VSCode.
• Reduces friction for CLI-driven development.
• Aligns with the growing use of dbcode in non-VSCode environments.

Notes from discussion:

• Right now, the server is too embedded in VSCode to run standalone.
• A wrapper may be needed to handle prompts and role checks.

[mikeburgh]

So I looked into this, not feasible at this stage.. the biggest issue is when credentials for the connections are stored in VSCode secrets (recommended and default option).. I don't have a way to get them without VSCode.

So going to put this on the backlog, and might be a path to it when I update some of the auth functionality options.. but it's going to be low priority as current option works, and there are lot of things to get sorted in front of it..