torbjorn/my-pal-mcp-server
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
3db49413ff29cf30b311715076bfad2c242f0fec
my-pal-mcp-server/docs/tools/version.md
Beehive Innovations 4151c3c3a5 Migration from Docker to Standalone Python Server (#73) 
* Migration from docker to standalone server
Migration handling
Fixed tests
Use simpler in-memory storage
Support for concurrent logging to disk
Simplified direct connections to localhost

* Migration from docker / redis to standalone script
Updated tests
Updated run script
Fixed requirements
Use dotenv
Ask if user would like to install MCP in Claude Desktop once
Updated docs

* More cleanup and references to docker removed

* Cleanup

* Comments

* Fixed tests

* Fix GitHub Actions workflow for standalone Python architecture

- Install requirements-dev.txt for pytest and testing dependencies
- Remove Docker setup from simulation tests (now standalone)
- Simplify linting job to use requirements-dev.txt
- Update simulation tests to run directly without Docker

Fixes unit test failures in CI due to missing pytest dependency.

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

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

* Remove simulation tests from GitHub Actions

- Removed simulation-tests job that makes real API calls
- Keep only unit tests (mocked, no API costs) and linting
- Simulation tests should be run manually with real API keys
- Reduces CI costs and complexity

GitHub Actions now only runs:
- Unit tests (569 tests, all mocked)
- Code quality checks (ruff, black)

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

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

* Fixed tests

* Fixed tests

---------

Co-authored-by: Claude <noreply@anthropic.com>
2025-06-18 23:41:22 +04:00

3.9 KiB
Raw Blame History

Version Tool - Server Information

Get server version, configuration details, and list of available tools

The version tool provides information about the Zen MCP Server version, configuration details, and system capabilities. This is useful for debugging, understanding server capabilities, and verifying your installation.

Usage

"Get zen to show its version"

Key Features

  • Server version information: Current version and build details
  • Configuration overview: Active settings and capabilities
  • Tool inventory: Complete list of available tools and their status
  • System health: Basic server status and connectivity verification
  • Debug information: Helpful details for troubleshooting

Output Information

The tool provides:

Version Details:

  • Server version number
  • Build timestamp and commit information
  • MCP protocol version compatibility
  • Python runtime version

Configuration Summary:

  • Active providers and their status
  • Default model configuration
  • Feature flags and settings
  • Environment configuration overview

Tool Availability:

  • Complete list of available tools
  • Tool version information
  • Capability status for each tool

System Information:

  • Server uptime and status
  • Memory and resource usage (if available)
  • Conversation memory status
  • Server process information

Example Output

🔧 Zen MCP Server Information

📋 Version: 2.15.0
🏗️ Build: 2024-01-15T10:30:00Z (commit: abc123f)
🔌 MCP Protocol: 1.0.0
🐍 Python Runtime: 3.11.7

⚙️ Configuration:
• Default Model: auto
• Providers: Google ✅, OpenAI ✅, Custom ✅
• Conversation Memory: Active ✅
• Web Search: Enabled

🛠️ Available Tools (12):
• chat - General development chat & collaborative thinking
• thinkdeep - Extended reasoning partner  
• consensus - Multi-model perspective gathering
• codereview - Professional code review
• precommit - Pre-commit validation
• debug - Expert debugging assistant
• analyze - Smart file analysis
• refactor - Intelligent code refactoring
• tracer - Static code analysis prompt generator
• testgen - Comprehensive test generation
• listmodels - List available models
• version - Server information

🔍 System Status:
• Server Uptime: 2h 35m
• Memory Storage: Active
• Server Process: Running

When to Use Version Tool

  • Troubleshooting: When experiencing issues with the server or tools
  • Configuration verification: To confirm your setup is correct
  • Support requests: To provide system information when asking for help
  • Update checking: To verify you're running the latest version
  • Capability discovery: To understand what features are available

Debug Information

The version tool can help diagnose common issues:

Connection Problems:

  • Verify server is running and responsive
  • Check MCP protocol compatibility
  • Confirm tool availability

Configuration Issues:

  • Validate provider setup
  • Check API key configuration status
  • Verify feature enablement

Performance Troubleshooting:

  • Server uptime and stability
  • Resource usage patterns
  • Memory storage health

Tool Parameters

This tool requires no parameters - it provides comprehensive server information automatically.

Best Practices

  • Include in bug reports: Always include version output when reporting issues
  • Check after updates: Verify version information after server updates
  • Monitor system health: Use periodically to check server status
  • Validate configuration: Confirm settings match your expectations

When to Use Version vs Other Tools

  • Use version for: Server diagnostics, configuration verification, troubleshooting
  • Use listmodels for: Model availability and capability information
  • Use other tools for: Actual development and analysis tasks
  • Use with support: Essential information for getting help with issues