mim: the Mimetic CLI

Bring your site's growth context into the terminal and the AI tools where you already work.

Quick start

Install it, then run setup. Setup handles sign-in, project detection, and MCP registration for whichever agents this machine has, and verifies each step for real rather than assuming it worked.

npm install -g @mimeticinc/mim-cli
mim setup

Setup registers the server with Claude Code, Codex, Cursor, Windsurf and Claude Desktop, whichever of them it finds. Each config file is backed up before it is written, and any other MCP servers you have are left alone. Add one later with mim mcp install cursor, or re-run mim mcp install all.

Install globally rather than through npx. Your agent launches mim as the MCP server, so it needs a mim that stays on your PATH, and every example in these docs is written as mim <command>. Requires Node.js 20 or newer.

Re-running setup is safe: it reuses your existing login and registration instead of creating new credentials.

If mim says "command not found" after the install, npm's global bin directory is not on your shell PATH. Run this to see the exact fix for your shell:

npx -y @mimeticinc/mim-cli setup

That prints the export PATH= line to add to your shell profile. Use the npx form for one-off commands too, but install globally before wiring up an MCP client.

Mimetic connects audits, live analytics, ad performance, lifecycle marketing, and session behavior so you can find what is holding growth back, decide what to do next, and move into a reviewable fix workflow without hopping between dashboards. Use mim directly from the shell or give the same context and actions to Claude Code, Codex, and other MCP clients.

Mimetic is the hosted service behind the CLI. Learn more at trymimetic.com.

What you can accomplish

• Find the highest-impact problems. Pull site audits, prioritized findings, and redacted session-replay insights into one project context.
• Answer growth questions with live data. Query acquisition, conversion, revenue, search, advertising, product analytics, and lifecycle performance without exporting CSV files.
• Repair measurement and acquisition setup. Provision hosted GA4 and Search Console, install tracking through a PR, Shopify pixel, or agent-applied snippet, and create or connect Google Ads resources.
• Turn findings into reviewable work. Start a code-fix workflow, then open the proposed PR, diff, preview, or Mimetic review page.
• Give coding agents business context. Let an MCP client inspect the same findings and connected data before it recommends or starts an action.

Integrations

Questions you can answer

Once the relevant accounts are connected, you can use the CLI or ask an MCP client questions such as:

• Which landing pages lost organic clicks but still convert well in GA4?
• Where is ad spend rising without a matching increase in conversions?
• What are users struggling with in recent high-priority sessions?
• Is the abandoned-cart flow live, and which campaign templates contain dead links?
• What is the highest-priority fix that is ready to start, and where can I review the proposed change?

From context to action

# Build a project brief from audits, findings, and connected signals
mim context --project yourstore.com

# Investigate acquisition and conversion performance
mim query-ga4 --project yourstore.com \
  --metrics sessions,conversions,totalRevenue \
  --dimensions sessionDefaultChannelGroup
mim query-gsc --project yourstore.com --dimensions query,page
mim query-bq --project yourstore.com --describe
mim query-bq --project yourstore.com --sql \
  "SELECT event_name, COUNT(*) AS n FROM \`events_*\` WHERE _TABLE_SUFFIX >= '20260901' GROUP BY 1 ORDER BY n DESC"
mim ads query --project yourstore.com

# Check lifecycle marketing and recent customer friction
mim klaviyo query --project yourstore.com --resource abandoned_cart_status
mim recordings --project yourstore.com

# Move a prioritized finding into a reviewable fix workflow
mim fixes list --project yourstore.com
mim fixes start 1 --project yourstore.com

Running commands

With a global install, run mim <command>. Without one, every command also works through npx:

npx -y @mimeticinc/mim-cli <command>

Authentication and local credentials

mim auth login opens a browser-based device flow. The server-issued token expires after a configured lifetime (90 days by default).

Logging in is idempotent: if this machine already has a working token, mim auth login verifies it against the server and reuses it instead of minting a new one. Use mim auth login --force to sign in as a different account.

After every login the CLI makes a real API call to confirm the token works and to list your projects. Projects belong to the email your Mimetic audit or report was sent to. If you sign in with a different email (personal instead of work, for example), the project list will be empty and the CLI tells you which email to use instead. mim auth status runs the same server-side verification and shows exactly which account and projects this machine is using.

Headless servers and SSH

The browser does not need to run on the same machine as the CLI. On a server without a desktop environment, start the device flow without attempting to launch a local browser:

mim auth login --no-open

Keep that process running, open the printed verification URL on your laptop or phone, and approve the login there. The server will finish the login by polling Mimetic and will store its own token in ~/.mim/config.json.

For unattended deployments, provide MIM_API_TOKEN through the server's secret manager or environment instead of relying on an interactive login. Do not put the token directly in a command argument.

By default, the CLI stores that bearer token as plaintext JSON in ~/.mim/config.json. On supported POSIX systems it enforces mode 0700 on the directory and 0600 on the file whenever credentials are saved. The token is not encrypted locally and is not stored in the operating-system keychain.

mim auth status
mim auth logout

mim auth logout revokes the stored managed token on Mimetic's server before removing the local file. If revocation cannot be confirmed, the CLI keeps the local credentials and reports the error. mim auth logout --local-only removes only the local copy; the token remains usable until it expires or is revoked another way.

For CI or a secret manager, set MIM_API_TOKEN instead. Environment tokens override locally stored credentials and are never changed by mim auth logout. Tokens are intentionally not accepted as command-line arguments, where they could be exposed through shell history or process listings.

Commands

Run mim --help for all options.

MCP

The mim-mcp binary proxies MCP stdio messages to Mimetic's hosted Streamable HTTP endpoint. mim setup registers it for you. To register only the MCP piece:

mim mcp install all       # every agent found on this machine
mim mcp install claude    # registers with Claude Code at user scope, then verifies
mim mcp install codex     # writes ~/.codex/config.toml
mim mcp install cursor    # writes ~/.cursor/mcp.json
mim mcp install windsurf  # writes ~/.codeium/windsurf/mcp_config.json
mim mcp install desktop   # writes Claude Desktop's config file

Every file write is backed up first and read back after, and other MCP servers already in the file are preserved. Codex config is TOML, so the entry is appended rather than the file being reparsed and rewritten. Running any of these twice does not create a duplicate entry. Add --print to any of them to see the block without writing anything.

mim mcp install claude registers at user scope on purpose: the Claude Code default (local scope) only applies to the directory the command ran in, which is the most common reason a "successful" install never shows up in a session. After registering, the CLI reads the entry back through claude mcp get mim and makes a live call to the hosted endpoint, so success means the server is reachable, not just that a command exited 0.

The MCP surface includes read tools for findings, redacted replay insights, and provider-read-only analytics queries. It also includes explicitly described action tools that can start audits, create or configure analytics/advertising resources, or initiate reviewable fix workflows. Review tool descriptions and your client's approval prompt before authorizing an action.

See docs/MCP.md for client configuration, the data flow, remote HTTP setup, and registry publication notes.

Connected-data access

The CLI and MCP wrapper are clients for Mimetic's hosted API; they do not query Google, PostHog, or Klaviyo directly from your computer. Credentials, tool arguments, and requested provider results pass through Mimetic's systems. Mimetic therefore has technical access to connected credentials and data while providing the request. A connector's “read-only” label describes its permissions at the third-party provider; it does not mean the data is invisible to Mimetic.

PostHog queries can return distinct identifiers and event or user properties available to the connected project. The current Klaviyo connector does not request profile or write scopes. If you invoke tools through an AI client, the returned data is also provided to the AI client and account you configured.

See the Privacy Policy and Terms of Service before connecting production data.

Transport security

Bearer tokens are sent only to HTTPS URLs by default. Plain HTTP is allowed for loopback hosts such as localhost, 127.0.0.1, and ::1. For an unusual local development environment, MIM_ALLOW_INSECURE_HTTP=1 explicitly disables this protection; do not use it with production credentials.

Environment

Metadata telemetry includes the client version, project, command or tool name, status, duration, trace ID, HTTP status, and bounded diagnostics. It is designed not to include access tokens, query text, MCP arguments, replay narratives, or provider results. Hosted requests and results still reach Mimetic when telemetry is disabled.

Development

npm install
npm run typecheck
npm test
npm run build
npm pack --dry-run

Licensed under the MIT License. Copyright © 2026 Mimetic Inc.