# Connect Dify to aicharged.io

> Dify: an HTTP MCP server under Tools → MCP with a custom Authorization header.

## At a glance

| Kind | Sign-in | Platforms | Status | Verified |
|---|---|---|---|---|
| Automation | API key (Bearer), OAuth sign-in | Web | works today | 2026-10-22 |

- MCP: `https://aicharged.io/api/v1/mcp`
- Docs: https://docs.dify.ai/en/cloud/use-dify/build/mcp

## Recipe

1. Open Integrations → Tools → MCP and add an MCP server (HTTP).
2. Server URL: https://aicharged.io/api/v1/mcp · name and server identifier: aicharged
3. Advanced Options → Custom Headers: Authorization = Bearer <API_KEY>

Remote MCP server URL:

```text
https://aicharged.io/api/v1/mcp
```

Authorization header value:

```text
Bearer <API_KEY>
```

[Client documentation](https://docs.dify.ai/en/cloud/use-dify/build/mcp)

## Authentication

- Send `Authorization: Bearer <API_KEY>` with every request. Create a key at https://aicharged.io/admin/account/api-keys.
- OAuth 2.1 (PKCE S256) is available for clients that cannot send a static key (ChatGPT).
- Without a key the endpoint answers 401 with a WWW-Authenticate header that points to https://aicharged.io/.well-known/oauth-protected-resource.

All 51 clients: https://aicharged.io/connect.md

HTML version: https://aicharged.io/connect/dify