fix: rebranding, see [docs/name-change.md](docs/name-change.md) for details

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: guidedways

.dockerignore

@@ -11,7 +11,7 @@ __pycache__/
 env/
 venv/
 .venv/
-.zen_venv/
+.pal_venv/
 ENV/
 env.bak/
 venv.bak/

.env.example

@@ -1,4 +1,4 @@
-# Zen MCP Server Environment Configuration
+# PAL MCP Server Environment Configuration
 # Copy this file to .env and fill in your values
 
 # API Keys - At least one is required
@@ -191,7 +191,7 @@ DISABLED_TOOLS=analyze,refactor,testgen,secaudit,docgen,tracer
 # LOCALE=fr-FR
 
 # ===========================================
-# Zen MCP Server Configuration  
+# PAL MCP Server Configuration
 # ===========================================
 
 # Force .env file values to override system environment variables
@@ -213,15 +213,15 @@ DISABLED_TOOLS=analyze,refactor,testgen,secaudit,docgen,tracer
 #   Development with multiple AI tools: true (prevents tool conflicts)
 #   Production/Container deployments: false (preserves security practices)
 #   CI/CD environments: false (respects pipeline secrets)
-ZEN_MCP_FORCE_ENV_OVERRIDE=false
+PAL_MCP_FORCE_ENV_OVERRIDE=false
 
 # ===========================================
 # Docker Configuration
 # ===========================================
 
 # Container name for Docker Compose
 # Used when running with docker-compose.yml
-COMPOSE_PROJECT_NAME=zen-mcp
+COMPOSE_PROJECT_NAME=pal-mcp
 
 # Timezone for Docker containers
 # Ensures consistent time handling in containerized environments

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -12,7 +12,7 @@ body:
     attributes:
       label: Project Version
       description: "Which version are you using? (To see version: ./run-server.sh -v)"
-      placeholder: "e.g., 5.1.0"
+      placeholder: "e.g., 9.4.1"
     validations:
       required: true
 
@@ -29,7 +29,7 @@ body:
     id: logs
     attributes:
       label: Relevant Log Output
-      description: "Please copy and paste any relevant log output. Logs are stored under the `logs` folder in the zen folder. You an also use `./run-server.sh -f` to see logs"
+      description: "Please copy and paste any relevant log output. Logs are stored under the `logs` folder in the pal folder. You an also use `./run-server.sh -f` to see logs"
       render: shell
 
   - type: dropdown

.github/ISSUE_TEMPLATE/config.yml

@@ -1,12 +1,12 @@
 blank_issues_enabled: false
 contact_links:
   - name: 💬 General Discussion
-    url: https://github.com/BeehiveInnovations/zen-mcp-server/discussions
+    url: https://github.com/BeehiveInnovations/pal-mcp-server/discussions
     about: Ask questions, share ideas, or discuss usage patterns with the community
   - name: 📚 Documentation
-    url: https://github.com/BeehiveInnovations/zen-mcp-server/blob/main/README.md
+    url: https://github.com/BeehiveInnovations/pal-mcp-server/blob/main/README.md
     about: Check the README for setup instructions and usage examples
   - name: 🤝 Contributing Guide
-    url: https://github.com/BeehiveInnovations/zen-mcp-server/blob/main/CONTRIBUTING.md
+    url: https://github.com/BeehiveInnovations/pal-mcp-server/blob/main/CONTRIBUTING.md
     about: Learn how to contribute to the project
 

.github/ISSUE_TEMPLATE/tool_addition.yml

@@ -1,5 +1,5 @@
 name: 🛠️ New Gemini Tool Proposal
-description: Propose a new Zen MCP tool (e.g., `summarize`, `fixer`, `refactor`)
+description: Propose a new PAL MCP tool (e.g., `summarize`, `fixer`, `refactor`)
 labels: ["enhancement", "new-tool"]
 body:
   - type: input
@@ -15,7 +15,7 @@ body:
     id: purpose
     attributes:
       label: What is the primary purpose of this tool?
-      description: "Explain the tool's core function and the value it provides to developers using Claude + Zen."
+      description: "Explain the tool's core function and the value it provides to developers using Claude + PAL."
       placeholder: "This tool will automatically generate comprehensive documentation from code, extracting class and function signatures, docstrings, and creating usage examples."
     validations:
       required: true
@@ -27,7 +27,7 @@ body:
       description: "Show how a user would invoke this tool through Claude and what the expected output would look like."
       placeholder: |
         **User prompt to Claude:**
-        "Use zen to generate documentation for my entire src/ directory"
+        "Use pal to generate documentation for my entire src/ directory"
 
         **Expected behavior:**
         - Analyze all Python files in src/
@@ -61,7 +61,7 @@ body:
     id: system-prompt
     attributes:
       label: Proposed System Prompt (Optional)
-      description: "If you have ideas for how zen should be prompted for this tool, share them here."
+      description: "If you have ideas for how pal should be prompted for this tool, share them here."
       placeholder: |
         You are an expert technical documentation generator. Your task is to create comprehensive, user-friendly documentation from source code...
 

.github/workflows/docker-pr.yml

@@ -95,7 +95,7 @@ jobs:
             ```json
             {
               "mcpServers": {
-                "zen": {
+                "pal": {
                   "command": "docker",
                   "args": ["run", "--rm", "-i", "-e", "GEMINI_API_KEY", "ghcr.io/${{ github.repository }}:pr-${{ github.event.number }}"],
                   "env": { "GEMINI_API_KEY": "your-key" }

.github/workflows/docker-release.yml

@@ -87,7 +87,7 @@ jobs:
           \`\`\`json
           {
             "mcpServers": {
-              "zen-mcp-server": {
+              "pal-mcp-server": {
                 "command": "docker",
                 "args": [
                   "run", "--rm", "-i",

.gitignore

@@ -179,7 +179,7 @@ CLAUDE.local.md
 .claude/settings.local.json
 
 # Standalone mode files
-.zen_venv/
+.pal_venv/
 .docker_cleaned
 logs/
 *.backup

.pre-commit-config.yaml

@@ -28,7 +28,7 @@ exclude: |
     \.git/|
     \.venv/|
     venv/|
-    \.zen_venv/|
+    \.pal_venv/|
     __pycache__/|
     \.pytest_cache/|
     logs/|

AGENTS.md

@@ -5,29 +5,29 @@ See `requirements.txt` and `requirements-dev.txt`
 Also read CLAUDE.md and CLAUDE.local.md if available.
 
 ## Project Structure & Module Organization
-Zen MCP Server centers on `server.py`, which exposes MCP entrypoints and coordinates multi-model workflows. 
+PAL MCP Server centers on `server.py`, which exposes MCP entrypoints and coordinates multi-model workflows. 
 Feature-specific tools live in `tools/`, provider integrations in `providers/`, and shared helpers in `utils/`. 
 Prompt and system context assets stay in `systemprompts/`, while configuration templates and automation scripts live under `conf/`, `scripts/`, and `docker/`. 
 Unit tests sit in `tests/`; simulator-driven scenarios and log utilities are in `simulator_tests/` with the `communication_simulator_test.py` harness. 
 Authoritative documentation and samples live in `docs/`, and runtime diagnostics are rotated in `logs/`.
 
 ## Build, Test, and Development Commands
-- `source .zen_venv/bin/activate` – activate the managed Python environment.
+- `source .pal_venv/bin/activate` – activate the managed Python environment.
 - `./run-server.sh` – install dependencies, refresh `.env`, and launch the MCP server locally.
 - `./code_quality_checks.sh` – run Ruff autofix, Black, isort, and the default pytest suite.
 - `python communication_simulator_test.py --quick` – smoke-test orchestration across tools and providers.
 - `./run_integration_tests.sh [--with-simulator]` – exercise provider-dependent flows against remote or Ollama models.
 
 Run code quality checks:
 ```bash
-.zen_venv/bin/activate && ./code_quality_checks.sh
+.pal_venv/bin/activate && ./code_quality_checks.sh
 ```
 
 For example, this is how we run an individual / all tests:
 
 ```bash
-.zen_venv/bin/activate && pytest tests/test_auto_mode_model_listing.py -q
-.zen_venv/bin/activate && pytest -q
+.pal_venv/bin/activate && pytest tests/test_auto_mode_model_listing.py -q
+.pal_venv/bin/activate && pytest -q
 ```
 
 ## Coding Style & Naming Conventions