Find answers to common questions about MIKROS MCP, supported workflows, security, game-engine compatibility, analytics integration, and marketing.
For an introduction to the platform, visit the MIKROS MCP Overview. For connection instructions, visit the Installation page.
MIKROS MCP allows compatible AI assistants to securely interact with supported MIKROS services using natural language.
Depending on the tools available to your AI client and your account permissions, an assistant may help create projects, integrate analytics, recommend events, retrieve metrics, prepare reports, and manage supported marketing workflows.
Model Context Protocol, or MCP, is an open standard that allows compatible AI assistants to connect to external tools and services.
Instead of only explaining how to complete a task, an MCP-enabled assistant can use authorized tools to perform supported actions on the user's behalf.
No. You can use MIKROS MCP by connecting it to a compatible AI client and describing the task you want to complete.
A basic understanding of MCP can still be helpful when configuring clients, authentication, permissions, and troubleshooting.
No. MIKROS MCP provides an AI-assisted way to access supported MIKROS capabilities. The dashboard remains useful for reviewing account settings, projects, credentials, billing, analytics, and campaign information directly.
No. The MIKROS Analytics SDK collects analytics data from inside your game. MIKROS MCP helps automate tasks such as project setup, SDK integration, event recommendations, implementation review, reporting, and workflow management.
Most analytics implementations use both the SDK and MIKROS MCP together.
Yes, when you use a compatible AI development environment that can edit project files. The assistant may be able to add the MIKROS SDK and make related code changes using official installation guidance.
You remain responsible for reviewing, testing, and accepting all proposed code changes before they are used in production.
MIKROS Analytics integration through MCP currently focuses on Unity.
Support for Unreal Engine, Godot, HTML5, and additional custom integrations may be added in the future. MIKROS Marketing is platform-agnostic, so supported marketing workflows may still be used for games built with other engines.
Yes. MIKROS MCP can help recommend supported preset events and event schemas based on your game's genre, design, and analytics goals.
Event recommendations should use official event names and parameters. Unsupported event names should not be invented.
A compatible AI development assistant may review the project configuration, installed SDK version, and event implementation using available MIKROS guidance.
You should still test the game and confirm that expected analytics data reaches the correct MIKROS project before releasing the game.
MIKROS MCP can help draft and configure supported marketing campaigns after your account has been authenticated and any required billing setup is complete.
A campaign should never be submitted or launched without your explicit approval.
Yes. MIKROS Marketing is platform-agnostic, so supported promotional workflows may be used for games created with Unity, Unreal Engine, Godot, HTML5, or other technologies.
Billing may be required for paid MIKROS services such as supported marketing campaigns. If billing is missing, complete the required setup through the MIKROS dashboard before attempting the action again.
Use Development API Keys while developing and testing. Never expose Production API Keys in source code, prompts, screenshots, public repositories, or configuration files that may be shared.
Store credentials using the secure configuration method recommended by the official MIKROS MCP installation guide and your AI client.
Yes. Review requested permissions, proposed code changes, project selections, and marketing actions before approving them.
High-impact actions, including campaign submission, should require clear user confirmation.
Yes. Many supported tasks can be requested through natural language, including creating projects, recommending events, retrieving analytics, preparing reports, and drafting marketing campaigns.
Development knowledge is still recommended when the assistant edits project files or integrates an SDK.
Yes. Developers may combine supported MIKROS MCP tools into custom AI-assisted workflows through compatible MCP clients.
Refer to the official MIKROS MCP GitHub documentation for available tools, parameters, response formats, examples, and operating guidelines.
Yes. MIKROS MCP is intended to expand across more of the game-development lifecycle, including project setup, analytics, reporting, marketing, launch readiness, and post-launch optimization.
Capabilities described as planned or coming soon should not be treated as currently available until they appear in the official documentation.
Confirm that the MCP configuration was saved in the correct location and that the client was restarted or refreshed. Compare your setup with the latest client-specific example in the official GitHub documentation.
Confirm that your credential is valid, belongs to the correct MIKROS account, and has access to the requested project. Replace expired or revoked credentials and verify that required environment variables are configured correctly.
Review the official MIKROS MCP GitHub documentation for current setup and troubleshooting information.
You can also contact support@tatumgames.com for additional assistance.