# API Key

A **API Key** authenticates MCP client connections to the gateway. Every time Claude Desktop, VS Code, or your application makes a request through `gateway.mewcp.com`, it presents this key.

One key covers every app you have connected. You do not need a separate key per app, and you do not need to change the key when you connect a new one.

---

## Format

```
mcp_live_<hex_token>
```

Example: `mcp_live_7df44e73e8cd42bbf4860ffc66520ef...`

---

## How to get one

<Stepper>

1. Log in to the [MewCP dashboard](https://mewcp.com/dashboard)
1. Go to **API Keys**
1. Copy your **API Key**

</Stepper>

---

## How to use it

Pass it as a Bearer token in the `Authorization` header:

```
Authorization: Bearer MEWCP_API_KEY
```

In client configs:

```json
"headers": {
  "Authorization": "Bearer MEWCP_API_KEY"
}
```

Clients that cannot set an `Authorization` header can send the key as `x-mewcp-key` instead.

The key goes with your toolset endpoint:

```
https://gateway.mewcp.com/personal/mcp
```

---

## What it does and does not carry

The API Key identifies **you**. It does not carry any app credential.

When a tool runs, MewCP looks up the account you connected for that app and injects it into the upstream request at that moment. Your connected app credentials never travel to your client, your agent, or the model. The only secret in your config is this key.

---

## Best practices

- **Never put it in frontend code.** API Keys are for server-to-gateway connections only.
- **Use an environment variable.** Keep the key out of committed config files.
- **Revoke if compromised.** Go to **API Keys** and click **Revoke**. The old key stops working immediately.