MMCPMarkets
RI

respond-io/mcp-server

Developer tools

Эта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал

6 stars 16 forks Качество 73 Тренд 22MIT
Repository Install

A lightweight, high-performance MCP server connecting AI, tools, and automation through Stdio and HTTP streamable transports — enabling real-time context flow, smart orchestration, and seamless...

Обзор

A Model Context Protocol (MCP) server implementation for the Respond.io API, enabling seamless integration with AI assistants, automation tools, and Claude Desktop. - ✅ Get, create, update, and delete contacts - ✅ Create or update contact (upsert by identifier) - ✅ Merge two contacts (primary + secondary) - ✅ List contacts with filters and search - ✅ Add and remove contact tags - ✅ Update contact lifecycle stages - ✅ List contact channels (e.g. WhatsApp, Facebook) - ✅ Send messages (text, attachments, WhatsApp templates, emails) - ✅ Retrieve message details and status - ✅ List messages for a contact (with pagination) - ✅ Support for multiple channel types - ✅ Assign/unassign conversations to users - ✅ Open and close conversations - ✅ Add closing notes and summaries - ✅ List users and get user by ID - ✅ List, get, and create custom fields - ✅ List channels and message templates (e.g.

README

Показан фрагмент оригинального README. Открыть оригинал.

Respond.io MCP Server

A Model Context Protocol (MCP) server implementation for the Respond.io API, enabling seamless integration with AI assistants, automation tools, and Claude Desktop.

Features

Contact Management

  • ✅ Get, create, update, and delete contacts
  • ✅ Create or update contact (upsert by identifier)
  • ✅ Merge two contacts (primary + secondary)
  • ✅ List contacts with filters and search
  • ✅ Add and remove contact tags
  • ✅ Update contact lifecycle stages
  • ✅ List contact channels (e.g. WhatsApp, Facebook)

Messaging

  • ✅ Send messages (text, attachments, WhatsApp templates, emails)
  • ✅ Retrieve message details and status
  • ✅ List messages for a contact (with pagination)
  • ✅ Support for multiple channel types

Conversations

  • ✅ Assign/unassign conversations to users
  • ✅ Open and close conversations
  • ✅ Add closing notes and summaries

Workspace Management

  • ✅ List users and get user by ID
  • ✅ List, get, and create custom fields
  • ✅ List channels and message templates (e.g. WhatsApp)
  • ✅ List closing notes (for closing conversations)
  • ✅ Create, update, and delete workspace tags

Comments

  • ✅ Add internal comments to contacts
  • ✅ Mention users in comments

HTTP/STDIO Dual Mode

  • ✅ Can run as a local subprocess via stdio or as an HTTP server (/mcp endpoint)
  • ✅ Health endpoint (/health) for monitoring and uptime checks
  • ✅ CORS enabled for HTTP mode

Prerequisites

  • Node.js 18+
  • npm / yarn / bun
  • Git

Installation

# Clone the repository
git clone https://github.com/respond-io/mcp-server.git
cd mcp-server

# Install dependencies (includes Respond.io SDK)
npm install

# Build the project
npm run build

The project depends on @respond-io/typescript-sdk. See SETUP_GUIDE.md for full installation and configuration.

Configuration

Environment Variables

The server is configured using environment variables. Set them in your shell or deployment environment.

  • RESPONDIO_API_KEY: (Required in STDIO mode) Your Respond.io API key. Not used in HTTP mode — see below.
  • RESPONDIO_BASE_URL: The base URL for the Respond.io API (defaults to https://api.respond.io/v2).
  • MCP_SERVER_MODE: The server mode, either stdio or http (defaults to stdio).
  • PORT: The port for HTTP mode (defaults to 3000).

How credentials work in each mode

Mode Where the token comes from
stdio RESPONDIO_API_KEY from the environment. The server process belongs to one user.
http The Authorization: Bearer header on each request. RESPONDIO_API_KEY is ignored and the server logs a warning if it is set.

[!IMPORTANT] HTTP mode has no built-in access control. Every request must carry its own Respond.io token, and the server forwards that token upstream unchanged.

Token validity is enforced by the Respond.io API, not by this server. This

Открыть полный README на GitHub

Установка

npx @respond-io/mcp-server
Новичок в MCP? Начните с руководства на mcpskill.org →