MCP server for reading OmniPlan (.oplx) and Microsoft Project (.mpp) schedule files
Project description
OmniPlan MCP Server
A Model Context Protocol (MCP) server that lets Claude read and analyze project schedule files — OmniPlan (.oplx) and Microsoft Project (.mpp) formats.
Ask Claude questions like:
- "What's the current project schedule?"
- "List all milestones and their dates"
- "Show me tasks related to the robotic arm"
- "What's the overall progress percentage?"
Features
| Feature | Description |
|---|---|
| 📂 Read .mpp | Parse Microsoft Project files via OmniPlan bridge |
| 📂 Read .oplx | Direct XML parsing (no OmniPlan needed) |
| 🏛️ Full hierarchy | Groups, tasks, milestones with dates and progress |
| 🔍 Search | Find tasks by keyword across the entire schedule |
| 👤 Resources | List all human resources and assignments |
| 📊 Summary | Phase overview, progress statistics, timeline |
| 🔒 Safe concurrency | Direct AppleScript reading avoids temp-file conflicts when multiple sessions run |
Prerequisites
| Requirement | Notes |
|---|---|
| macOS | Required (for AppleScript/OmniPlan bridge) |
| Python 3.10+ | For running the MCP server |
| OmniPlan | Only needed for .mpp files; .oplx works without it |
Install OmniPlan (optional — only for .mpp files)
brew install --cask omniplan
First run: macOS may prompt for Accessibility/Automation permissions when OmniPlan is called via AppleScript. Grant them in System Settings → Privacy & Security → Automation.
Quick Start
1. Install
# Option A: One-line installer (recommended)
curl -fsSL https://raw.githubusercontent.com/cygnusyang/omniplan-mcp/main/install.sh | bash
# Option B: Manual clone
git clone https://github.com/cygnusyang/omniplan-mcp.git
cd omniplan-mcp
pip install -e .
2. Configure Claude Code
Add to your ~/.claude/settings.json:
uv run (recommended)
{
"mcpServers": {
"omniplan": {
"command": "uv",
"args": [
"run",
"--directory", "/Users/yourusername/.local/share/omniplan-mcp",
"omniplan-mcp"
],
"env": {}
}
}
}
pip install (after PyPI publish)
{
"mcpServers": {
"omniplan": {
"command": "uvx",
"args": ["omniplan-mcp"],
"env": {}
}
}
}
Direct Python
{
"mcpServers": {
"omniplan": {
"command": "/path/to/python3",
"args": ["-m", "omniplan_mcp"],
"env": {
"PYTHONPATH": "/path/to/omniplan-mcp/src"
}
}
}
}
3. Restart Claude Code
The MCP server will start automatically. You can now ask Claude about your project files!
Usage Examples
Read a project schedule
你:帮我读取 PLB1011 项目计划,看看有哪些阶段
Claude:调用 read_schedule → 显示完整任务树
List milestones
你:列出所有里程碑节点
Claude:调用 list_milestones → 显示所有 ◇ 里程碑
Search for tasks
你:搜索所有关于"机械臂"的任务
Claude:调用 search_tasks → 显示匹配的任务列表
Project summary
你:这个项目的整体进度怎么样?
Claude:调用 schedule_summary → 显示阶段概览和进度统计
Tools Reference
| Tool | Description | Parameters |
|---|---|---|
read_schedule |
Full task hierarchy with dates and progress | filepath (required), format: tree/flat/json |
list_milestones |
All milestone tasks | filepath |
list_resources |
All human resources | filepath, detail: simple/full |
search_tasks |
Search tasks by keyword | filepath, keyword |
schedule_summary |
Phase overview and progress stats | filepath |
get_task_detail |
Detailed info about a specific task | filepath, task_id or task_name |
get_resource_detail |
Detailed info about a specific resource | filepath, resource_name |
list_violations |
All scheduling conflicts/violations | filepath |
list_assignments |
All resource-to-task assignments | filepath |
list_dependencies |
All task dependency relationships | filepath |
get_schedule_settings |
Scheduling granularity & working hours | (reads active OmniPlan document) |
evaluate_omniplan_script |
Run Omni Automation JS in OmniPlan | script (JavaScript code) |
export_schedule |
Export schedule to various formats | filepath, format (optional), output_path (optional) |
lookup_task |
Find task by name, get its numeric ID | search_name |
set_task_completed |
Set task to 100% complete | task_id, include_subtree |
set_task_completed_by_name |
Set task to 100% complete by name | task_name, include_subtree |
add_dependency |
Add finish-to-start dependency | dependent_task_id, prerequisite_task_id |
remove_dependency |
Remove a dependency | dependent_task_id, prerequisite_task_id |
set_task_duration |
Change task duration | task_id, duration_seconds |
clear_constraint_date |
Remove locked start date | task_id |
rename_task |
Rename a task | task_id, new_name |
delete_task |
Delete a task and its children | task_id |
add_task |
Add a new task under a parent | parent_task_id, task_name, duration_seconds (optional) |
save_document |
Save the OmniPlan document | (none) |
New in v0.4.0
- 12 new write-operation tools — Now you can modify schedules directly from Claude:
lookup_task— Find any task by name to get its numeric IDset_task_completed/set_task_completed_by_name— Mark tasks as 100% completeadd_dependency/remove_dependency— Manage task dependencies (prerequisites)set_task_duration— Adjust task durationsclear_constraint_date— Remove locked/constraint datesrename_task/delete_task/add_task— Structure editingsave_document— Persist changes to disk
- Bug fixes: .oplx parsing now prefers Actual.xml (fixes stale backup reads), outline_depth computed from hierarchy, percent-complete derived from effort-done/effort ratio, task_status computed for .oplx tasks, evaluate_javascript quotes properly escaped
- Parser robustness: build_task_tree handles both string and integer parent_ids
How It Works
.mpp file ──→ OmniPlan (AppleScript direct read) ──→ pipe-delimited records ──→ Claude
↑
.oplx file ───────────────┴─── direct XML parsing ──────┘
For .oplx files
Direct XML parsing — fast, no external dependencies.
For .mpp files
- MCP server opens the
.mppfile in OmniPlan via the macOSopencommand - Reads all project data (tasks, resources, dates, progress) directly from OmniPlan's in-memory object model via AppleScript
- Parses the pipe-delimited output into structured records
- Closes the document
No temporary files are created — data is read directly from OmniPlan's in-memory model.
Project Structure
omniplan-mcp/
├── install.sh # One-click installer
├── pyproject.toml # Package metadata (PyPI-ready)
├── README.md # This file
├── LICENSE # MIT license
├── .gitignore
├── src/
│ └── omniplan_mcp/
│ ├── __init__.py # Package version
│ ├── __main__.py # CLI entry point
│ ├── server.py # MCP server (tools & handlers)
│ └── parser.py # .mpp (AppleScript) / .oplx (XML) parsing
└── tests/
└── test_parser.py # Unit tests
Development
# Clone
git clone https://github.com/cygnusyang/omniplan-mcp.git
cd omniplan-mcp
# Install in editable mode
pip install -e .
# Run tests
python -m pytest tests/
# Run the server directly (stdio)
python -m omniplan_mcp
Publishing to PyPI
Published automatically via GitHub Actions (Trusted Publisher) when a tag is pushed:
git tag v0.1.0
git push origin v0.1.0
Manual build (for testing):
pip install build
python -m build
Requirements
- Python 3.10+
- macOS (for OmniPlan AppleScript bridge)
- OmniPlan (only for
.mppfiles; optional for.oplx)
Limitations
.mppparsing requires OmniPlan to be installed- Only supports macOS (AppleScript dependency)
- Does not modify
.mppfiles — read-only
License
MIT License — see LICENSE for details.
Related
Project details
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file omniplan_mcp-0.4.0.tar.gz.
File metadata
- Download URL: omniplan_mcp-0.4.0.tar.gz
- Upload date:
- Size: 29.0 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
3c0740318a4cc1e0662de989db3770157373a5251fcc33fc661990d358bee8cf
|
|
| MD5 |
80fc164ca586c382c9414725dedafc95
|
|
| BLAKE2b-256 |
7a088ea9b6938490e80d714138503c3e647d7223c82f82b876a7d3f27bda4bbc
|
Provenance
The following attestation bundles were made for omniplan_mcp-0.4.0.tar.gz:
Publisher:
publish.yml on cygnusyang/omniplan-mcp
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
omniplan_mcp-0.4.0.tar.gz -
Subject digest:
3c0740318a4cc1e0662de989db3770157373a5251fcc33fc661990d358bee8cf - Sigstore transparency entry: 1809424044
- Sigstore integration time:
-
Permalink:
cygnusyang/omniplan-mcp@9d6c184e333807dd1f25633b3487e34cb423c152 -
Branch / Tag:
refs/tags/v0.4.0 - Owner: https://github.com/cygnusyang
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish.yml@9d6c184e333807dd1f25633b3487e34cb423c152 -
Trigger Event:
push
-
Statement type:
File details
Details for the file omniplan_mcp-0.4.0-py3-none-any.whl.
File metadata
- Download URL: omniplan_mcp-0.4.0-py3-none-any.whl
- Upload date:
- Size: 25.2 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.13.12
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
6cd3cc3b33351ef804076637f42dab02d1e679ad134483e8e9ecc8dc9e72507d
|
|
| MD5 |
dd60a75adbc634d6c99bb489722ca9bb
|
|
| BLAKE2b-256 |
c9c14e826a5451846f678905ba81712dc418af8f888a122586d4747878625282
|
Provenance
The following attestation bundles were made for omniplan_mcp-0.4.0-py3-none-any.whl:
Publisher:
publish.yml on cygnusyang/omniplan-mcp
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
omniplan_mcp-0.4.0-py3-none-any.whl -
Subject digest:
6cd3cc3b33351ef804076637f42dab02d1e679ad134483e8e9ecc8dc9e72507d - Sigstore transparency entry: 1809424051
- Sigstore integration time:
-
Permalink:
cygnusyang/omniplan-mcp@9d6c184e333807dd1f25633b3487e34cb423c152 -
Branch / Tag:
refs/tags/v0.4.0 - Owner: https://github.com/cygnusyang
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
publish.yml@9d6c184e333807dd1f25633b3487e34cb423c152 -
Trigger Event:
push
-
Statement type: