> For the complete documentation index, see [llms.txt](https://docs.avastudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avastudio.com/api-and-mcp/sign-in-with-ava.md).

# Sign in with Ava

Sign in with Ava lets ChatGPT, Claude and other apps use your Ava account without an API key. You sign in to Ava Studio, choose what the app may do, and can disconnect it at any time.

To set it up in ChatGPT or Claude, follow [Connect your AI app](https://docs.avastudio.com/api-and-mcp/connect.md).

Free Ava accounts can connect too; no paid Ava plan or API key is required. Paid operations use your account's available credits, including any active [starter credits](https://docs.avastudio.com/api-and-mcp/credits-and-pricing.md#free-accounts-and-starter-credits). Your MCP client's own plan requirements are separate from your Ava plan.

#### What you approve

When an app connects, Ava Studio shows a consent screen with:

* **The app's name and web address.** ChatGPT and Claude are marked **Verified**. Any other app is **Unverified**: only continue if you started the connection yourself.
* **The account it will use**, the one you're signed in with.
* **Permissions**, set to **Full access** by default. Choose **Read only** or **Custom** to allow less. See [API keys and permissions](https://docs.avastudio.com/api-and-mcp/api-keys.md#permissions) for what each one allows.
* **A monthly credit budget**, 1,000 credits by default. Change it, or clear it for no limit.

Click **Allow** to connect, or **Deny** to cancel.

#### Manage connected apps

**Settings > Developers > Connected apps** lists every app you allowed, with its permissions, when it was connected and last used, and what it spent this month.

* **Change the budget** at any time; it applies within seconds.
* **Revoke** disconnects the app: it can't make any more calls until you connect it again.

Connecting the same app again adds a new connection with the permissions and budget you choose then. The old one stays listed until you revoke it.

Credits a connected app spends come from your account's balance, exactly like a key's. A connection's monthly budget limits the work it can start; it does not grant additional credits.

#### For app developers

Ava follows the [MCP authorization spec](https://modelcontextprotocol.io/specification/latest/basic/authorization) (OAuth 2.1), so MCP clients that support it connect without extra setup.

|                               |                                                                                                                                                                                                                                                           |
| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Resource (MCP server)         | `https://mcp.avastudio.com/mcp`                                                                                                                                                                                                                           |
| Protected resource metadata   | `https://mcp.avastudio.com/.well-known/oauth-protected-resource`                                                                                                                                                                                          |
| Authorization server metadata | `https://mcp.avastudio.com/.well-known/oauth-authorization-server`                                                                                                                                                                                        |
| Client registration           | Dynamic Client Registration (`POST /oauth/register`) or a Client ID Metadata Document (an https `client_id`)                                                                                                                                              |
| Grant                         | Authorization code with PKCE (`S256` only), plus refresh tokens                                                                                                                                                                                           |
| Redirect URIs                 | Exact match; `https://`, loopback `http://127.0.0.1`, `http://localhost` or `http://[::1]` (any port), or an app scheme                                                                                                                                   |
| Scopes                        | The permission ids: `account:read`, `brands:read`, `brands:write`, `research`, `ads:read`, `ads:write`, `drafts:read`, `drafts:write`, `campaigns:read`, `campaigns:write`, `production`, `agent`. Omit `scope` to request all; the user can grant fewer. |
| Tokens                        | Access tokens last 1 hour. Refresh tokens last 60 days and rotate on every use; reusing an old one disconnects the app.                                                                                                                                   |
| Revocation                    | `POST /oauth/revoke`                                                                                                                                                                                                                                      |

An unauthenticated request to `/mcp` answers `401` with a `WWW-Authenticate` header that points to the protected resource metadata, which is how clients discover the sign-in. Send the access token as `Authorization: Bearer <token>`.
