Use API keys and MCP access

Create API keys for supported integrations and connect MCP-compatible clients with the right scope and approval flow.

Where API keys live

Open Settings > API Keys to create, copy, revoke, or review keys and connected apps. Not every key is valid for every feature, so pay attention to the scope shown with each key.

API keys and MCP access are Premium-tier features. If your account is inactive or on Standard, Dolla keeps existing data but blocks API-key creation and management until the workspace is upgraded. MCP access is read-only, and Dolla rechecks the Premium entitlement whenever an OAuth grant or manual MCP token is used.

Which scope to choose

The self-service API key scopes are read, transactions, and write. For MCP clients, read is required. Use read,transactions only if you also want the same key to work for transaction-aware automation elsewhere, and keep read,write for broader integrations that truly need write access. Keys with only transactions or only write do not authorize MCP access.

Platform admins also see blog:publish, which creates a blog automation key through a separate privileged endpoint. Use that scope only for the blog publishing script. Non-admin accounts do not see or create internal publishing keys.

Connect Claude or ChatGPT

Use the built-in OAuth flow when the client supports it. Open the MCP connector setup in your client, point it at your Dolla MCP endpoint, and sign in through the browser approval page that opens. OAuth approval is the consent boundary: the external provider you connect can read the financial data Dolla returns to that client. If the client asks for manual fields, leave the OAuth client ID and secret blank unless it explicitly requires them.

Manual token clients

If a client cannot complete OAuth, create a key in Settings > API Keys and paste the Bearer header into the client:

Authorization: Bearer pk_live_...

That path is best for tools like MCP Inspector or IDE plugins. Manual token clients must use a key with the read scope. This path is not required for Claude or ChatGPT when OAuth is available.

If access is not working

Check that the key is active, not expired, and has the read scope. MCP also depends on the backend being deployed with the required environment settings, the account still having Premium MCP access, and the user approving the connection in the browser flow. You can revoke connected OAuth apps from Settings > API Keys.

If key creation or app revocation fails, the settings page now keeps the relevant form or list visible and shows the server error so you can retry. Load failures for the API-key and connected-app lists show a retry action before you make changes.