Step 1
Open your AI client's connector settings
In Codex, Claude, or another MCP-compatible client, open the place where remote MCP servers or connectors are managed.
AI agent setup
Use the official DoroSocial MCP server to let an AI agent inspect approved brand context, prepare social content, manage drafts, and check publishing workflows through a secure DoroSocial connection. Scheduling requires your approval by default; connecting an agent does not approve its posts.
Before you start
You need a DoroSocial account and an MCP-compatible AI client that supports remote Streamable HTTP servers.
Access model
DoroSocial asks you to sign in, choose brands, and approve the agent connection.
Best first prompt
Ask the agent to inspect brand context and suggest a content plan before creating drafts.
Step 1
In Codex, Claude, or another MCP-compatible client, open the place where remote MCP servers or connectors are managed.
Step 2
Select Streamable HTTP or the equivalent remote MCP server type. Studio is for local/custom development workflows, not the normal DoroSocial hosted connection.
Step 3
Name the connector DoroSocial, use https://doro.social/mcp, and leave bearer token, custom headers, and headers from environment variables empty for the standard OAuth flow.
Step 4
Click Authenticate. Sign in to DoroSocial if prompted, then review the agent connection request.
Step 5
Select only the brands the agent should work with, review the requested DoroSocial capabilities, and approve the connection.
Step 6
Start with a clear task such as: Review my DoroSocial content calendar and draft next week's posts for the selected brand.
By default, the agent creates a proposal marked Needs approval. A proposed post is not scheduled and will not publish until approval succeeds. Approving the agent connection only grants access to the selected brands and capabilities.
Tell the agent which brand, channel, account, date, time, and timezone you want. For example: “Prepare this carousel for Brightline Kitchen’s Instagram account @brightlinekitchen on October 6, 2026 at 10 AM America/Los_Angeles.” The agent is instructed to ask when the destination or timing is ambiguous, and to reuse choices you have already made.
To review several proposals together, select their checkboxes, inspect the selected accounts and times, then use the selected-post approval button. You can approve up to 50 per batch. If some fail, check each result: successful items are scheduled while failed items still need attention.
If a proposed time has passed, approval is disabled. Choose a future time first. Pending calendar proposals do not expire after 24 hours. If content or account details changed since your review, reload and inspect the latest version before approving again.
For scheduling without an agent, see Schedule your first post.
Keep manual review if you want to inspect every proposal. If you want an agent to schedule drafts without individual approval, enable that permission yourself in DoroSocial. Saying “approve everything” in chat does not change this permission, and the agent cannot enable it through MCP.
Posts scheduled this way can publish at their scheduled times without another approval. The permission applies only to that OAuth connection and brand. Other agents and brands retain their own settings.
Existing proposals stay pending when you enable the setting. Approve them in Schedule or ask the agent to schedule the specific drafts after enabling permission; switching the setting on does not process a backlog.
Automatic scheduling covers future scheduling of drafts. It does not grant permission to publish now, retry a failed publish, or edit already-scheduled content. Account access, plan limits, platform rules, and validation still apply.
To turn it off, return to the same agent and brand and click Require my approval. Existing schedules stay unchanged; turning it off does not cancel posts already scheduled.
In review mode, it should say the post is proposed and awaiting approval, name the brand and destination accounts, give the exact time and timezone, and provide a clickable Schedule link. In automatic mode, it should say scheduled only after DoroSocial confirms success. Saved drafts and content plans are not schedules, and a queued publish is not yet a confirmed publication.
The MCP calendar tool currently excludes pending proposals. Use the browser Schedule page to review them; the agent can check a proposal when it has its approval ID. If a proposal seems missing, check the selected brand, date, and filters.
This setting is for OAuth agent connections with scheduling access. If the connection lacks that access, reconnect with scheduling permission. API-token MCP connections do not have this automatic-scheduling setting.
No. Your AI client may ask whether it can call a tool. DoroSocial separately enforces its scheduling permission and post approval. The MCP supplies guidance and links, but the AI client controls its wording.
Open DoroSocial Settings, go to Agent connections, and revoke the connection you no longer want to use. You can reconnect later and choose a different brand set.
The AI agent workflow page explains the user-facing value: connect an AI agent to DoroSocial so it can help plan, draft, review, and manage social content.