Delulu

Give an agent structured publishing tools

Social media MCP server

Connect compatible agents to Delulu's hosted MCP server with OAuth, or run the local server with a workspace API key for structured social publishing tools.

How it works

From setup to a finished workflow

  1. 1

    Connect the server

    Add the hosted MCP URL to a browser-capable client, or run the local package over stdio or SSE.

  2. 2

    Authorize a workspace

    Sign in, select an eligible workspace and scopes, approve access, then confirm setup status.

  3. 3

    Call structured tools

    List accounts, import media, create or update posts, publish prepared work, and inspect results.

Capabilities

What you can do

  • Hosted remote MCP with browser OAuth authorization
  • Local stdio and SSE server modes for workspace API keys
  • Workspace discovery and setup-status tools
  • Connected-account listing, inspection, and authorization links
  • Public-URL media import
  • Post list, create, update, delete, and publish-now tools
  • Usage and subscription inspection

Best fit

Who it is for

  • Teams operating publishing through an MCP-compatible client
  • Developers adding social tools to an agent workflow
  • Self-hosters who want a local MCP transport with a scoped API key

Examples

  • Ask an authorized agent to prepare a draft for selected connection IDs and return the post state.
  • Import campaign media from a public HTTPS URL before creating the post.
  • Use setup status to identify a missing account connection before attempting to publish.

Structured tools do not remove human control

Hosted MCP opens Delulu sign-in and authorization in the browser. The user selects the workspace and scopes before the client receives app-issued access tokens.

Every tool call reuses the REST domain rules for membership, role, scope, quota, payer eligibility, and review. The client must inspect returned post and target states because a successful tool call can still result in a draft, schedule, review, or in-progress publication.

Requirements and limits

What to know before you start

  • Hosted use requires a browser-capable MCP client that stores and refreshes its own app-issued tokens.
  • Local stdio or SSE use requires a workspace-bound Delulu API key.
  • Remote MCP cannot read arbitrary local file paths; media must come from a public HTTPS URL or an existing media ID.

Questions

What people ask about social media mcp server

Can I use Delulu MCP without pasting a token into the client?

Yes. The hosted server uses OAuth with browser authorization and PKCE. The MCP client stores and refreshes the app-issued tokens after approval.

What tools does the server provide?

The current server covers workspace setup, checkout, accounts, media import, post listing and management, immediate publishing, usage, and subscription status.

Can the hosted server upload a file from my laptop?

No. Remote MCP cannot receive arbitrary local paths. Import a public HTTPS or supported public share URL, or upload locally with the CLI and pass the completed media ID.

Does MCP ignore review requirements?

No. Live roles, scopes, workspace binding, quotas, and review rules apply to every tool call just as they do in the app and REST API.

How do I choose among several workspaces?

Pass a workspace ID or configure the local default. If several workspaces are eligible and no explicit choice exists, the operation fails instead of guessing.

Related features

Works with these connected channels

Availability still depends on the post format, account type, and permissions described above.

Put social media mcp server into your real workflow

Connect an account, create the first piece of work, and see how Delulu fits your publishing process.

Create your account