MCP workspaces and permissions
Choose the acting workspace and understand the permissions granted during connection.
Reepl asks you to authorize the AI client in your browser. Check the account shown before selecting Allow.
Connection permissions
| Permission | What it enables |
|---|---|
| Always included | Read supported Reepl content and use drafting tools. Draft-only access can still create or change content and use credits. |
| Act on your social accounts | Publish, schedule, comment, reply, and review approvals using supported tools. |
| Manage your account | Allows supported account-management tools when they are available. This does not add tools that the current server does not provide. |
If a tool requires a permission you did not grant, reconnect and approve that permission. The connection's permissions do not override your workspace role or a post's reviewer requirements.
Choose the workspace explicitly
Ask the client to call list_workspaces before working with a team or agency account. Most workspace-aware tools accept workspace_id for that call.
For example:
List my workspaces. Use the Acme workspace for this task, read its context and audience profiles, and show me its scheduled posts.
set_default_workspace changes which workspace MCP uses when you omit workspace_id. The web app keeps its currently open workspace until you switch it there as well. For a single task, passing workspace_id avoids changing your default.
Select the publishing account
Use channels_list to find the account's channel_id. Check its platform, owner, and enabled status before publishing. A workspace can contain your account, a teammate's account, and Company Pages on the same platform.
Credits and shared context
AI operations can spend the acting workspace's credits. Voice profile updates can affect shared workspace writing settings. Ask the client to show the intended changes before applying a shared setting update.
See MCP publishing for result statuses and approvals.