updates details for brave search

[jonathansampson]

I have verified that task build succeeds (with a small change for Windows).

The task catalog command also passes, however it does show an incorrect summary of tools, presumably until http://desktop.docker.com/mcp/catalog/v2/tools/brave.json is updated—it is unclear to me when/how this resource gets updated.

[mihaiplesa]

@ipedrazas could we get your review on this one please?

[hspencer77]

🔥

[ipedrazas]

Hey, thanks for this contribution. One small issue: if you try to build and run the tools by running this command:

task build -- --tools brave

You will see that the docker image is built correctly, but the tools cannot be listed (probably because it needs the correct configuration set).

We only push to Hub images that list tools. Is there any chance that you can make the listing tools not require a valid connection?

[jonathansampson]

Thank you, @ipedrazas. I will take a look at that change ASAP and follow up with a commit.

[jonathansampson]

@ipedrazas The fix appears to simple; just needed to change the env.BRAVE_MCP_TRANSPORT.example from http to stdio. When the server is stood up for tool enumeration, whatever is in the example field is used as the command-line value, which I was not expecting. I assumed whatever was provided as the example was provided only as a hint to the user 😀

mcp-registry/internal/mcp/client.go

Lines 189 to 198 in 00d9af2

	func toEnviron(env []servers.Env, secrets []servers.Secret) []string {
	var environ []string
	for _, env := range env {
	environ = append(environ, fmt.Sprintf("%s=%s", env.Name, env.Example))
	}
	for _, secret := range secrets {
	environ = append(environ, secret.Env+"="+secret.Example)
	}
	return environ
	}

[mihaiplesa]

Thank you @ipedrazas.

[mihaiplesa]

@ipedrazas how/when would https://hub.docker.com/r/mcp/brave-search and https://hub.docker.com/mcp/server/brave/overview get updated? And have archived removed.