PAL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level (e.g., INFO, DEBUG) | |
| OLLAMA_HOST | No | Ollama host URL (default localhost:11434) | |
| XAI_API_KEY | No | Your X.AI API key | |
| DIAL_API_KEY | No | Your DIAL API key | |
| DEFAULT_MODEL | No | Default model to use | |
| DISABLED_TOOLS | No | Comma-separated list of tools to disable | |
| GEMINI_API_KEY | No | Your Gemini API key | |
| OPENAI_API_KEY | No | Your OpenAI API key | |
| OPENROUTER_API_KEY | No | Your OpenRouter API key | |
| AZURE_OPENAI_API_KEY | No | Your Azure OpenAI API key | |
| AZURE_OPENAI_ENDPOINT | No | Your Azure OpenAI endpoint | |
| MAX_CONVERSATION_TURNS | No | Maximum conversation turns | |
| CONVERSATION_TIMEOUT_HOURS | No | Conversation timeout in hours | |
| DEFAULT_THINKING_MODE_THINKDEEP | No | Default thinking mode for thinkdeep tool |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chatA | General chat and collaborative thinking partner for brainstorming, development discussion, getting second opinions, and exploring ideas. Use for ideas, validations, questions, and thoughtful explanations. |
| clinkB | Link a request to an external AI CLI (Gemini CLI, Qwen CLI, etc.) through PAL MCP to reuse their capabilities inside existing workflows. |
| thinkdeepA | Performs multi-stage investigation and reasoning for complex problem analysis. Use for architecture decisions, complex bugs, performance challenges, and security analysis. Provides systematic hypothesis testing, evidence-based investigation, and expert validation. |
| plannerA | Breaks down complex tasks through interactive, sequential planning with revision and branching capabilities. Use for complex project planning, system design, migration strategies, and architectural decisions. Builds plans incrementally with deep reflection for complex scenarios. |
| consensusA | Builds multi-model consensus through systematic analysis and structured debate. Use for complex decisions, architectural choices, feature proposals, and technology evaluations. Consults multiple models with different stances to synthesize comprehensive recommendations. |
| codereviewB | Performs systematic, step-by-step code review with expert validation. Use for comprehensive analysis covering quality, security, performance, and architecture. Guides through structured investigation to ensure thoroughness. |
| precommitA | Validates git changes and repository state before committing with systematic analysis. Use for multi-repository validation, security review, change impact assessment, and completeness verification. Guides through structured investigation with expert analysis. |
| debugA | Performs systematic debugging and root cause analysis for any type of issue. Use for complex bugs, mysterious errors, performance issues, race conditions, memory leaks, and integration problems. Guides through structured investigation with hypothesis testing and expert analysis. |
| secauditA | Performs comprehensive security audit with systematic vulnerability assessment. Use for OWASP Top 10 analysis, compliance evaluation, threat modeling, and security architecture review. Guides through structured security investigation with expert validation. |
| docgenA | Generates comprehensive code documentation with systematic analysis of functions, classes, and complexity. Use for documentation generation, code analysis, complexity assessment, and API documentation. Analyzes code structure and patterns to create thorough documentation. |
| analyzeB | Performs comprehensive code analysis with systematic investigation and expert validation. Use for architecture, performance, maintainability, and pattern analysis. Guides through structured code review and strategic planning. |
| refactorA | Analyzes code for refactoring opportunities with systematic investigation. Use for code smell detection, decomposition planning, modernization, and maintainability improvements. Guides through structured analysis with expert validation. |
| tracerA | Performs systematic code tracing with modes for execution flow or dependency mapping. Use for method execution analysis, call chain tracing, dependency mapping, and architectural understanding. Supports precision mode (execution flow) and dependencies mode (structural relationships). |
| testgenB | Creates comprehensive test suites with edge case coverage for specific functions, classes, or modules. Analyzes code paths, identifies failure modes, and generates framework-specific tests. Be specific about scope - target particular components rather than testing everything. |
| challengeA | Prevents reflexive agreement by forcing critical thinking and reasoned analysis when a statement is challenged. Trigger automatically when a user critically questions, disagrees or appears to push back on earlier answers, and use it manually to sanity-check contentious claims. |
| apilookupA | Use this tool automatically when you need current API/SDK documentation, latest version info, breaking changes, deprecations, migration guides, or official release notes. This tool searches authoritative sources (official docs, GitHub, package registries) to ensure up-to-date accuracy. |
| listmodelsA | Shows which AI model providers are configured, available model names, their aliases and capabilities. |
| versionA | Get server version, configuration details, and list of available tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| chat | Chat and brainstorm ideas |
| clink | Forward a request to a configured AI CLI (e.g., Gemini) |
| thinkdeeper | Step-by-step deep thinking workflow with expert analysis |
| planner | Break down complex ideas, problems, or projects into multiple manageable steps |
| consensus | Step-by-step consensus workflow with multi-model analysis |
| review | Perform a comprehensive code review |
| precommit | Step-by-step pre-commit validation workflow |
| debug | Debug an issue or error |
| secaudit | Comprehensive security audit with OWASP Top 10 coverage |
| docgen | Generate comprehensive code documentation with complexity analysis |
| analyze | Analyze files and code structure |
| refactor | Refactor and improve code structure |
| tracer | Trace code execution paths |
| testgen | Generate comprehensive tests |
| challenge | Challenge a statement critically without automatic agreement |
| apilookup | Look up the latest API or SDK information |
| listmodels | List available AI models |
| version | Show server version and system information |
| continue | Continue the previous conversation using the chat tool |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Many tools have overlapping purposes, particularly among analyze, codereview, debug, thinkdeep, and tracer, which all involve systematic analysis of code. Although each targets a specific aspect (architecture, security, debugging), the boundaries are fuzzy, and agents may struggle to select the appropriate tool for a given task.
Tool names are uniformly lowercase concatenated words (e.g., apilookup, codereview, testgen). While some names are generic (chat, clink), there is a consistent pattern overall. However, the lack of a standard verb_noun prefix (like list_, create_) limits predictability.
With 18 tools, the server is at the upper end of a reasonable scope. All tools seem to serve a distinct purpose, though the overlap among analysis tools suggests some consolidation could be beneficial. The count is appropriate for a comprehensive development assistant.
The tool set covers a wide range of development tasks: analysis, review, debugging, security, documentation, testing, planning, and consensus. However, it lacks tools for executing code, searching code, or direct editing, which are common in such assistants. These gaps are minor given the existing coverage.