On this page you will learn:
- where to write;
- how the Telegram support chat works;
- what to include in a request and what never to send.
Where to write
Section titled “Where to write”support@mmwhub.tech — for anything: connection errors, payments, organization activation and pilots, data deletion, consent withdrawal.
Write from the email your account is registered with: it helps us find the account faster, and data deletion requests are accepted from that address.
Telegram support chat
Section titled “Telegram support chat”If you linked the MMW Telegram bot, a support person may message you through the bot or offer to open a support chat.
- The chat opens only after you agree: the bot asks, and you answer with “Yes” or “No”.
- While the chat is open, your messages go to support and are not saved to memory.
- The chat closes by itself after 24 hours without messages, or when you send
/unlink.
Support session with diagnostics
Section titled “Support session with diagnostics”If a client won’t connect or your agent can’t see its memory, the easiest way is a support session: an operator sees how things are set up on your side and suggests a fix. Nothing to install.
-
Account → “Support” → “Open a support session”. The account shows a six-digit code (valid for 15 minutes, single use) and a command.
-
Run the command in a terminal on the computer where your AI client runs:
Terminal window MMW_ENDPOINT=https://mcp.mmwhub.tech uvx --from https://app.mmwhub.tech/downloads/mmw-agent/mmw_agent-0.1.14-py3-none-any.whl mmw-agent support 482913 -
The agent shows exactly what it will send and asks whether to send diagnostics to the operator. Nothing leaves without your “yes”.
-
The operator reviews the diagnostics and may propose an action. The agent shows the whole change and applies it only after your “yes”.
-
You can stop any time: “End session” in the account or Ctrl+C in the terminal. An idle session closes itself after an hour.
What the operator sees: agent, Python and OS versions; whether a key is set and passes the check (never the key itself — only “present / length”); connectivity to MMW; which clients (Cursor, Claude Desktop, Codex, VS Code) are set up for MMW and with which addresses; sync state; the agent’s recent errors. Your home folder is replaced with ~, and secrets are scrubbed from error texts. Your files are never sent in full.
What the operator can propose — from a closed list only:
| Action | What happens after your “yes” |
|---|---|
| Re-check | The agent collects and sends diagnostics again |
| Fix a client config | The agent writes the MMW block into the Cursor, Claude Desktop, Codex or VS Code config from the template in these docs, keeping your key; it backs the file up first (*.bak-mmw-…) |
| Rotate the key | A hint only: where to rotate the key in your account. The operator never sees or sets keys |
| Enable the Stop hook | Adds the mmw-agent hook-stop hook to Claude Code settings, with a backup |
The operator cannot run arbitrary commands on your computer.
The timeline — who did what in the session, with times — is visible to you in your account and to the operator. Diagnostics are kept for 30 days, the timeline for three years, like support correspondence.
What to include
Section titled “What to include”The more precise the description, the faster the answer. A good request looks like this:
Subject: 401 in Cursor after rotating my key
Client: Cursor, connected via mmw-agent 0.1.14What I did: clicked Rotate in the account, pasted the new key into ~/.cursor/mcp.json, restarted CursorExpected: MMW tools workGot: 401 on every search callWhen: 2026-10-05, around 14:20 UTCrequest-id from the response: (if any)Output of mmw-agent status: (without the key)Checklist:
- client — Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, Codex, VS Code, other;
- connection method — mmw-agent and its version, or a direct HTTP connection;
- what you did, what you expected, what you got — the full error text;
- time of the error, with time zone;
- request-id, if the response has one;
- space — personal or organization (name), if the question is about an organization;
- URL of the account page, if the error is in the account.
Check these first
Section titled “Check these first”Many problems take a minute to fix:
- the agent does not see the tools — run
mmw-agent statuswith the sameMMW_API_KEYand restart the client; see Agent troubleshooting; - an unfamiliar error code — see Errors;
- the agent stopped saving but still finds old records — your subscription may have expired; see Plans and billing;
- “Your access to this organization has expired” — contact your organization’s admin, not support.
Correspondence and your data
Section titled “Correspondence and your data”Support correspondence — emails and Telegram chat messages — is kept for 3 years to provide support and resolve disputes, then deleted automatically. See Data and deletion.