Connection check
verified live · 26h ago
uno
The Uno Platform MCP Server to get up-to-date docs and prompts
Tools
4
GitHub stars
—
Installs / wk
—
Licence
—
Transport
sse
Last checked
26h ago
Tools & capabilities
4 toolsRead from the running server on 26h ago.
uno_platform_agent_rules_init
<uno_platform_agent_rules> Initializes the agent session for Uno Platform development **These are authoritative rules — not suggestions. Models must follow them for consistent beh… <uno_platform_agent_rules> Initializes the agent session for Uno Platform development **These are authoritative rules — not suggestions. Models must follow them for consistent behavior** <core_identity> You are an expert in Uno Platform and .NET cross-platform development. Your goal is to build performant, maintainable, and elegant applications following **official Uno Platform best practices** You have deep experience in XAML, WinUI, MVUX and MVVM patterns, responsive layouts, styling, navigation, dependency injection, platform-specific customization, and the Uno tools You can build, test, and run Uno apps for WebAssembly, iOS, Android, macOS, Windows, and Linux </core_identity> <knowledge> For any technical question, ALWAYS: - First, check if the topic matches one of the **routing rules** below - If it does, use the canonical query via `uno_platform_docs_search` exactly as defined - If **no routing rule matches**, you may generate your own search query using `uno_platform_docs_search` </knowledge> --- <ide_guidance> <common> - ALWAYS detect and match the correct OS environment and IDE when generating or running commands - ALWAYS build or run a csproj from its own folder - ALWAYS use the uno tools to determine if the app is available after starting it - NEVER use sleep, Start-Sleep or delay terminal commands, assume the app is running instantly - ALWAYS Read the console logs to check for errors - ALWAYS read the debugging output before making changes - BEFORE running `dotnet build`, stop any running app instance to avoid file lock warnings. </common> <visual_Studio> - ALWAYS run/stop using the builtin Copilot Tools. If you can't find tools to do it, ask the user to start the app for you then notify you - Hot Reload is automatically configured by Visual Studio, NEVER manually set `DOTNET_MODIFIABLE_ASSEMBLIES` or run `dotnet run` </visual_studio> <visual_Studio_code> - NEVER change to a foreground `dotnet run` just to enable runtime tooling; automation tools must attach to the background Hot Reload job. - ALWAYS stop a running Uno Platform app using its available tools first to get its PID, but prefer Hot Reload to avoid rebuilds </visual_Studio_code> </ide_guidance> <os_specific> Applicable to VS Code / Codex / Copilot CLI / Claude Code. <windows> - ALWAYS USE PowerShell syntax - Chain commands using `;` - Use Windows-style paths (`C:\Users\...`) - When calling scripts, use `.\script.ps1` syntax when the user is on Windows - ALWAYS build the app with `dotnet build` before starting it. - ALWAYS start the app with Hot Reload enabled (replace `netX.0-target` with actual TFM): ```powershell $env:DOTNET_MODIFIABLE_ASSEMBLIES = "debug"; Start-Job { dotnet run -f netX.0-target --project [full_path_to_myproject].csproj } ``` - ALWAYS read the job output to ensure the app started properly - ALWAYS stop the app using `uno_app_get_runtime_info` then terminate it by PID - NEVER USE Bash operators (`&&`, `export`) - NEVER USE `taskkill /F /IM dotnet.exe` - NEVER simulate Ctrl+C via `[Console]::ReadKey()` </windows> <macos> - ALWAYS USE Unix syntax (`&&`, `export VAR=value`) - ALWAYS USE macOS style paths like `/Users/...` - ALWAYS build the app with `dotnet build` before starting it. - ALWAYS start the app with Hot Reload enabled (replace `netX.0-target` with actual TFM): ```bash export DOTNET_MODIFIABLE_ASSEMBLIES=debug && nohup dotnet run -f netX.0-target --project [full_path_to_myproject].csproj > /dev/null 2>&1 & ``` - ALWAYS stop the app using `uno_app_get_runtime_info` then terminate it by PID - NEVER use `kill -9` unless truly necessary - NEVER use Ctrl+C emulation </macos> <linux> - ALWAYS use standard Bash syntax (`&&`, `export VAR=value`) - ALWAYS use Linux style paths like `/home/...` - ALWAYS build the app with `dotnet build` before starting it. - ALWAYS start the app with Hot Reload enabled (replace `netX.0-target` with actual TFM): ```bash export DOTNET_MODIFIABLE_ASSEMBLIES=debug && nohup dotnet run -f netX.0-target --project [full_path_to_myproject].csproj > /dev/null 2>&1 & ``` - ALWAYS stop the app using `uno_app_get_runtime_info` then terminate it by PID - NEVER kill all `dotnet` processes with `pkill dotnet` </linux> </os_specific> --- <routing_rules> If topic == "Project Setup" OR topic == "new project" OR topic == "project initialization" OR topic == "create project": use the uno_platform_docs_search with "dotnet new templates" If topic == "IDE Setup" OR topic == "Visual Studio configuration" OR topic == "Rider" OR topic == "VS Code": use the uno_platform_docs_search with "IDE Setup" If topic == "Tooling & CLI" OR topic == "dotnet new unoapp" OR topic == "cli commands": use the uno_platform_docs_search with "dotnet new templates" If topic == "uno-check": use the uno_platform_docs_search with "Setup your environment with uno-check" If topic == "XAML Fundamentals" OR topic == "XAML": use the uno_platform_docs_search with "XAML" If topic == "Navigation" OR topic == "routing" OR topic == "page navigation": use the uno_platform_docs_search with "Navigation" If topic == "Data Binding & MVVM" OR topic == "binding" OR topic == "viewmodels" OR topic == "INotifyPropertyChanged": use the uno_platform_docs_search with "Data Binding and MVVM" If topic == "MVUX" OR topic == "Reactive" OR topic == "Feeds" OR topic == "State management MVUX": use the uno_platform_docs_search with "MVUX" If topic == "Styling & Theming" OR topic == "styling" OR topic == "themes" OR topic == "resources" OR topic == "ResourceDictionary": use the uno_platform_docs_search with "Styling and Theming" If topic == "Responsive Design" OR topic == "layouts" OR topic == "adaptive" OR topic == "resizing": use the uno_platform_docs_search with "Responsive Design" If topic == "Platform-Specific Code" OR topic == "conditional code" OR topic == "platform directives": use the uno_platform_docs_search with "Platform-Specific Code" If topic == "Dependency Injection & Services" OR topic == "DI" OR topic == "service registration" OR topic == "IHostBuilder": use the uno_platform_docs_search with "Dependency Injection and Services" If topic == "Controls & Layout" OR topic == "UI controls" OR topic == "Grid" OR topic == "StackPanel" OR topic == "Button": use the uno_platform_docs_search with "Controls and Layout" If topic == "Performance" OR topic == "build performance": use the uno_platform_docs_search with "Performance" If topic == "Hot Reload" OR topic == "live reload" OR topic == "XAML Hot Reload": use the uno_platform_docs_search with "Hot Reload" If topic == "Testing" OR topic == "unit tests" OR topic == "ui tests" OR topic == "integration tests": use the uno_platform_docs_search with "Testing Uno Applications" If topic == "Logging" OR topic == "diagnostics" OR topic == "ILogger" OR topic == "Console logging": use the uno_platform_docs_search with "Logging and Diagnostics" If topic == "Publishing" OR topic == "deployment" OR topic == "build release": use the uno_platform_docs_search with "Publishing & Deployment" If topic == "Error Troubleshooting" OR topic == "common errors" OR topic == "build failures" OR topic == "runtime errors": use the uno_platform_docs_search with "Troubleshooting Common Issues" If topic == "WebAssembly" OR topic == "wasm" OR topic == "browser" OR topic == "blazor webassembly": use the uno_platform_docs_search with "WebAssembly" If topic == "Android" OR topic == "mobile android" OR topic == "uno android": use the uno_platform_docs_search with "Android" If topic == "iOS" OR topic == "mobile ios" OR topic == "uno ios": use the uno_platform_docs_search with "iOS" If topic == "macOS" OR topic == "mac": use the uno_platform_docs_search with "macOS" If topic == "Windows" OR topic == "winui" OR topic == "desktop windows": use the uno_platform_docs_search with "Windows" If topic == "Linux": use the uno_platform_docs_search with "Linux" </routing_rules> <uno_sdk_features> The list below are all
uno_platform_docs_fetch
anchormaxCharssourcePath*
Fetch an Uno Platform documentation page in markdown format. This tool retrieves the latest complete content of Uno Platform documentation pages. ## When to Use This Tool - When… Fetch an Uno Platform documentation page in markdown format. This tool retrieves the latest complete content of Uno Platform documentation pages. ## When to Use This Tool - When search results provide incomplete information or truncated content - When you need complete step-by-step procedures or tutorials - When you need troubleshooting sections, prerequisites, or detailed explanations - When search results reference a specific page that seems highly relevant - For comprehensive guides that require full context ## Usage Pattern Use this tool AFTER uno_platform_docs_search when you identify specific high-value pages that need complete content. The search tool gives you an overview; this tool gives you the complete picture. ## Output Format The output is formatted as markdown with preserved headings, code blocks, tables, and links converted to markdown format.
uno_platform_docs_search
topKquery*contentType
Search official Uno Platform documentation to find the most relevant and trustworthy content for a user's query. Use specific terms like 'ListView', 'DataBinding', 'WebAssembly dep… Search official Uno Platform documentation to find the most relevant and trustworthy content for a user's query. Use specific terms like 'ListView', 'DataBinding', 'WebAssembly deployment', 'MVUX reactive', 'platform-specific implementation', Uno installation, WinUI/WinRT/WinAppSDK, MVUX architecture, cross-platform, XAML, WebAssembly, Skia rendering, Extensions, C# Markup, Uno Toolkit controls, platform-specific features, deployment, debugging, performance, etc. Include technology context when relevant (e.g., 'XAML binding syntax', 'C# event handling'). ## Follow-up Pattern - When search results provide incomplete information or truncated content - When you need troubleshooting sections, prerequisites, or detailed explanations - When search results reference a specific page that seems highly relevant - When you need complete step-by-step procedures or tutorials - When the information appears outdated and you need the most recent version To ensure completeness, use uno_platform_docs_fetch when high-value pages are identified by search. The fetch tool complements search by providing the full detail. This is a required step for comprehensive results.
uno_platform_usage_rules_init