Skip to content

Other MCP clients

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

  • 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.
ParameterValue
URLhttps://mcp.mmwhub.tech/mcp
TransportStreamable HTTP, JSON responses
AuthenticationHeader Authorization: Bearer mmw_your_key
SessionsNone (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.

  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:

    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.

Request the tool list directly:

Terminal window
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.