PDDL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PDDL_DOMAIN_PATH | Yes | The path to the PDDL domain template file. | ./templates/domain.pddl |
| FAST_DOWNWARD_PATH | Yes | The path to the fast-downward.py script required for PDDL planning. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| plan_from_textC | Plan from a natural-language task description. |
| generate_planC | Plan from a task dictionary or existing domain/problem PDDL paths. |
| validate_configA | Validate runtime configuration and report missing optional components. |
| get_system_infoA | Return server and runtime information. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: generate_plan uses structured input, plan_from_text uses natural language, get_system_info provides runtime info, and validate_config checks configuration. No overlap.
Three tools follow a verb_noun pattern (generate_plan, get_system_info, validate_config), but plan_from_text breaks the pattern by starting with a noun, making it less predictable.
With 4 tools, the server is slightly underpopulated but still reasonable for a specialized domain like PDDL planning. Each tool serves a clear role.
The tool set covers core planning generation and system info but lacks features like PDDL validation or plan debugging, which are notable gaps for a planning server.