Mallary MCP supports OAuth 2.1 for apps and agents. Mallary API keys remain supported for scripts and existing integrations.
Mallary connectors for Claude, ChatGPT, Codex, and Cursor use OAuth. They never ask the user to create, paste, or reveal a Mallary API key.
Before using the Mallary MCP Server:
- Sign up at https://mallary.ai
- Connect your social media accounts in the Mallary dashboard
- Approve the access requested by your app, or get a Mallary API key for a manual setup
OAuth
OAuth-ready clients discover Mallary’s authorization server automatically from:
Mallary uses the authorization code flow with PKCE. The authorization server is:
Mallary asks the signed-in user to approve the app connection. First-party Mallary clients request all Mallary capabilities in one login, so the user does not choose scopes or sign in again for another capability. Mallary never gives the app the user’s password or connected social account tokens.
Claude can use a Client ID Metadata Document, while other clients can use Mallary’s dynamic client registration endpoint. Mallary keeps both methods available. Access tokens are short lived. Refresh tokens rotate, and revoked grants stop working.
Users can review and revoke OAuth access at https://mallary.ai/oauth-connections.
OAuth Scope Reference
These scopes remain part of the OAuth protocol for client compatibility. They are not choices shown by the Mallary CLI.
mallary.read: read posts, comments, analytics, profiles, platforms, settings, and webhooks
mallary.publish: upload media and create or schedule posts
mallary.engage: reply to comments
mallary.manage: change settings, profiles, webhooks, connections, and pending posts
For a manual API-key setup, send the key as a bearer token:
Identity Resolution
Identity is always resolved from the OAuth grant or API key owner. You do not separately pass a user ID when calling MCP tools.
Base URL
Mallary MCP is served from:
Endpoint
Use the MCP server at:
Last modified on August 10, 2026