Trouble connecting to Docker MCP toolkit

What version of the VS Code extension are you using?

0.4.9

Which IDE are you using?

vs code

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What steps can reproduce the bug?

I have the docker MCP toolkit setup with a few different tools. I'm struggling to get the codex extension to access them using plain english, even if requesting it use the MCP tool.

I've added this to the config.toml:

[mcp_servers.MCP_DOCKER]
command = "docker"
args = ["mcp", "gateway", "run"]
type = "stdio"

i've also added the server to my mcp.json under %APPDATA%/Code/User/mcp.json
as well as ~/<user>/.config/mcp/mcp.json in my WSL2 instance.

I've successfully given co-pilot access to my tools by adding the docker server to my mcp.json.

Apologies if this is not yet implemented!

What is the expected behavior?

Expect to be able to call tools connected to the docker mcp server using plain english.

eg. "Create a note in the obsidian app using the mcp tool with the title Codex"

What do you see instead?

Exact response from the above prompt:

Use the Docker MCP Toolkit’s obsidian_append_content tool to create the note. Call it once with the desired filename and a heading: ``powershell docker mcp tools call obsidian_append_content --input-json '{"filepath":"codex.md","content":"# Codex\n"}' `` That request writes or creates codex.md in your vault root with the heading “Codex,” matching the tool’s required filepath and content fields and letting the append tool auto-create missing notes (docker mcp tools list — Docker MCP Toolkit CLI, Accessed 2025-07-08; docker mcp tools inspect obsidian_append_content --format json — Docker MCP Toolkit CLI, Accessed 2025-07-08). Next steps: Run the command above. Refresh Obsidian to confirm codex.md exists and opens with the expected title. Let me know if you want the note stored in a subfolder or pre-populated with template text; I can adjust the JSON payload accordingly.

Additional information

_No response_