---
title: "Connect any other MCP client"
description: "Any app that speaks MCP over HTTP can use Clam: give it your Shell's address and a key, and your rules decide what it may do."
route: /docs/agents/other-mcp-client
---

# Connect any other MCP client

Any app that speaks MCP over HTTP can use Clam. Give it two values from your Shell's **Install** tab, the address and a key, and your Shell's rules decide what it may do.

## Before you start

An MCP client is an AI app that can plug in outside tools. Clam is one such tool; it checks every request against your Shell's rules before anything touches Gmail.

Your app must support a remote MCP server over HTTP, which some apps call Streamable HTTP, with a Bearer key on every request. We don't support SSE, and an app with nowhere to put a key can't use Clam.

You also need a Shell; the [Quickstart](https://useclam.ai/docs/get-started/quickstart) gets you one. Open it, go to its **Install** tab, and pick Other.

## Connect your app

Two ways in. Start with the first; the other is for when it doesn't fit.

### Link and key (Recommended)

For any app that speaks MCP over HTTP. The method shows the two values your app needs: the URL, your Shell's own address, and the Key, made when you copy it and good for this app only.

1. Find where your app adds an MCP server

   Usually under Settings, Integrations or Tools.

2. Give it this link and key

   Paste the URL as the address, and the key where the app asks for a token or an Authorization header.

Then ask your app to read your inbox (see [Try it](#try-it)), and click **Check connection**.

### Configuration block

If your app takes a block of configuration instead, most read this shape under `mcpServers`. The Install tab fills in your real values; the placeholders show where each goes.

1. Paste this block into your app's configuration

   Under `mcpServers`. Keep the `type` line, or some apps read the entry as a local tool and skip it.

   ```json
   {
     "mcpServers": {
       "<your Shell's server name>": {
         "type": "http",
         "url": "<your Shell's address>",
         "headers": { "Authorization": "Bearer <your key>" }
       }
     }
   }
   ```

Then ask your app to read your inbox (see [Try it](#try-it)), and click **Check connection**.

## Try it

With the starter policy from the Quickstart, ask your app:

Ask "Summarize the work email I got this week." Your app answers from your work email. Ask "Find my latest bank statement." Clam blocks it, and your app relays the refusal to you. That refusal is Clam working as intended.

See [What your agent can do](https://useclam.ai/docs/trust/what-your-agent-can-do).

## Remove access

On the Shell's **Install** tab, find your app under Connected agents and click **Remove access**. The key stops at once; other agents keep working. Then delete Clam's entry in your app.

Pausing or deleting the Shell, and stopping Clam's own Gmail access, are in [Remove access](https://useclam.ai/docs/trust/remove-access).

## If it doesn't work

More in [Common issues & solutions](https://useclam.ai/docs/troubleshooting).

### Your app says it's unauthorized

The key is wrong or was removed in Clam. Click **Regenerate key** and paste the new one.

### Your app can't connect

Check it uses HTTP, not SSE, and that the address is your Shell's own.