IntelliJ MCP Server extension plugin for Unity Editor
{
"mcpServers": {
"mcp-extension-unity": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
IntelliJ MCP Server extension plugin for Unity Editor
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
Apache-2.0. View license →
Is it maintained?
Last commit 30 days ago. 2 stars.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
No known vulnerabilities.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationHave you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
An open-source AI agent that brings the power of Gemini directly into your terminal.
The full-stack TypeScript framework to build, test, and deploy production-ready MCP servers and AI-native apps.
Open-source persistent memory for AI agent pipelines (LangGraph, CrewAI, AutoGen) and Claude. REST API + knowledge graph + autonomous consolidation.
MCP Security Weekly
Get CVE alerts and security updates for Mcp Extension Unity and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A plugin that extends the MCP Server built into JetBrains Rider. Adds tools for operating Unity Editor from any Coding Agents.
git workspace, claude --workspace, etc., you get tools that work without any additional configuration.The run_unity_tests tool runs tests on Unity Editor through Rider's test infrastructure.
Recommend filtering by assemblyNames, categoryNames, groupNames, and testNames to narrow down the tests to the scope of changes.
Parameters
| Name | Required | Description |
|-----------------|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| testMode | Required | EditMode or PlayMode (case insensitive). If the includePlatforms in the assembly definition file (.asmdef) contains Editor, it is an Edit Mode test; otherwise it is a Play Mode test. |
| assemblyNames | Required | Names of test assemblies to run (without .dll extension, e.g. MyFeature.Tests). Specify the name property in the assembly definition file. |
| categoryNames | Optional | Names of a category to include in the run. Any test or fixture runs that have a category matching the string. |
| groupNames | Optional | Same as testNames, except that it allows for Regex. This is useful for running specific fixtures or namespaces. |
| testNames | Optional | The full name of the tests to match the filter. This is usually in the format FixtureName.TestName. If the test has test arguments, then include them in parentheses. |
Response
| Field | Type | Description |
|---------------------|---------|----------------------------------------------------------------|
| success | boolean | true if all tests passed |
| passCount | number | Number of passing tests |
| failCount | number | Number of failing tests