VivaDialog

com.vivadialogPublished by vivadialog.comOfficial publisherv0.3.0Updated Oct 26, 2026

Read and work a VivaDialog social inbox: reply to customers, tag, manage contacts and automations.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

VivaDialog connects an assistant to a VivaDialog social inbox so it can reply to customers, tag conversations, and manage contacts and automations.

What you can do
  • Reply to customers in a VivaDialog social inbox
  • Tag and organize conversations
  • Manage contacts
  • Manage automations
When to use it
Useful when a team runs customer conversations through VivaDialog and wants an assistant to draft or send replies, tag threads, and keep contacts and automations up to date without switching apps.
Requirements
A remote MCP endpoint at api.vivadialog.com reached over streamable HTTP, with OAuth sign-in to a VivaDialog account. No environment variables or headers are declared.
Before you install
The assistant can act on live customer conversations: replies are sent to customers and tags, contacts and automations can be changed. Grant access only to accounts whose inbox data you are comfortable exposing, and review what it sends before relying on it.

Installation

In SourceWeft

  1. Open VivaDialog 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/com.vivadialog%2Fvivadialog/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": {
    "vivadialog": {
      "type": "http",
      "url": "https://api.vivadialog.com/mcp"
    }
  }
}

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

2
  1. v0.3.0LatestOct 26, 2026
  2. v0.2.0Oct 22, 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 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
  • 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.