uv pip install 
   # Example:
   uv pip install autogen-ext mcp[cli]

uv pip install  # Installs all dependencies from pyproject.toml

uv run src/mcp_server.py
   uv run src/mcp_client.py

uv sync --upgrade

uv pip install -r requirements.txt
  # or
  uv add --requirements requirements.txt

python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt

uv pip install -r requirements.txt

python src/mcp_server.py
  # or, explicitly:
  python src/mcp_server.py --transport sse
  # or, using uv:
  uv run src/mcp_server.py

python src/mcp_server.py --transport stdio
  # or, using uv:
  uv run src/mcp_server.py --transport stdio

python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt

uv pip install -r requirements.txt

cd src
python -m mcp_client

cd src
uv run mcp_client.py

{
      "mcpServers": {
        "test-dh-mcp": {
          "command": "/Users/chip/dev/test-dh-mcp/.venv/bin/python3",
          "args": ["/Users/chip/dev/test-dh-mcp/src/mcp_server.py", "--transport", "stdio"],
          "env": {
            "DH_MCP_CONFIG_FILE": "/Users/chip/dev/test-dh-mcp/deephaven_workers.json"
          }
        }
      }
    }

{
      "mcpServers": {
        "test-dh-mcp": {
          "command": "uv",
          "args": [
            "--directory",
            "/Users/chip/dev/test-dh-mcp/src",
            "run",
            "mcp_server.py",
            "--transport",
            "stdio"
          ],
          "env": {
            "DH_MCP_CONFIG_FILE": "/Users/chip/dev/test-dh-mcp/deephaven_workers.json"
          }
        }
      }
    }

> **Note:** All `DH_MCP_*` environment variables listed in the Deephaven Session Configuration section can be set here. These control the Deephaven session for every tool call.
    
4. Restart Claude Desktop.
5. Debugging logs can be found in `~/Library/Logs/Claude/`

## Deephaven Worker Configuration

All Deephaven worker configuration is now handled via a JSON file. The path to this file must be specified using the `DH_MCP_CONFIG_FILE` environment variable. There is no default path—this variable is required.

The config file should look like this:

- The `workers` object maps worker names to their connection settings.
- The `default_worker` is optional and used if a worker name is not specified in a tool call. If set, it must match one of the keys in the `workers` dictionary.

> **Important:** The `DH_MCP_CONFIG_FILE` environment variable must always be set to the path of your worker config file. There is no default config path.

**Supported fields for each worker:**

| Field               | Type           | Description                                                                 |
|---------------------|----------------|-----------------------------------------------------------------------------|
| `host`              | `str`          | Deephaven server hostname or IP (optional)                                  |
| `port`              | `int`          | Deephaven server port (optional)                                            |
| `auth_type`         | `str`          | Authentication type (e.g., `Anonymous`, `Bearer`) (optional)                |
| `auth_token`        | `str`          | Authentication token (optional)                                             |
| `never_timeout`     | `bool`         | Whether the session should never timeout (optional, default: True)          |
| `session_type`      | `str`          | Session type, e.g., `python` (optional, default: 'python')                  |
| `use_tls`           | `bool`         | Whether to use TLS/SSL (optional, default: False)                           |
| `tls_root_certs`    | `str` or `null`| Path to TLS root certificates (optional)                                    |
| `client_cert_chain` | `str` or `null`| Path to client certificate chain (optional)                                 |
| `client_private_key`| `str` or `null`| Path to client private key (optional)                                       |

> Note: You may define workers with only a subset of these fields, depending on your use case and authentication method. No fields are strictly required; defaults will be used where possible.

### Tool Usage

- `echo_tool(message: str) -> str`: Echoes back the input message, prefixed with 'Echo:'.
- `gnome_count_colorado() -> int`: Returns the current number of gnomes in Colorado (demo tool).
- `deephaven_worker_names() -> list[str]`: Returns all configured Deephaven worker names from the config file.
- `deephaven_default_worker() -> str`: Returns the name of the default worker as set in config (or None if not set).
- `deephaven_list_tables(worker_name: str = None) -> list`: Lists table names for the specified worker. If `worker_name` is not provided, uses the default_worker from config.
- `deephaven_table_schemas(worker_name: str = None) -> list`: Returns schemas for all tables in the specified worker. If `worker_name` is not provided, uses the default_worker from config.

See the example config file above for how to set up multiple workers.

## Registering Tools

Define new tools in `dhmcp/__init__.py` using the `@mcp_server.tool()` decorator. Example:

## Troubleshooting

- Ensure you are running commands from the correct directory (`src` for direct script execution).
- If you change tool definitions, restart the server.
- For connection issues, check that the server is running and listening on the expected address/port (for SSE), or correctly attached via stdio (for Claude/Inspector).

### Is the server running?

- **SSE mode:**

- **Stdio mode:**
  - Check your Claude/Inspector logs for successful connection and tool listing.

### MCP Inspector

The MCP Inspector is a tool that allows you to inspect the state of an MCP server.

1. Install the MCP Inspector:

2. Run the MCP Inspector:

> **⚠️ WARNING:**
> When using the MCP Inspector, all string values must be entered with quotes (e.g., "worker1").
> If you do not use quotes, the Inspector may send `null` or invalid values to the server.
> The value can be validated by clicking on the `Format JSON` button.

    - ** SSE mode: **

        - Using `venv`:

- Using `uv`:

- ** Stdio mode: **

        - Using `venv`:

- Using `uv`:

// Code block