AI apps (MCP)
Authentication
Sign in with OAuth and choose the permissions, or use an API key. Either way the app only gets what you allow, and you can take it back anytime.
- OAuth 2.1 + PKCE
- Access 1 hour, renewed by the app
- Revoke in Connected apps
Which one to use
OAuth
RecommendedFor Claude (claude.ai and desktop) and any client that supports it. You sign in, pick the permissions and click Authorize. No key to copy or store.
API key
DevelopersFor Claude Code, Cursor, VS Code and scripts. Send the key as Authorization: Bearer. The key scopes decide which tools show up.
OAuth
Your app does all of this by itself. You only see the Sendcorex window.
- 1
The app calls the server without a token and gets 401 with a link to the Sendcorex authorization metadata.
- 2
The app registers itself (dynamic client registration) and opens a Sendcorex window.
- 3
You sign in to the dashboard if needed, choose the permissions (or the mailbox) and click Authorize.
- 4
The app gets an access token (1 hour) and a refresh token (30 days, renewed on every use) and starts calling tools.
Members of an organization can only grant the permissions they have themselves.
Permissions
On the Authorize screen each area is No access, Read or Full. The same scopes work on API keys. Account, billing, team and API key management are never available to AI apps.
| Area | Read | Full adds |
|---|---|---|
| Domains | domain:read | domain:create, domain:delete |
| Senders | sender:read | sender:create, sender:update, sender:delete |
| Templates | template:read | template:create, template:update, template:delete |
| Contacts | contact:read | contact:create, contact:update, contact:delete |
| Logs | logs:read | — |
| Bounces & complaints | feedback:read | — |
| Counters | counters:read | — |
| Tracking preferences | privacy:read | privacy:write |
| Email validation | — | tools:validate |
| Send email | — | email:send |
API key
Create a key in the dashboard with only the scopes the app needs, and send it on every request.
POST https://g.sendcorex.com/mcp/account
Authorization: Bearer SENDCOREX_API_KEY
Content-Type: application/json- The tool list follows the key. A key with only
logs:readsees only the log tools. - Allowed IPs still apply. Cloud apps call from their own servers, so a key locked to your IPs will be refused there. Use OAuth for those.
Mailbox access
The mailbox server works on one mailbox at a time. With OAuth you pick the mailbox on the Authorize screen (search helps when you have many). From code, the mailbox token from the Receive Emails API works too. General API keys never open a mailbox.
Read-only access
When you connect a mailbox, you choose Full access or Read only. Read only is the default for apps and the safest choice for AI assistants that only need to read your email.
A token created as Read only, or an app authorized as Read only, can only read the mailbox.
Any write command returns READ_ONLY_ACCESS (HTTP 403 in the attachment upload route).
In the MCP, the write tools are not listed: the app only sees the tools it can use.
Allowed commands
whoamilist_foldersget_counterslist_threadsget_threadlist_messagesget_messagessearchget_attachmentget_raw_sourcelist_draftsget_draftget_trackinglist_activityactivity_countslist_contactscount_contactsget_mailbox_contactlist_segmentsget_audiencecheck_recipientsget_delivery_statusget_contact_eventsget_trustlist_trustlist_junkblocked_junk_countlist_top_sendersget_filter_modelist_signaturesget_conversationlist_assigneeslist_conversationslist_conversation_noteslist_rulesget_rulerule_optionstest_rulelist_templatesget_templatelist_labelsget_contactlist_followupsget_unsubscribe_optionslist_unsubscribedRevoke access
Connected apps in the dashboard lists every app you authorized, what it can access and when it was last used. Revoke and the app loses access within a minute. To use it again, connect and authorize once more.
Open Connected apps