# mantis-mcp

Build proven high converting product showrooms and websites from your existing ecommerce catalog

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.1.0
- **Author:** io.github.kahlilashanti
- **License:** MIT
- **npm:** mantis-mcp
- **Source:** https://github.com/kahlilashanti/mantis-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 3 days

## Security scan

- **Status:** warnings
- **Scanned:** 2026-10-01T21:47:43.430Z
- **Version scanned:** 1.1.0
- **CVEs:** none found by OSV at scan time

## Tools

14 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `installMantisSDK` — Install and configure Mantis SDK with proper .npmrc setup
- `validateSetup` — Validate Mantis SDK installation and configuration
- `createMantisIntegration` — Generate Mantis integration code for your framework
- `generateEventHandler` — Generate event handler code for Mantis SDK events
- `debugPostMessage` — Debug postMessage communication issues
- `analyzeConsoleErrors` — Analyze console errors and suggest fixes
- `checkBrowserCompatibility` — Check browser compatibility issues
- `testMantisEvent` — Test Mantis SDK events and responses
- `simulateUserFlow` — Simulate user interactions with Mantis experience
- `getPerformanceMetrics` — Get performance metrics for 3D experience
- `analyzeEventFlow` — Analyze event flow and user behavior
- `importCatalog` — 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
- `createStore` — Create a 3D commerce showroom that converts better than traditional e-commerce. Use this after importing products to build a store that drives sales. Shopify ch
- `publishStore` — Publish the 3D showroom live so customers can start shopping and converting. Final step to launch a high-converting store.

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mantis\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"mantis-mcp\"\n      ],\n      \"env\": {\n        \"MANTIS_AUTH_TOKEN\": \"<YOUR_MANTIS_AUTH_TOKEN>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `MANTIS_AUTH_TOKEN` — Mantis Auth Token (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 1 credential (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Moderate blast radius — holds an api key; runs on your machine.
- Floor 23, ceiling 23 (tier: moderate)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/mantis-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/mantis-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/mantis-mcp
- HTML page: https://forgeregistry.com/registry/mantis-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.