Doro Social
Login
Developer docs

Model Context Protocol

Connect AI agents to DoroSocial with MCP.

The DoroSocial MCP server lets MCP-compatible agents such as Codex and Claude work directly with your approved DoroSocial brands, content, drafts, schedules, and publishing status without asking users to paste API tokens into chat.

See the AI agent workflowTechnical setupUser setup guide

Quickstart

Connect in four steps

1

Choose a remote MCP connection

In your AI client, choose Streamable HTTP or the equivalent remote MCP server option.

2

Use the DoroSocial MCP URL

Enter https://doro.social/mcp. Leave bearer token and custom headers empty unless your organization has a separate gateway policy.

3

Authenticate with DoroSocial

Click Authenticate. DoroSocial opens a secure sign-in and consent screen where you choose which brands the agent may access.

4

Review and approve access

Approve the requested DoroSocial agent capabilities only if the brand selection and account are correct.

What agents can do

MCP is the agent-friendly interface for DoroSocial. It exposes workflows as tools with useful names and structured inputs, so an agent can plan and manage social work without reverse-engineering raw API endpoints.

  • Read workspace, brand, connected-account, and plan-limit context.
  • Find existing content items, platform drafts, transcripts, media status, publishing state, and schedule context.
  • Create or update content records and platform-specific draft posts when the consented account has write access.
  • Prepare publishing and scheduling workflows while preserving DoroSocial approval, platform, and account rules.
  • Report job, validation, and publishing status so the agent can explain what happened instead of guessing.

Discovery URLs

Most users only need the MCP server URL. MCP clients use OAuth discovery metadata behind the scenes to learn where to authenticate and how to request consent.

MCP endpoint

https://doro.social/mcp

Protected resource metadata

https://doro.social/.well-known/oauth-protected-resource/mcp

Authorization server metadata

https://doro.social/.well-known/oauth-authorization-server/oauth

MCP vs Public API

Use MCP for AI agents

MCP is best when a person connects Codex, Claude, or another agent and wants it to inspect context, draft content, and operate through consented DoroSocial tools.

Use the API for software integrations

The Public API is best for backend services, scripts, SDKs, and deterministic app-to-app integrations that should authenticate with scoped API tokens.

View API docs

Security and consent

  • MCP access uses OAuth instead of copying API tokens into prompts.
  • Users choose brands during consent and can revoke agent connections from DoroSocial settings.
  • The MCP server does not expose connected social-platform provider tokens to the AI client.
  • Publishing still follows DoroSocial account permissions, plan limits, platform rules, and validation.

Troubleshooting

The client asks for a bearer token

Leave it empty for the normal DoroSocial MCP flow. Authentication happens through the OAuth screen after you click Authenticate.

The client cannot connect

Confirm the URL is exactly https://doro.social/mcp, then retry authentication. If you are testing a local development server, use the matching local URL and make sure that server is running.

The agent cannot see a brand

Reconnect and select the brand during consent, or review the existing connection from DoroSocial settings.