Integrations: Todoist independent task archive. Read-only storage of accessible data; shared AI-agent memory search is not connected yet.
YouGile: Two-way MMW integration. Connect in your MMW dashboard; manage tasks, deadlines and comments; privately search yougile:. How to obtain an API key.
On this page you will learn which clients work with MMW, which connection method to choose and how the methods differ. Step-by-step instructions are on each client’s page.
Three ways to connect
Section titled “Three ways to connect” 1. Local agent 2. Direct HTTP 3. OAuth connector ────────────── ────────────── ───────────────── client client claude.ai / ChatGPT │ stdio │ HTTPS │ HTTPS mmw-agent (uvx) │ Authorization: │ client's own token │ HTTPS, MMW_API_KEY │ Bearer mmw_… │ (sign-in on an MMW page) ▼ ▼ ▼ MMW server https://mcp.mmwhub.tech/mcp| Method | How it works | What you get |
|---|---|---|
| Local agent mmw-agent | The client starts the agent with uvx; the agent forwards calls to the server. Requires Python 3.11+ and uv. | Every server tool, the mmw_sync_status tool, and Claude Code and Codex session history upload (only with your consent). If the server is unreachable at start-up, the client does not fail. |
| Direct HTTP | The client config holds the server URL and an Authorization: Bearer mmw_… header. | Every server tool. No session history and no mmw_sync_status. Nothing to install. |
| OAuth connector | The web client opens an MMW page, you paste your API key, and the client receives its own token. | Every server tool. Your key is not shared with the client. |
The server tools are the same in every method: remember, search, search_history, forget, validate_memory, plus the tools of integrations connected to the key’s project.
Clients
Section titled “Clients”| Client or service | Recommended method | Alternative | Session history |
|---|---|---|---|
| Claude Code | Local agent | Direct HTTP | Yes, with consent |
| Claude Desktop | Local agent | — | No |
| claude.ai | OAuth connector | — | No |
| ChatGPT | App / OAuth | — | No |
| Cursor | Local agent | Direct HTTP | No |
| Codex | Direct MCP | Optional local agent | Yes, with consent |
| VS Code | Direct HTTP | — | No |
| Other MCP clients | Direct HTTP | Local agent, if the client runs stdio servers | No |
| Telegram bot | Linking in your account | — | Not applicable |
| Todoist task archive | Connect in MMW dashboard | — | Not applicable |
| YouGile tasks and comments | Connect in MMW dashboard | — | Not applicable |
Session history is uploaded only for Claude Code and Codex: the agent reads their session files on your computer. The agent searches uploaded sessions with the search_history tool.
Where to see connected clients
Section titled “Where to see connected clients”In the account, the “Clients & key” tab has a “Connected clients” table: which app uses the memory, how it connects (local agent, connector or direct), with which key, how many calls it made and when it was last seen.
The name is what the client says about itself. Through the local agent different apps use one key, so The current mmw-agent passes the server the name and version of the app that started it (header X-MMW-Client). With an older agent the table shows “Local agent (app not identified)”. MMW records clients since October 6, 2026.
One key or several
Section titled “One key or several”All clients using the same key see the same memory. If a key is bound to a project, the client sees only that project. A handy setup is one key per computer: if a laptop is lost, you revoke one key and every other client keeps working. See API keys and OAuth.