# Other MCP clients

> Connect any MCP client to MMW over Streamable HTTP with an API key. The server is stateless.

On this page you will connect a client that has no dedicated guide, and check the server straight from a terminal.

## What you get

- The `remember`, `search`, `forget`, `validate_memory` and `gateway_call` tools, plus tools of integrations connected to the key's project.
- The same memory your other clients see with a key from the same account and project.

## Server parameters

| Parameter | Value |
|---|---|
| URL | `https://mcp.mmwhub.tech/mcp` |
| Transport | Streamable HTTP, JSON responses |
| Authentication | Header `Authorization: Bearer mmw_your_key` |
| Sessions | None (stateless): every request stands on its own |

Because the server keeps no sessions, a client never needs to reconnect after a pause, a computer sleep or a network drop.

## Setup

1. In your client's settings, find where to add a remote MCP server over HTTP (it may be called "remote", "HTTP" or "Streamable HTTP").

2. Enter the URL and header. In many clients it looks like this:

   ```json title="Client MCP configuration"
   {
     "mcpServers": {
       "mmw": {
         "url": "https://mcp.mmwhub.tech/mcp",
         "headers": { "Authorization": "Bearer mmw_your_key" }
       }
     }
   }
   ```

   Key names (`mcpServers`, `servers`, `url`, `headers`, `type`) vary by client; check its documentation.

3. Restart the client and check the tool list.

Use the local mmw-agent: set the command to `uvx`, the arguments to `--from https://app.mmwhub.tech/downloads/mmw-agent/mmw_agent-0.1.4-py3-none-any.whl mmw-agent`, and the environment variables `MMW_API_KEY` and `MMW_ENDPOINT=https://mcp.mmwhub.tech`. Python 3.11+ and uv are required. See [The mmw-agent](/agent/overview/).

## Check from a terminal

Request the tool list directly:

```bash
curl -s https://mcp.mmwhub.tech/mcp \
  -H "Authorization: Bearer mmw_your_key" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
```

The response is JSON-RPC with a `result.tools` array listing `remember`, `search`, `forget`, `validate_memory` and `gateway_call`. If the key is wrong, revoked or missing, you get a 401.

To check inside the client, ask "Remember in MMW: staging is deployed with the systemd unit app-staging", then in a new conversation "How do we deploy staging? Check MMW." The expected answer mentions `app-staging` and cites the record.

## Common problems

Check that the header is named `Authorization`, the value starts with `Bearer ` and the key has not been revoked.

Too many calls per minute for your plan. Wait a minute; limits are listed in [Limits](/reference/limits/).

Without an active subscription the server reports that memory is unavailable. Once a subscription expires, memory is read-only for a grace period.

## What's next