Overview

API keys and OAuth

Create personal API keys, authorise an AI client over OAuth and revoke either one.

Open .md

The MCP server authenticates with a Bearer token. That token is either a personal API key or an OAuth access token issued after a browser approval, and both are managed on one page: Settings → Connected apps & API keys.

API keys

PropertyBehaviour
Formatgr_live_ followed by a random string
DisplayedOnce, when it is created
StoredOnly a hash, never the key itself
ExpiryNone; a key stays valid until it is revoked
LimitFive active keys per account
Name1–50 characters, for your own reference
RevocationImmediate, and not reversible

A key carries the full tool permissions of its account. It spends that account's credits, and it can only reach that account's projects and assets; passing someone else's project id does not widen it. A key whose account is a guest account, banned, or being deleted is refused with 401.

Each key shows when it was created and when it was last used, so a key that no longer appears in your clients can be revoked with confidence. Revoking a key leaves renders that were already submitted alone; it only stops new calls.

OAuth connections

Client apps that support the browser flow are listed under Connected apps, with the date they were connected and a disconnect action.

  1. The app asks GetRender for authorization.

  2. A browser opens GetRender, where you sign in and review what the app will be able to do: upload images, generate with your credits, and view your projects and balance. A guest session is asked to sign in with a full account first.

  3. Approving issues the app an access token, which it refreshes on its own.

Disconnecting deletes the stored authorization, and because the connection is checked on every call, the app loses access immediately. Only one thing has to be remembered about the order of operations: removing a connector inside the AI client does not tell GetRender anything. Disconnect here as well.

OAuth access is limited to clients whose metadata is published at claude.ai or chatgpt.com. Other clients, including Cursor, use an API key.

OAuth details for client developers

ItemValue
Protected resourcehttps://getrender.ai/mcp/app
Resource metadatahttps://getrender.ai/.well-known/oauth-protected-resource/mcp/app
Authorization server (issuer)https://getrender.ai/api/auth, metadata at /.well-known/oauth-authorization-server/api/auth
Required scopemcp:render
Other scopes offeredopenid, profile, offline_access
Grant typesauthorization_code and refresh_token
Client identificationClient ID Metadata Documents, from claude.ai and chatgpt.com only
Dynamic client registrationDisabled
Access token lifetimeOne hour
Refresh tokensRotated on use; the previous token is accepted for 30 seconds after a refresh, so two parallel refreshes do not lock the client out
Sender-constrained tokensNot supported; a token carrying a DPoP cnf claim is refused

A 401 from the server carries WWW-Authenticate: Bearer resource_metadata="…", scope="mcp:render", which is how a client discovers where to authorize. A token without the mcp:render scope is refused even when it is otherwise valid.

Keeping a key private

  • Keep it in the client's own credential store rather than in a shared repository or a screenshot.

  • Do not paste a key into an AI conversation. An agent connection needs the key in the client's configuration, not in a message.

  • A key that was pasted, committed or shared should be revoked, and a replacement created.

  • Rotate a key by creating a new one, pointing the client at it, then revoking the old one. Two keys can be active at once, so the client is never left without a working key.

When authentication fails

SymptomCauseAction
401 before any tool runsMissing, malformed or revoked credentialRecreate the key or reconnect the app
UNAUTHORIZED from a toolCredential belongs to an account that cannot renderSign in with a full account rather than a guest
FORBIDDENThe account does not have access to what was requestedCheck the project or asset belongs to this account
OAuth flow ends in an errorThe authorization request expired or was started elsewhereStart the connection again from the client
A previously working key stopsThe key was revokedCreate a replacement

Reading documentation — this page included, and the Markdown endpoint — needs no key at all.

Client configuration · MCP tools · Errors and limits