> ## Documentation Index
> Fetch the complete documentation index at: https://composio-preview.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Jan 8, 2026

> Latest updates and announcements

## Optional API Key Enforcement for MCP Servers

We've introduced a new project-level security setting that allows you to require API key authentication for all MCP server requests. This opt-in feature gives you fine-grained control over who can access your MCP endpoints.

> [!NOTE]
>
> **Opt-in today, default soon**: This feature is currently opt-in. Starting **March 1, 2026**, it will be enabled by default for new organizations. We recommend enabling it now to prepare your integrations.

## What's New

A new **"Require API Key for MCP"** toggle is now available in your Project Settings. When enabled, all requests to your MCP servers must include a valid Composio API key in the request headers.

| Setting | Default | Impact |
| - | - | - |
| `require_mcp_api_key` | `false` | Opt-in; no changes to existing behavior |

## How It Works

When the setting is **disabled** (default):

* MCP servers work without API key authentication
* Existing integrations continue to function unchanged

When the setting is **enabled**:

* All MCP requests must include the `x-api-key` header with a valid Composio API key
* Requests without a valid API key receive `401 Unauthorized`
* Only API keys belonging to the same project are accepted

### Request Examples

**Without API key (when enforcement is enabled):**

```bash theme={null}
curl -X POST "https://mcp.composio.dev/{your_mcp_server_url}" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize"}'

# Response: 401 Unauthorized
```

**With API key:**

```bash theme={null}
curl -X POST "https://mcp.composio.dev/{your_mcp_server_url}" \
  -H "Content-Type: application/json" \
  -H "x-api-key: ak_your_api_key" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize"}'

# Response: 200 OK
```

## Enabling the Setting

### Via Dashboard

1. Navigate to [Project Settings](https://dashboard.composio.dev/~/project/settings/general?utm_source=docs\&utm_medium=content\&utm_campaign=changelog-01-08-26-mcp-api-key-enforcement)
2. Go to the **Project Configuration** tab
3. Find the **"Require API Key for MCP"** toggle
4. Enable the toggle

![MCP API Key Toggle in Project Settings](https://mintcdn.com/composio-preview/cL3pOAF8H-TYHF1S/assets/images/mcp-api-key-toggle.png?fit=max\&auto=format\&n=cL3pOAF8H-TYHF1S\&q=85\&s=fb910c994cf1a40eb53a2511cc2502d8)

### Via API

Update your project configuration using the API:

```bash theme={null}
curl -X PATCH "https://backend.composio.dev/api/v3/org/project/config" \
  -H "Content-Type: application/json" \
  -H "x-api-key: ak_your_api_key" \
  -d '{"require_mcp_api_key": true}'
```

**Response:**

```json theme={null}
{
  "require_mcp_api_key": true,
  "is_2FA_enabled": true,
  "mask_secret_keys_in_connected_account": true,
  "log_visibility_setting": "show_all"
}
```

### Via Code

> [tab] Python
>
> ```python theme={null}
> import requests
>
> response = requests.patch(
>     "https://backend.composio.dev/api/v3/org/project/config",
>     headers={
>         "Content-Type": "application/json",
>         "x-api-key": "ak_your_api_key"
>     },
>     json={"require_mcp_api_key": True}
> )
>
> print(response.json())
> ```

> [tab] TypeScript
>
> ```typescript theme={null}
> const response = await fetch(
>   "https://backend.composio.dev/api/v3/org/project/config",
>   {
>     method: "PATCH",
>     headers: {
>       "Content-Type": "application/json",
>       "x-api-key": "ak_your_api_key"
>     },
>     body: JSON.stringify({ require_mcp_api_key: true })
>   }
> );
>
> console.log(await response.json());
> ```

## When to Use This

Enable API key enforcement when you need to:

* **Prevent unauthorized access** to your MCP servers
* **Control which applications** can interact with your MCP endpoints
* **Add an extra security layer** for production deployments
* **Audit and track** MCP server usage through API key attribution

## API Reference

### Get Current Setting

```http theme={null}
GET /api/v3/org/project/config
```

### Update Setting

```http theme={null}
PATCH /api/v3/org/project/config
```

```json theme={null}
{
  "require_mcp_api_key": true
}
```
