MCP Server Support

Connect Repliz to your AI assistant using the official Repliz MCP server. It lets any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, ChatGPT, and others) manage your Repliz workspace in plain language: list and reply to comments, schedule posts, handle DMs, browse content and stats, research Threads, and more.

What is MCP?

The Model Context Protocol is an open standard that lets AI assistants call external tools. Your client connects to the Repliz server and gains a set of tools, one per Repliz action. You can then say things like "reply to the latest pending comment" or "schedule this image to Instagram tomorrow at 9am", and the assistant calls the right Repliz API for you.

Two ways to run

Mode	Transport	Best for	Clients
Local	stdio (a subprocess on your machine)	yourself and per-user setups	Claude Desktop, Claude Code, Cursor, VS Code, Gemini CLI
Remote	Streamable HTTP (a hosted HTTPS endpoint)	serving many users over the web	Claude.ai connectors, ChatGPT developer mode, API integrations

WARNING

Web chat apps (Claude.ai, ChatGPT, the Gemini app) only accept remote servers, since they cannot launch a local process. Use Local mode for desktop and developer tools, and Remote mode to serve many users through the web apps.

Prerequisites

Node.js 18 or newer (the server uses the built-in fetch).
A Repliz API Access Key and Secret Key from your workspace.

The Repliz Public API uses HTTP Basic Auth: the Access Key is the username and the Secret Key is the password. To get your keys:

Log in to your Repliz Dashboard.
Navigate to Settings > API.
Copy your Access Key and Secret Key. If you do not have keys yet, click Generate New Keys.

Installation

From source

bash

git clone https://github.com/azickri/repliz-mcp.git
cd repliz-mcp
npm install
npm run build

This produces dist/index.js, the file you point your client at.

Via npx

Once the package is published, you can run it without cloning:

bash

npx repliz-mcp

Local mode (stdio)

Run the server as a subprocess from a desktop or developer client. Credentials are passed through environment variables:

Variable	Required	Default	Description
`REPLIZ_ACCESS_KEY`	Yes	—	Your API Access Key (Basic Auth username)
`REPLIZ_SECRET_KEY`	Yes	—	Your API Secret Key (Basic Auth password)
`REPLIZ_BASE_URL`	No	`https://api.repliz.com`	API base URL; override only if needed

Claude Desktop

Edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):

json

{
  "mcpServers": {
    "repliz": {
      "command": "node",
      "args": ["/absolute/path/to/repliz-mcp/dist/index.js"],
      "env": {
        "REPLIZ_ACCESS_KEY": "your_access_key",
        "REPLIZ_SECRET_KEY": "your_secret_key"
      }
    }
  }
}

Restart Claude Desktop, and the Repliz tools appear in the tools menu.

Claude Code (CLI)

bash

claude mcp add repliz \
  --env REPLIZ_ACCESS_KEY=your_access_key \
  --env REPLIZ_SECRET_KEY=your_secret_key \
  -- node /absolute/path/to/repliz-mcp/dist/index.js

Cursor

In .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

json

{
  "mcpServers": {
    "repliz": {
      "command": "node",
      "args": ["/absolute/path/to/repliz-mcp/dist/index.js"],
      "env": {
        "REPLIZ_ACCESS_KEY": "your_access_key",
        "REPLIZ_SECRET_KEY": "your_secret_key"
      }
    }
  }
}

TIP

Any MCP client works. Point its command and args at node dist/index.js (or npx repliz-mcp once published) and pass the two environment variables.

Remote mode (HTTP)

Run a hosted server that many users connect to over HTTPS. Each user supplies their own Repliz credentials per request, so one deployment serves everyone.

Run it

bash

npm run build
npm run start:http

Variable	Required	Default	Description
`REPLIZ_BASE_URL`	No	`https://api.repliz.com`	API base URL shared by all users
`PORT`	No	`3000`	Port to listen on
`REPLIZ_ACCESS_KEY` / `REPLIZ_SECRET_KEY`	No	—	Optional fallback credentials for single-tenant hosting. Leave unset for multi-user.

The MCP endpoint is https://<your-host>/mcp, with a GET /health check. Serve it over HTTPS in production by putting it behind a reverse proxy or platform TLS (Railway, Fly.io, Render, Cloudflare, Nginx).

Per-user authentication

Each user passes their Repliz credentials on the request, in either form:

http

Authorization: Basic base64(accessKey:secretKey)

http

X-Repliz-Access-Key: <accessKey>
X-Repliz-Secret-Key: <secretKey>

Credentials are captured when the MCP session starts and bound to that session only, so users are isolated from one another. Requests with no valid credentials are rejected with 401.

Connect from the web apps

Claude.ai (Pro, Max, Team, Enterprise): go to Settings > Connectors > Add custom connector and enter https://<your-host>/mcp. On Team and Enterprise, an owner adds it under Organization settings > Connectors first.
ChatGPT (Plus, Pro, Business, Enterprise): go to Settings > Connectors > Advanced and enable Developer mode, then add a connector pointing at https://<your-host>/mcp.
Anthropic API: pass the server under mcp_servers with type: "url", url: "https://<your-host>/mcp", and your Repliz Basic token in the connector's authorization_token.

Available Tools

The server exposes 33 tools across the Repliz Public API, grouped by domain:

Accounts `<Badge type="info" text="Standard+" />`

Manage the social accounts connected to your workspace.

repliz_list_accounts, repliz_count_accounts, repliz_get_account, repliz_delete_account

Comments `<Badge type="info" text="Standard+" />`

Retrieve and moderate comments collected in your inbox.

repliz_list_comments, repliz_get_comment, repliz_reply_comment, repliz_update_comment_status

Chat `<Badge type="warning" text="Gold+" />`

Manage direct message conversations.

repliz_list_chats, repliz_get_chat, repliz_list_messages, repliz_send_message, repliz_read_chat

Content `<Badge type="warning" text="Gold+" />`

Work with published posts, reels, and stories, plus their comments and stats.

repliz_list_content, repliz_get_content, repliz_get_content_comments, repliz_create_content_comment, repliz_get_content_statistic, repliz_message_content_comment, repliz_delete_content_comment

Schedule `<Badge type="danger" text="Premium+" />`

Create, update, and queue scheduled posts across platforms.

repliz_list_schedules, repliz_get_schedule, repliz_create_schedule, repliz_update_schedule, repliz_retry_schedule, repliz_delete_schedule, repliz_delete_schedules

Research (Threads)

Search Threads content, user content, and user profiles.

repliz_search_threads_content, repliz_search_threads_user_content, repliz_search_threads_user

Add-ons `<Badge type="danger" text="Premium+" />`

Helper utilities for building posts.

repliz_tiktok_trending_music, repliz_shopee_products, repliz_link_metadata

Plan requirements

Tool availability follows your Repliz subscription tier. Accounts and Comments work on Standard, Chat and Content require Gold, and Schedule and Add-ons require Premium.

OAuth connect flows

Account connection flows (authorize, exchange, connect) are not included as tools. They are interactive browser steps that are better done from the Repliz web app. See Integration Account for those.

Usage examples

Once connected, ask your assistant things like:

"List my connected accounts."
"Show pending comments and reply to the newest one with a thank-you."
"Schedule this video to Instagram on 2026-06-20 at 09:00 UTC."
"What are the trending POP songs on TikTok in Indonesia this week?"
"Get engagement stats for my latest post on account <id>."

Review write actions

Tools that reply, schedule, send, or delete take real action on your accounts. Review what the assistant proposes before confirming, and be careful with untrusted content the model reads, since it can carry prompt-injection attempts.

Delete Comment

Reply Comment

Like Comment

DM Comment

Reply DM

Delete Comment

Reply Comment

Like Comment

DM Comment

MCP Server Support

Two ways to run

Prerequisites

Installation

From source

Via npx

Local mode (stdio)

Claude Desktop

Claude Code (CLI)

Cursor

Remote mode (HTTP)

Run it

Per-user authentication

Connect from the web apps

Available Tools

Accounts `<Badge type="info" text="Standard+" />`

Comments `<Badge type="info" text="Standard+" />`

Chat `<Badge type="warning" text="Gold+" />`

Content `<Badge type="warning" text="Gold+" />`

Schedule `<Badge type="danger" text="Premium+" />`

Research (Threads)

Add-ons `<Badge type="danger" text="Premium+" />`

Usage examples

MCP Server Support ​

Two ways to run ​

Prerequisites ​

Installation ​

From source ​

Via npx ​

Local mode (stdio) ​

Claude Desktop ​

Claude Code (CLI) ​

Cursor ​

Remote mode (HTTP) ​

Run it ​

Per-user authentication ​

Connect from the web apps ​

Available Tools ​

Accounts <Badge type="info" text="Standard+" /> ​

Comments <Badge type="info" text="Standard+" /> ​

Chat <Badge type="warning" text="Gold+" /> ​

Content <Badge type="warning" text="Gold+" /> ​

Schedule <Badge type="danger" text="Premium+" /> ​

Research (Threads) ​

Add-ons <Badge type="danger" text="Premium+" /> ​

Usage examples ​

MCP Server Support

Two ways to run

Prerequisites

Installation

From source

Via npx

Local mode (stdio)

Claude Desktop

Claude Code (CLI)

Cursor

Remote mode (HTTP)

Run it

Per-user authentication

Connect from the web apps

Available Tools

Accounts `<Badge type="info" text="Standard+" />`

Comments `<Badge type="info" text="Standard+" />`

Chat `<Badge type="warning" text="Gold+" />`

Content `<Badge type="warning" text="Gold+" />`

Schedule `<Badge type="danger" text="Premium+" />`

Research (Threads)

Add-ons `<Badge type="danger" text="Premium+" />`

Usage examples