EasyAR MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EASYAR_API_TOKEN | No | Your registered EasyAR user token | |
| EASYAR_UNITY_PATH | No | Path to Unity executable | |
| EASYAR_API_BASE_URL | No | Base URL for EasyAR API (default: https://www.easyar.cn) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| easyar_server_statusA | Return mcp-easyar server version, capability summary, resources, authorization state, and recommended next steps. |
| easyar_list_samplesA | List known EasyAR Unity sample categories and setup requirements. |
| easyar_official_infoA | Return official EasyAR links and package versions captured by this MCP server. |
| easyar_auth_statusA | Report whether EasyAR account environment variables are configured without exposing secret values. |
| easyar_generate_client_configB | Generate MCP client configuration snippets for connecting Codex, Claude Desktop, or another stdio MCP client. |
| easyar_generate_sample_planB | Generate a step-by-step plan for preparing and running an EasyAR Unity sample. |
| easyar_inspect_unity_projectB | Inspect a Unity project and report EasyAR/sample readiness signals. |
| easyar_check_sample_readinessA | Check whether a Unity project has the local pieces needed to run a specific EasyAR sample workflow. |
| easyar_validate_local_configC | Validate ProjectSettings/EasyAR/easyar.local.json without returning secret values. |
| easyar_analyze_unity_logC | Analyze Unity Editor or build logs for common EasyAR, permission, license, compile, and build issues. |
| easyar_prepare_unity_projectC | Prepare a Unity project for an authorized EasyAR sample workflow by creating editor helpers, local config templates, and secret ignore rules. |
| easyar_create_mobile_settings_helperC | Create a Unity Editor script that applies Android/iOS player settings commonly required by EasyAR camera samples. |
| easyar_create_build_settings_helperB | Create a Unity Editor script that adds the matching EasyAR sample scene to Build Settings and optionally switches the active build target. |
| easyar_create_device_build_helperB | Create a Unity Editor script that builds the configured EasyAR sample scenes for Android, iOS, or standalone targets. |
| easyar_create_sample_runnerB | Create a Unity Editor script that opens EasyAR sample scenes by name. |
| easyar_create_mono_behaviourC | Create a Unity C# MonoBehaviour template for common EasyAR sample development tasks. |
| easyar_write_csharp_fileB | Create or replace a C# script inside a Unity project. The file must stay inside the project and end with .cs. |
| easyar_unity_environmentB | Inspect local Unity executable configuration and common install locations without launching Unity. |
| easyar_run_unity_methodC | Run a Unity static editor method in batch mode for project automation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| easyar-samples-catalog | |
| easyar-official-info | |
| easyar-unity-checklist | |
| easyar-quickstart-workflow |
TDQS
Scored across 19 tools
Most tools have distinct purposes, but there is some overlap among the three build helpers (build_settings, device_build, mobile_settings) and between prepare_unity_project and the individual helper creators. Overall, descriptions are clear enough to avoid major confusion.
All tools follow a consistent 'easyar_verb_noun' pattern with snake_case. No mixing of conventions, making the set predictable and easy to navigate.
19 tools is slightly above the typical well-scoped range of 3-15, but each tool addresses a specific aspect of EasyAR Unity development, justifying the count. It's still manageable for an agent.
The tool set covers the core workflow: analysis, preparation, build helpers, validation, and automation. Minor gaps exist, such as lacking a tool to directly query EasyAR SDK version or manage licenses, but the stated domain (sample workflow) is adequately covered.