# Any other MCP client

If it speaks MCP over HTTP, it connects. Here is what it needs.

Sign in with browserAPI key

## Setup

1.  1
    
    Transport: Streamable HTTP at the server URL. SSE-only clients are not supported.
    
    **Server URL**
    
    ```
    https://api.zomler.com/mcp
    ```
    
2.  2
    
    Authentication, either: OAuth 2.1 with dynamic client registration, discovered from the URL's .well-known documents; or a bearer header carrying an API key.
    
    **Header**
    
    ```
    Authorization: Bearer zk_live_…
    ```
    
3.  3
    
    Tools: one per platform, plus capabilities and check\_balance. Every tool answers with the same envelope the REST API returns; see Reading a response.
    

## What you get

One tool per platform, plus `capabilities` and `check_balance`, at `https://api.zomler.com/mcp`. Every answer is [the envelope](https://zomler.com/docs/api/responses): what was measured, when, what was left out and why, and what it cost. Fresh fetches spend [credits](https://zomler.com/docs/api/credits); anything already held is free.

Keys are created under [API keys](https://app.zomler.com/api-keys) in the dashboard, where each one's calls and spend are listed. Revoking a key stops this client on its next call. The same key also calls the [REST API](https://zomler.com/docs/api).

[All clients](https://zomler.com/docs/mcp)

---

Source: https://zomler.com/docs/mcp/any