Skip to content

Project Roadmap

Jump to bottom
Marcus Sanatan edited this page Oct 1, 2025 · 2 revisions

Unity MCP - Project Roadmap

Welcome to the Unity MCP roadmap! This document outlines our high-level goals, priorities, and planned features for the project. It's intended to give users and contributors insight into where the project is heading, enabling seamless communication between the Unity Editor and LLM tools like Claude Desktop and Cursor via the Model Context Protocol (MCP).

Please Note: This roadmap is a living document and reflects our current plans and priorities. These are subject to change based on community feedback, unforeseen challenges, or shifts in project direction. Timelines are estimates and not guarantees. The dates on linked issues/PRs may reflect when they were opened, not necessarily the target completion date.

Want to contribute or discuss the roadmap? We'd love your input! Please see the How to Contribute or Provide Feedback section below.

Table of Contents

Overall Vision & Goals

Our primary goal for Unity MCP is to provide a robust, flexible, and easy-to-use bridge and MCP server enabling powerful interactions between the Unity Editor and other MCP clients.

Key objectives driving our development include:

  • Goal 1: Simplify Installation & Configuration: Make setup straightforward and reliable across different platforms and MCP clients. (High Priority)
  • Goal 2: Enhance Stability & Performance: Ensure reliable communication and efficient handling of commands, especially in large projects.
  • Goal 3: Expand Features & Integrations: Add more tools, support more Unity features (like HDRP), and integrate with more AI services/tools.
  • Goal 4: Improve User & Developer Experience: Enhance documentation, provide better feedback/error handling, and support community contributions like localization.
  • Goal 5: Increase Maintainability & Testability: Refine the architecture and add tests to ensure long-term health.

Current Focus / Next Release (v5.0)

We are currently focused on improving the plugin installation process. Our goal is to be on the Unity Asset Store. As such, we need to make the plugin as self-contained as possible. That means, the user is guided to install dependencies like Git, Python and uv within the plugin so they can successfully use it.

Target: Aiming for completion in early October 2025.

Key items being actively worked on or planned for this cycle:

  • 🧹 Tech Debt/Refactoring: Use typed parameters/classes instead of a JSON object in the tool parameters
  • 🧹 Tech Debt/Refactoring: Return typed classes instead of a Python dictionaries in the MCP server
  • 📄 Docs: Update docs to make it clear how to add new tools

Legend: ✨ Feature, 🐛 Bug Fix, 📈 Improvement, 📄 Docs, 🧪 Tests, 🧹 Tech Debt/Refactoring, 🏗️ Architecture

Short-Term Plans (Post-Installation Overhaul)

Following the installation refactor, our focus will shift to Stabilization, Configuration Improvements, and Integrating Community Contributions.

Planned items include (priorities may change):

  • ✨ Feature: UI refresh with UI toolkit, and being transparent of the changes on Unity's side
  • 🧹 Tech Debt/Refactoring: Utilize resources and prompts so MCP clients can perform better
  • 🐛 Fix for shader generation #290
  • ✨ Feature: Prepare and upload to Unity Asset Store (#6).

Mid-Term Plans

These are items we aim to tackle further out. Details and priorities are less defined.

  • ✨ Feature: Explore Runtime MCP Operation (#58).
  • 📈 Improvement: Explore ways to reduce context sent to LLM (#287).
  • 📈 Improvement: Incorporate screenshots into LLM decision making

Long-Term Ideas & Future Directions

This section captures bigger ideas or major features that are further down the line (>6-9 months) or require significant research/design.

  • Create more auto-configurations to support for additional MCP clients.
  • Add more play mode functionality
  • Add prompt templates to speed up multiple 2D and 3D workflows
  • ✨ Feature: Add HDRP support (#27).

Maybe / Icebox / Backlog

These are ideas that have been suggested or considered but are not currently planned for active development. They might be revisited later.

  • Visual scripting integration (e.g., Bolt/PlayMaker).

Recently Completed

For details on past releases and completed work, please see:

How to Contribute or Provide Feedback

Your feedback and contributions are crucial! Here's how you can get involved:

  1. Discuss Ideas: Use GitHub Discussions or open an issue with the enhancement or discussion label to discuss roadmap items or propose new ideas.
  2. Request Features: For specific, well-defined feature requests, please open a new issue using the "Feature Request" template. Check existing issues first!
  3. Report Bugs: If you find a bug, please open a bug report. Provide clear steps to reproduce.
  4. Contribute Code/Docs: Check our README.md guide for details. Look for issues tagged help wanted or good first issue. Review open Pull Requests.
  5. Comment on Issues/PRs: Provide feedback directly on the issues and pull requests linked in the roadmap sections above.

Disclaimer

This roadmap provides a high-level overview of potential future direction for Unity MCP. It is not a commitment or guarantee. Priorities and timelines may change significantly based on various factors including (but not limited to) community feedback, resource availability, technical challenges, and strategic shifts. We will strive to keep this document updated but please refer to specific GitHub Issues and Milestones for the most granular, up-to-date status.

Clone this wiki locally