# Connect Kiro to aicharged.io

> Kiro: ~/.kiro/settings/mcp.json with the key from an environment variable that you approve in the Kiro settings.

## At a glance

| Kind | Sign-in | Platforms | Status | Verified |
|---|---|---|---|---|
| Editors & IDEs | API key (Bearer), OAuth sign-in | macOS, Linux, Windows | works today | 2026-10-22 |

- MCP: `https://aicharged.io/api/v1/mcp`
- Docs: https://kiro.dev/docs/mcp/configuration

## Recipe

Config file (`~/.kiro/settings/mcp.json`):

```json
{
  "mcpServers": {
    "aicharged": {
      "url": "https://aicharged.io/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${AICHARGED_API_KEY}"
      },
      "autoApprove": []
    }
  }
}
```

Add AICHARGED_API_KEY to Mcp Approved Env Vars in the Kiro settings, otherwise Kiro does not expand it. For one project use .kiro/settings/mcp.json.

Config with the key inline (`~/.kiro/settings/mcp.json`):

```json
{
  "mcpServers": {
    "aicharged": {
      "url": "https://aicharged.io/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer <API_KEY>"
      },
      "autoApprove": []
    }
  }
}
```

[Client documentation](https://kiro.dev/docs/mcp/configuration)

## 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/kiro