PDDL MCP Server
PDDL MCP Server is a planning backend that accepts natural-language tasks or explicit PDDL files, generates PDDL models, runs Fast Downward, and returns structured plans.
plan_from_text: Convert natural-language task descriptions into executable Fast Downward plans through semantic parsing, domain matching, PDDL generation, and validation.
generate_plan: Plan from a task dictionary or existing domain/problem PDDL paths.
validate_config: Check runtime configuration and report missing optional components like Fast Downward or LLM settings.
get_system_info: Return server capabilities, Python/platform info, project root, and output directory.
Generate artifacts for every run:
domain.pddl,problem.pddl,sas_plan, planner log, andresult.json.Support optional LLM semantic parsing with deterministic local fallback.
Return stable structured responses with workflow steps, warnings, explanations, and errors.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@PDDL MCP Server Create a plan for robot r2 to move from the warehouse to the office"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
PDDL MCP Server
PDDL MCP Server is a personal MCP backend project for turning natural-language planning requests or explicit PDDL files into executable Fast Downward plans.
It is designed as a clean single-version planning service: understand the task, match domain knowledge, generate PDDL, run a planner, validate the result, and return a structured MCP response with artifacts.
Project Context and Contribution
I designed and implemented this repository independently from start to finish, including the natural-language/PDDL workflow, Fast Downward integration and debugging, domain templates, stable tool responses, artifact handling, validation, modular src package structure, tests, CI, security guidance, release documentation, and demo assets.
My algorithm engineering internship at UniDT Co., Ltd. is relevant professional context for my interest in automated planning, but this repository is my independently developed personal project. It is not company code, does not require or imply company authorization, and does not contain employer credentials, private services, internal data, or an endorsement by UniDT Co., Ltd.
Related MCP server: bumi-mcp
Highlights
Natural language to PDDL workflow through
plan_from_text.Direct PDDL planning through
generate_planwithdomain_pathandproblem_path.Configurable LLM semantic parsing with deterministic local fallback.
Fast Downward integration for real planner execution.
Generated artifacts for every run:
domain.pddl,problem.pddl,sas_plan, planner log, andresult.json.Stable MCP tool response shape for downstream agents or clients.
Tests for config loading, semantic fallback, domain matching, PDDL generation, planning, validation, and MCP responses.
Demo
The project can solve the classic farmer, wolf, goat, and cabbage river-crossing puzzle.
The animation shows the end-to-end flow: natural-language input, semantic processing, template matching, PDDL generation, Fast Downward planning, and validated plan output.
Input:
A farmer must take a wolf, a goat, and a cabbage across a river.
The boat must be driven by the farmer and can carry at most one item.
If the farmer is absent, the wolf eats the goat and the goat eats the cabbage.
Plan how to move everything safely to the other side.Output plan:
(cross-with goat left right)
(cross-alone right left)
(cross-with cabbage left right)
(cross-with goat right left)
(cross-with wolf left right)
(cross-alone right left)
(cross-with goat left right)This is a valid 7-step solution: take the goat first, return alone, move the cabbage, bring the goat back, move the wolf, return alone, and take the goat across again.
Architecture
The code is intentionally split into focused modules:
Module | Responsibility |
| Load |
| Convert natural language into a semantic planning representation. |
| Match the task to a domain template. |
| Generate domain/problem PDDL. |
| Build and run the Fast Downward command. |
| Validate declared plan actions and result shape. |
| Orchestrate the full planning pipeline. |
| Expose MCP tools through FastMCP. |
Project Layout
pddl-mcp/
├── .github/CODEOWNERS
├── .dockerignore
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── Dockerfile
├── pyproject.toml
├── server.py
├── .mcp.json
├── docs/
│ ├── assets/
│ └── releases/
├── examples/
│ └── mcp_client_quickstart.py
├── src/pddl_mcp/
│ ├── config.py
│ ├── knowledge.py
│ ├── modeling.py
│ ├── planner.py
│ ├── semantic.py
│ ├── server.py
│ ├── validation.py
│ ├── workflow.py
│ └── resources/domain_templates.json
└── tests/Installation
git clone https://github.com/NBNBTM/pddl-mcp-server.git
cd pddl-mcp-server
python -m pip install -e ".[dev]"
cp .env.example .envConfiguration
Edit .env for your local runtime.
Minimal configuration:
OUTPUT_DIR=output
LOG_LEVEL=INFOReal Fast Downward planning:
FAST_DOWNWARD_PATH=/absolute/path/to/fast-downward.py
FAST_DOWNWARD_SEARCH=astar(blind())
MAX_PLANNING_TIME=300Optional LLM semantic parsing:
LLM_API_URL=https://your-llm-endpoint.example/v1/chat/completions
LLM_API_KEY=...
LLM_MODEL=qwen-max
LLM_TIMEOUT=120
LLM_RETRIES=2LLM_API_TOKEN is also supported as a backward-compatible alias when LLM_API_KEY is empty.
Do not commit real .env files or API keys. The repository only includes .env.example.
Fast Downward Setup
One local setup option:
mkdir -p .tools
git clone https://github.com/aibasel/downward.git .tools/downward
cd .tools/downward
python build.pyThen set:
FAST_DOWNWARD_PATH=/absolute/path/to/pddl-mcp-server/.tools/downward/fast-downward.py.tools/ is ignored by Git, so local planner builds are not uploaded.
Docker
Build the image from the repository root:
docker build -t pddl-mcp-server:4.0.1 .The image compiles a pinned Fast Downward revision and sets FAST_DOWNWARD_PATH automatically. It runs the MCP server over stdio and does not contain API credentials or a local .env file.
Run it interactively and keep generated artifacts in a named volume:
docker run --rm -i \
--mount type=volume,source=pddl-mcp-output,target=/app/output \
pddl-mcp-server:4.0.1Optional LLM settings must be passed at runtime, for example with --env LLM_API_URL, --env LLM_API_KEY, and --env LLM_MODEL. Never place real credentials in the Dockerfile or image build arguments.
Run The MCP Server
python server.pyThe root server.py is a compatibility entry point. The actual implementation lives in pddl_mcp.server.
Python Usage
from pddl_mcp.workflow import plan_from_text_response
result = plan_from_text_response(
"Move robot r1 from room1 to room3",
{"task_id": "robot-demo"},
)
print(result["success"])
print(result["plan_content"])River-crossing example:
from pddl_mcp.workflow import plan_from_text_response
text = """
A farmer must take a wolf, a goat, and a cabbage across a river.
The boat must be driven by the farmer and can carry at most one item.
If the farmer is absent, the wolf eats the goat and the goat eats the cabbage.
"""
result = plan_from_text_response(text, {"task_id": "farmer-river-demo"})
print(result["plan_content"])MCP Tools
plan_from_text
plan_from_text(text: str, options: dict | None = None)Runs the complete natural-language workflow:
text -> semantic parsing -> knowledge match -> PDDL generation -> planning -> validationgenerate_plan
generate_plan(task: dict)Supports two modes:
{
"description": "Move robot r1 from room1 to room3"
}or:
{
"domain_path": "/path/to/domain.pddl",
"problem_path": "/path/to/problem.pddl"
}validate_config
Checks whether Fast Downward and LLM settings are configured correctly.
get_system_info
Returns server capabilities, Python version, platform, project root, and output directory.
Response Shape
Every planning response follows the same structure:
{
"success": true,
"task_id": "farmer-river-demo",
"plan_content": "...",
"explanation": "...",
"artifacts": {
"domain_path": "...",
"problem_path": "...",
"plan_path": "...",
"log_path": "...",
"result_path": "..."
},
"workflow_steps": [
{
"name": "planning",
"success": true,
"duration_sec": 0.136,
"message": ""
}
],
"warnings": [],
"error": ""
}MCP Client Configuration
The repository includes .mcp.json:
{
"mcpServers": {
"pddl-planner": {
"command": "python",
"args": ["server.py"],
"cwd": "."
}
}
}For desktop MCP clients, use the absolute project path in cwd if relative paths are not supported by your client.
MCP Python client quickstart
After installing the project, run the included stdio client against the local server:
python examples/mcp_client_quickstart.pyPass a different natural-language request with --text. The client lists the available tools, calls get_system_info, then sends the request to plan_from_text and prints the complete structured response.
Testing
python -m compileall -q src tests examples server.py
python -m pytest -q -p no:cacheprovider
python -m ruff check . --no-cacheExpected local result:
19 passed
All checks passedIf FAST_DOWNWARD_PATH is not configured, real planner execution reports a clear configuration warning. Mock workflow tests still run.
Release Notes
The current release notes are available at:
The project documentation site is available at:
Security Notes
Do not commit
.env, API keys, model tokens, or private planner outputs.Keep local Fast Downward builds under
.tools/.Generated outputs belong under
output/.Both
.tools/andoutput/are ignored by Git.
License
Copyright (c) 2024 Lindsey Yang. This independently developed project is released by its copyright holder under the MIT License. See the copyright and source notice for the provenance boundary of the included planning-domain metadata.
Available Tools
4 toolsgenerate_planC
Plan from a task dictionary or existing domain/problem PDDL paths.
Inputs: task (required). Returns: object
get_system_infoA
Return server and runtime information.
Inputs: no named parameters. Returns: object
plan_from_textC
Plan from a natural-language task description.
Inputs: text (required), options. Returns: object
validate_configA
Validate runtime configuration and report missing optional components.
Inputs: no named parameters. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
MCP server for generating rough-draft project plans from natural-language prompts.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Related MCP Servers
- FlicenseCqualityCmaintenanceA Model Context Protocol server that enables natural language interactive control of Universal Robots collaborative robots, allowing users to control robot motion, monitor status, and execute programs through direct commands to large language models.398-
- AlicenseAqualityBmaintenanceMCP server for controlling the Noetix Bumi humanoid robot via ROS 2, with support for autonomous mission planning using LLMs and computer vision.28MIT
- AlicenseNot gradedqualityCmaintenanceEnables natural language command control of robots via ROS2, with a web portal for real-time visualization and interaction.1MIT
- AlicenseNot gradedqualityCmaintenanceTask planning and execution MCP server with durable SQLite storage and a browser UI for reviewing plans and following progress.1ISC