MCP Gee Sweet MCP Server

What the code does

We read the source, 23 h ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

RUN curl -LsSf https://astral.sh/uv/install.sh | sh

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mcp-gee-sweet -- uvx mcp-gee-sweet

{
  "mcpServers": {
    "mcp-gee-sweet": {
      "command": "uvx",
      "args": [
        "mcp-gee-sweet"
      ]
    }
  }
}

[mcp_servers.mcp-gee-sweet]
command = "uvx"
args = ["mcp-gee-sweet"]

{
  "mcpServers": {
    "mcp-gee-sweet": {
      "command": "uvx",
      "args": [
        "mcp-gee-sweet"
      ]
    }
  }
}

{
  "servers": {
    "mcp-gee-sweet": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-gee-sweet"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: AUTH_METHOD (Pin a single auth method with no fallback, instead of the default waterfall (OAuth, then service account, then Application Default Credentials)), CREDENTIALS_PATH (Path to an OAuth Client ID JSON file downloaded from GCP Console, used for the oauth auth method), TOKEN_PATH (Path where the OAuth token is cached after the first interactive authorization), SERVICE_ACCOUNT_PATH (Path to a Google service account JSON key file, used for the service_account auth method), CREDENTIALS_CONFIG (Base64-encoded service account JSON key, as an alternative to SERVICE_ACCOUNT_PATH for headless or container deployments), ENABLED_TOOLS (Comma-separated list of tool function names to register. Default: all tools enabled).