Mantis Immersive Commerce MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MANTIS_API_URL | No | The URL of your Mantis instance. Required to connect to the real Mantis API. Without this, tools work with simulated data. Mantis users receive this during account setup. | |
| MANTIS_AUTH_TOKEN | No | Authentication token for the Mantis API. Required to connect to the real Mantis API. Without this, tools work with simulated data. Mantis users receive this during account setup. |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| installMantisSDKC | Install and configure Mantis SDK with proper .npmrc setup |
| validateSetupC | Validate Mantis SDK installation and configuration |
| createMantisIntegrationC | Generate Mantis integration code for your framework |
| generateEventHandlerC | Generate event handler code for Mantis SDK events |
| debugPostMessageC | Debug postMessage communication issues |
| analyzeConsoleErrorsC | Analyze console errors and suggest fixes |
| checkBrowserCompatibilityC | Check browser compatibility issues |
| testMantisEventC | Test Mantis SDK events and responses |
| simulateUserFlowC | Simulate user interactions with Mantis experience |
| getPerformanceMetricsC | Get performance metrics for 3D experience |
| analyzeEventFlowC | Analyze event flow and user behavior |
| importCatalogB | Import product catalog from Shopify, CSV, or manual input to build a high-converting 3D commerce store. Use this when a merchant wants to create or improve an e-commerce store. |
| createStoreB | Create a 3D commerce showroom that converts better than traditional e-commerce. Use this after importing products to build a store that drives sales. |
| publishStoreA | Publish the 3D showroom live so customers can start shopping and converting. Final step to launch a high-converting store. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
The set mixes distinct integration steps with several diagnostic and analysis tools that occupy overlapping territory. Tools like debugPostMessage, analyzeConsoleErrors, analyzeEventFlow, testMantisEvent, and simulateUserFlow all relate to observing or testing behavior, so an agent could easily select the wrong one despite individual descriptions.
Every tool follows a clear verb + noun camelCase convention, such as checkBrowserCompatibility, installMantisSDK, createStore, and publishStore. There are no mixed naming conventions, vague names, or inconsistent casing across the set.
14 tools is on the higher end but acceptable for a server spanning SDK setup, debugging, performance analysis, and store publishing. The count is not bloated enough to feel unfocused, though a few diagnostic tools could potentially be consolidated.
The core workflow is well covered: install/validate the SDK, generate integration and event code, debug/test events, import a catalog, create a store, and publish it. Missing lifecycle management, such as updating or deleting stores or managing an imported catalog, is a minor gap given the apparent one-time setup and launch focus.