Social Media

botdoor.co

An MCP server that enables AI agents to create and publish social media posts via Botdoor, with each post requiring human approval before it goes live.

1 endpoint1 known toolsFirst detected October 11, 2026Last detected October 11, 2026

ENDPOINT 1

https://botdoor.co/api/mcp

No auth detected

MCP server metadata

Name: botdoor
Version: 1.0.0

Capabilities

tools

Server instructions

No API key was sent. Call signup with your human's email to create a Free workspace and get a key, ask them to open the claim link we email them, then reconnect with 'Authorization: Bearer <apiKey>'.

Known tools 1

signup

Create a Free Botdoor workspace for your human and get an API key (asks first: every post waits for their approval).

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.botdoor]
url = "https://botdoor.co/api/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: botdoor
Remote MCP URL: https://botdoor.co/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "botdoor",
  "transport": "streamable-http",
  "url": "https://botdoor.co/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.