Chat33

io.chat33Published by chat33.ioOfficial publisherv1.0.0Updated Oct 29, 2026

Publish to 8 social networks, answer Instagram and Facebook DMs, build comment-to-DM flows.

Overview

AI-generated overview

Hosted Chat33 server that lets an assistant publish and schedule social posts, reply to DMs and comments, and build comment-to-DM automations.

What you can do
  • Publish and manage posts: create, validate, list, read, delete and log posts, request approvals and add notes
  • Upload media and generate upload URLs
  • Check account identity and connected accounts
  • Read analytics for published posts
  • List, inspect, create and enable or pause comment-to-DM automations
  • Read inbox conversations and post comments, and send replies
When to use it
Useful when you want an assistant to draft, schedule and publish content across Instagram, Facebook, Threads, TikTok, YouTube, X, LinkedIn and Bluesky, or to triage and answer Instagram and Facebook DMs and comments from the same chat.
Requirements
A remote hosted endpoint; nothing to install. Sign-in uses OAuth 2.1 in the browser, or an API key created in Chat33 settings sent as an x-api-key header or Bearer token. A Chat33 account and plan are required, and connected social accounts count against plan limits.
Before you install
The server can publish, schedule and delete posts and send messages to real people, so review drafts before approving. Replies to DMs and comments are meant to ask for your approval first, and new automations start as drafts. An API key grants access to your accounts; keep it secret. Platform limits apply, such as 24-hour DM reply windows and one private reply per comment.

Installation

In SourceWeft

  1. Open Chat33 in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/io.chat33%2Fchat33/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "chat33": {
      "type": "http",
      "url": "https://chat33.io/api/mcp/mcp"
    }
  }
}

README

[Chat33]

Chat33 MCP Server

Social media MCP server for AI agents. Connect Claude, ChatGPT, Cursor, VS Code or any MCP client to Chat33 and let your agent publish and schedule posts to Instagram, Facebook, Threads, TikTok, YouTube, X, LinkedIn and Bluesky, answer Instagram and Facebook DMs and comments, and build comment-to-DM automations.

This is a hosted (remote) server. There is nothing to install or run: point your client at the URL below and sign in.

https://chat33.io/api/mcp/mcp
  • Transport: Streamable HTTP
  • Auth: OAuth 2.1 sign-in in the browser (dynamic client registration), or an API key header
  • Docs: chat33.io/mcp

Connect your client

Prefer OAuth wherever your client supports it: add the server, choose Authenticate (or the client's login button) and approve in the browser tab that opens. No API key needed.

Claude Code

bash
claude mcp add --transport http --scope user chat33 https://chat33.io/api/mcp/mcp

Then run /mcp, choose chat33 → Authenticate and approve in the browser.

Claude (claude.ai and Claude Desktop)

Settings → Connectors → Add custom connector → URL https://chat33.io/api/mcp/mcp → Connect, then approve in the browser.

ChatGPT

Settings → Apps / Connectors → Advanced → turn on Developer mode → Create: name Chat33, URL https://chat33.io/api/mcp/mcp, authentication OAuth. Sign in to Chat33 and click Allow.

Cursor

~/.cursor/mcp.json:

json
{  "mcpServers": {    "chat33": {      "url": "https://chat33.io/api/mcp/mcp"    }  }}

VS Code

.vscode/mcp.json in your workspace (or the user MCP config):

json
{  "servers": {    "chat33": {      "type": "http",      "url": "https://chat33.io/api/mcp/mcp"    }  }}

Windsurf

~/.codeium/windsurf/mcp_config.json:

json
{  "mcpServers": {    "chat33": {      "serverUrl": "https://chat33.io/api/mcp/mcp"    }  }}

Codex

bash
codex mcp add chat33 --url https://chat33.io/api/mcp/mcpcodex mcp login chat33

Gemini CLI

bash
gemini extensions install https://github.com/chat33-io/chat33-mcp

Clients without OAuth (API key)

Create a key in Chat33 → Settings → API Keys and send it as an x-api-key header (or Authorization: Bearer):

json
{  "mcpServers": {    "chat33": {      "url": "https://chat33.io/api/mcp/mcp",      "headers": { "x-api-key": "sk_live_..." }    }  }}

Tools

GroupTools
Accountlist_accounts, whoami
Publishingcreate_post, validate_post, list_posts, get_post, delete_post, get_post_logs, request_approval, list_approvals, add_post_note
Mediaupload_media, create_upload_url
Analyticsget_analytics
Automationslist_flows, get_flow, create_flow, set_flow_status
Inboxlist_conversations, get_messages, reply_to_conversation
Commentslist_post_comments, reply_to_comment

Tools that message a real person (reply_to_conversation, reply_to_comment) tell the agent to ask for your approval first. New automations are created as drafts.

Try asking

  • "Schedule this photo to Instagram and Threads for tomorrow at 9am."
  • "Which DMs are waiting for a reply? Draft answers for me to approve."
  • "Build a flow that DMs the guide link to anyone who comments GUIDE on my last reel."
  • "How did my posts do this week?"

Limits

  • Your Chat33 plan's limits on posts and connected accounts apply.
  • Instagram and Facebook DM replies only work within 24 hours of the contact's last message.
  • Meta allows one private reply per comment, within 7 days.
  • LinkedIn: personal profiles only. Bluesky: publishing only (no DMs or comments).

Links

License

MIT. This repository describes the hosted server; the server itself runs at chat33.io.

Source: README.md at commit e9c3222

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

85% 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts