Implement tsh mcp db config

[gabrielcorado]

This command generates the MCP client configuration for MCP database access. For now, only Claude Desktop is supported.

This command follows the same flags and usage flow as tsh mcp config command with some differences:

• Running the command multiple times updates the config. So if you executed tsh mcp db config db1 and then tsh mcp db config db2, the second database will be added to the configuration file.
• Running the command for a database already on the config will cause its configuration to be updated.

Usage examples

Print JSON format with hint:

❯ tsh mcp db config --db-user=postgres --db-name=postgres pg-dev
Here is a sample JSON configuration for launching Teleport MCP servers:
{
  "mcpServers": {
    "teleport-databases": {
      "command": "/path/to/tsh",
      "args": [
        "mcp",
        "db",
        "start",
        "teleport://clusters/root.teleport.dev/databases/pg-dev?dbName=postgres&dbUser=postgres"
      ]
    }
  }
}

Tip: use --client-config=claude to update your Claude Desktop configuration.
You can also specify a custom config path with --client-config=<path> to update
a config file compatible with the "mcpServer" mapping.

Update Claude Desktop config:

❯ tsh mcp db config --db-user=postgres --db-name=postgres pg-dev --client-config=claude
Updated database "pg-dev" on the client configuration at:
/Users/gabrielcorado/Library/Application Support/Claude/claude_desktop_config.json

Teleport database access MCP server is named "teleport-databases" in this configuration.

You may need to restart your client to reload these new configurations.

Update Claude Desktop config with environment variables "conflict":

❯ tsh mcp db config --db-user=postgres --db-name=postgres pg-dev --client-config=claude
Updated database "pg-dev" on the client configuration at:
/Users/gabrielcorado/Library/Application Support/Claude/claude_desktop_config.json

Teleport database access MCP server is named "teleport-databases" in this configuration.

You may need to restart your client to reload these new configurations.

Environment variables have changed, but existing values will be preserved.
To overwrite them, rerun this command with the --overwrite flag.

[greedy52]

nit: instead of implementing the function twice (like with query and without query), maybe we could implement a function that returns a new ResourceURI without the query params like fullURI.WithoutQuery().String() == wantedURI. That way we can keep String simple, and no need to implement Equal.

[gabrielcorado]

I've updated the ResourceURI following your suggestion.

[greedy52]

i think we should just overwrite these with new values instead of using old values. if we want to be on the safe side, lets check if they have changed and prompt user for overwrite.

[gabrielcorado]

I assume this command is just making the smallest change possible to avoid disrupting any manual modifications the users might have made.

We could introduce another command to validate those entries or have a --fix argument so we don't set the expectation that this command will automatically fix any problem the config might have. What do you think?

[greedy52]

A new flag is also fine. Instead of --fix, how about --overwrite?

If not specified, but the content is different, print something like:

Environment variables have changed, but existing values will be preserved.
To overwrite them, rerun this command with the --overwrite flag.

[gabrielcorado]

Done, I've added the flag and the message.

[Tener]

Agreed with @greedy52 comments. Also, could you add more usage examples in the issue description? It would be worth to see all the different modes in action.

[gabrielcorado]

@Tener I've added more usage examples on the issue description. Let me know if you want me to show something else.

[juliaogris]

wow, I didn't know that. Seems surprising that this is the default.

[juliaogris]

nit:
Is it possible that there will be other parameters in the future, then maybe functional options is a better choice (and would only require one function name).

if it is unlikely that there will be other connect parameters, maybe it should be WithUser or so?

[gabrielcorado]

Yes, we can have at least one other parameter (database roles). Thanks for the suggestion. I've updated it to use a single function and provide the parameters as options.

[juliaogris]

sorry, I had this review pending from the very beginning - never clicked the button apparently, feel free to ignore.