PHXH
/
unity-mcp
51
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
unity-mcp/MCPForUnity/UnityMcpServer~/src/pyproject.toml

21 lines
513 B
TOML
Raw Normal View History

Rename plugin folder to MCPForUnity (#303) * Copy UnityMcpBridge into a new MCPForUnity folder This is to close #284 * refactor: rename UnityMcpBridge directory to MCPForUnity in docs * chore: rename UnityMcpBridge directory to MCPForUnity across workflow files * chore: rename UnityMcpBridge directory to MCPForUnity across all files * refactor: update import paths from UnityMcpBridge to MCPForUnity across test files * fix: update module import paths to use MCPForUnity instead of UnityMcpBridge * chore: update unity-mcp package path to MCPForUnity directory * feat: add OneTimeSetUp to initialize CommandRegistry before tests run Hopefully fix the CI failures * Apply recent fix to new folder * Temporarily trigger tests to see if CI works * Revert "Temporarily trigger tests to see if CI works" It works! This reverts commit 8c6eaaad07545cef047769f2c52fe506545a8161.
2025-10-04 08:23:28 +08:00
[project]
name = "MCPForUnityServer"
chore: bump version to 6.2.0
2025-10-19 08:47:51 +08:00
version = "6.2.0"
Rename plugin folder to MCPForUnity (#303) * Copy UnityMcpBridge into a new MCPForUnity folder This is to close #284 * refactor: rename UnityMcpBridge directory to MCPForUnity in docs * chore: rename UnityMcpBridge directory to MCPForUnity across workflow files * chore: rename UnityMcpBridge directory to MCPForUnity across all files * refactor: update import paths from UnityMcpBridge to MCPForUnity across test files * fix: update module import paths to use MCPForUnity instead of UnityMcpBridge * chore: update unity-mcp package path to MCPForUnity directory * feat: add OneTimeSetUp to initialize CommandRegistry before tests run Hopefully fix the CI failures * Apply recent fix to new folder * Temporarily trigger tests to see if CI works * Revert "Temporarily trigger tests to see if CI works" It works! This reverts commit 8c6eaaad07545cef047769f2c52fe506545a8161.
2025-10-04 08:23:28 +08:00
description = "MCP for Unity Server: A Unity package for Unity Editor integration via the Model Context Protocol (MCP)."
readme = "README.md"
requires-python = ">=3.10"
Add testing and move menu items to resources (#316) * deps: add tomli>=2.3.0 dependency to UnityMcpServer package * feat: dynamically fetch package version from pyproject.toml for telemetry * Add pydantic * feat: add resource registry for MCP resource auto-discovery * feat: add telemetry decorator for tracking MCP resource usage * feat: add auto-discovery and registration system for MCP resources * feat: add resource registration to MCP server initialization * feat: add MCPResponse model class for standardized API responses * refactor: replace Debug.Log calls with McpLog wrapper for consistent logging * feat: add test discovery endpoints for Unity Test Framework integration We haven't connected them as yet, still thinking about how to do this neatly * Fix server setup * refactor: reduce log verbosity by changing individual resource/tool registration logs to debug level * chore: bump mcp[cli] dependency from 1.15.0 to 1.17.0 * refactor: remove Context parameter and add uri keyword argument in resource decorator The Context parameter doesn't work on our version of FastMCP * chore: upgrade Python base image to 3.13 and simplify Dockerfile setup * fix: apply telemetry decorator before mcp.tool to ensure proper wrapping order * fix: swap order of telemetry and resource decorators to properly wrap handlers * fix: update log prefixes for consistency in logging methods * Fix compile errors * feat: extend command registry to support both tools and resources * Run get tests as a coroutine because it doesn't return results immediately This works but it spams logs like crazy, maybe there's a better/simpler way * refactor: migrate from coroutines to async/await for test retrieval and command execution * feat: add optional error field to MCPResponse model * Increased timeout because loading tests can take some time * Make message optional so error responses that only have success and error don't cause Pydantic errors * Set max_retries to 5 This connection module needs a lookover. The retries should be an exponential backoff and we could structure why it's failing so much * Use pydantic model to structure the error output * fix: initialize data field in GetTestsResponse to avoid potential errors * Don't return path parameter * feat: add Unity test runner execution with structured results and Python bindings * refactor: simplify GetTests by removing mode filtering and related parsing logic * refactor: move test runner functionality into dedicated service interface * feat: add resource retrieval telemetry tracking with new record type and helper function * fix: convert tool functions to async and await ctx.info calls * refactor: reorganize menu item functionality into separate execute and get commands An MCP resource for retrieval, and a simple command to execute. Because it's a resource, it's easier for the user to see what's in the menu items * refactor: rename manage_menu_item to execute_menu_item and update tool examples to use async/await We'll eventually put a section for resources * Revert "fix: convert tool functions to async and await ctx.info calls" This reverts commit 012ea6b7439bd1f2593864d98d03d9d95d7bdd03. * fix: replace tomllib with tomli for Python 3.10 compatibility in telemetry module * Remove confusing comment * refactor: improve error handling and simplify test retrieval logic in GetTests commands * No cache by default * docs: remove redundant comment for HandleCommand method in ExecuteMenuItem
2025-10-13 23:16:43 +08:00
dependencies = [
"httpx>=0.27.2",
"mcp[cli]>=1.17.0",
"pydantic>=2.12.0",
"tomli>=2.3.0",
]
Rename plugin folder to MCPForUnity (#303) * Copy UnityMcpBridge into a new MCPForUnity folder This is to close #284 * refactor: rename UnityMcpBridge directory to MCPForUnity in docs * chore: rename UnityMcpBridge directory to MCPForUnity across workflow files * chore: rename UnityMcpBridge directory to MCPForUnity across all files * refactor: update import paths from UnityMcpBridge to MCPForUnity across test files * fix: update module import paths to use MCPForUnity instead of UnityMcpBridge * chore: update unity-mcp package path to MCPForUnity directory * feat: add OneTimeSetUp to initialize CommandRegistry before tests run Hopefully fix the CI failures * Apply recent fix to new folder * Temporarily trigger tests to see if CI works * Revert "Temporarily trigger tests to see if CI works" It works! This reverts commit 8c6eaaad07545cef047769f2c52fe506545a8161.
2025-10-04 08:23:28 +08:00
[build-system]
requires = ["setuptools>=64.0.0", "wheel"]
build-backend = "setuptools.build_meta"
[tool.setuptools]
py-modules = ["config", "server", "unity_connection"]
packages = ["tools"]