Authentication
OAuth connection, workspace binding, and what each scope allows.
DunSocial MCP uses OAuth. You do not paste a long-lived secret into ChatGPT or Claude. You add the MCP URL; the client opens DunSocial so you can sign in, pick a workspace, and approve access.
The URL
https://api.dunsocial.com/api/mcpFind the same URL under Settings → MCP. Manage or revoke connections there too.
What happens when you connect
- Your assistant calls the MCP endpoint.
- DunSocial asks you to sign in (if needed).
- You choose a workspace. The connection stays bound to that workspace.
- You approve scopes (what the assistant may do).
- The client receives short-lived tokens and refreshes them for you.
Scopes
| Scope | What it allows |
|---|---|
workspace:read |
List and view posts, drafts, media, memories, accounts, and workspace details |
drafts:write |
Create and edit drafts (not publish) |
posts:schedule |
Schedule, reschedule, and cancel posts |
posts:publish |
Publish immediately |
content:delete |
Delete posts, drafts, memories, or media |
memory:write |
Create collections and save or update memories |
media:write |
Upload to the gallery |
offline_access |
Stay connected with refresh tokens |
Publish tools need posts:publish. If consent only showed “view workspace content,” disconnect in Settings → MCP and connect again so the full set is granted.
Workspace binding
OAuth connections are locked to the workspace you picked at consent. Asking the assistant to use a different workspace will fail until you reconnect for that workspace.
Good to know
- Tokens are never put in the URL query string for new setups.
- Prefer MCP for remote chat hosts. Prefer the CLI and personal access tokens for CI.
- Revoke a connection anytime from Settings → MCP.