Botdoor

co.botdoorPublished by botdoor.coOfficial publisherv1.0.0Updated Oct 24, 2026

Let AI agents post to social media with human approval: schedule, first comments, threads.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Lets an AI assistant create and schedule social media posts, threads and first comments, with every post held for a human's approval.

What you can do
Botdoor is a remote MCP endpoint for social media posting. With an API key, an assistant can create, schedule and reject posts, including threads and first comments, while approval stays with a signed-in person. A signup tool can create a free workspace and return an API key plus next steps; without a key, only that signup tool is available.
When to use it
Use it when you want an assistant to draft and queue social media content but keep a human in the loop before anything is published. It is not needed if you only want read-only social analytics or have no Botdoor workspace.
Requirements
A remote streamable HTTP endpoint at botdoor.co. An API key from the provider's key page, sent as an Authorization header in the form Bearer bd_...; alternatively the signup tool can create a free workspace and issue a key. No local runtime or packages are needed.
Before you install
The Authorization header carries a secret API key; keep it private. Keys can create, schedule and reject posts, so an assistant can queue content on your behalf, though only a signed-in person can approve. Signup emails a claim link to the person's address, and the returned API key is shown only once.

Installation

In SourceWeft

  1. Open Botdoor in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/co.botdoor%2Fbotdoor/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "botdoor": {
      "type": "http",
      "url": "https://botdoor.co/api/mcp"
    }
  }
}

Tools

1

signup

Sign up for Botdoor

Create a Free Botdoor workspace for your human and get an API key (asks first: every post waits for their approval). No account needed. Returns apiKey (shown once) and next steps. Botdoor emails your human a claim link; they set a password there and connect an account. If the email already has a workspace you get no key (202): your human signs in and creates one for you. Then reconnect to this MCP server with 'Authorization: Bearer <apiKey>' to get the posting tools.

ParametersemailrequiredlocaleagentNameworkspaceName

Version history

1
  1. v1.0.0LatestOct 10, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.