Potential update.
Created a new profile for Obsidian using the MCP Toolkit for Mac OS. The plugin when adding a client, in my case codex, updated the .codex/config.toml by default. The entry in the config was labeled [mcp_servers.MCP_DOCKER] very generic and codex had to take a couple of rounds to find it, as it does not identify as Obsidian. I had to direct the Agent to use [mcp_servers.MCP_DOCKER] in order for it to connect.
By the agents suggestion... if there was more context with the name it would have been able to associate the connection with this particular MCP. I changed the name but on restarted it failed to connect and Docker Desktop reported the client was not connected. Deleted the entry and rejoined with a codex client and everything worked again but the name reverted back to the original [mcp_servers.MCP_DOCKER].
As a suggested update more context should be added to the label if it's going to automatically update config files for various agents. In my case I added the profile name; [mcp_servers.MCP_DOCKER_OBSIDIAN]. As I have not tested any other MCP but I suspect the naming convention is the same, which would only add to the confusion.
Thanks,
Potential update.
Created a new profile for Obsidian using the MCP Toolkit for Mac OS. The plugin when adding a client, in my case codex, updated the
.codex/config.tomlby default. The entry in the config was labeled[mcp_servers.MCP_DOCKER]very generic and codex had to take a couple of rounds to find it, as it does not identify as Obsidian. I had to direct the Agent to use[mcp_servers.MCP_DOCKER]in order for it to connect.By the agents suggestion... if there was more context with the name it would have been able to associate the connection with this particular MCP. I changed the name but on restarted it failed to connect and Docker Desktop reported the client was not connected. Deleted the entry and rejoined with a codex client and everything worked again but the name reverted back to the original
[mcp_servers.MCP_DOCKER].As a suggested update more context should be added to the label if it's going to automatically update config files for various agents. In my case I added the profile name;
[mcp_servers.MCP_DOCKER_OBSIDIAN]. As I have not tested any other MCP but I suspect the naming convention is the same, which would only add to the confusion.Thanks,