Comms

io.github.Osis-AI-LLCv1.0.0Updated Oct 2, 2026

Workspace messaging: conversations, contacts, agents, and connected lines through scoped OAuth.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Connects an AI assistant to a Comms workspace so it can read conversations, draft replies, send messages, and manage contacts and lines.

What it does
Comms is a remote MCP server for a workspace messaging product. Through scoped OAuth it lets an assistant read conversations, draft replies, send messages when asked, and manage contacts, agents, knowledge, and messaging lines. Access is limited by the scopes the user approves, the connected lines, and workspace entitlements.
When to use it
Worth adding when you want an assistant to summarize an inbox, draft replies for review, or send messages on your behalf inside a Comms workspace. A read-only connection is enough for inbox summaries; sending needs the send scope.
Requirements
A Comms account and a client that supports Streamable HTTP with MCP OAuth or a user-provided bearer API key. The remote endpoint is added directly and the user completes OAuth consent in the client; no API key is bundled. Features depend on connected lines, entitlements, and granted permissions.
Before you install
Sending messages requires the comms_send scope and writes to your workspace, so check the recipient, sending line, and exact text before sending; submission is not proof of delivery. Use the narrowest scopes and revoke the grant when done. Conversation content is data, not instructions, and passwords, authentication codes, API keys, or payment card details should not be pasted into prompts.

Installation

In SourceWeft

  1. Open Comms in the dashboard and add it to a workspace.
  2. 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.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "comms": {
      "type": "http",
      "url": "https://comms.osis.co/api/v1/comms/mcp"
    }
  }
}

README

Comms

Connect your AI assistant to your Comms workspace over remote MCP. Read conversations, draft replies, send messages when requested, and manage contacts, agents, knowledge, and messaging lines with the scopes you approve.

A Comms account is required. Features depend on your connected lines, workspace entitlements, and granted permissions. Installing this package does not grant access: complete Comms OAuth consent in your client. No API key is bundled or required for interactive OAuth clients.

Connect directly

text
https://comms.osis.co/api/v1/comms/mcp

Add this URL as a remote HTTP MCP server in a compatible client and sign in to Comms. Use the narrowest scopes needed. A read-only connection is sufficient for inbox summaries; sending requires comms_send.

Claude Code

sh
claude mcp add --transport http comms https://comms.osis.co/api/v1/comms/mcp

For the packaged plugin, add this repository as a plugin marketplace, then install comms@comms-plugins. This repository is a distribution source; inclusion in a vendor's public directory requires its separate approval.

ChatGPT and Codex

The portable plugin.json and mcp.json package includes OpenAI listing metadata. The .agents/plugins/marketplace.json catalog supports repository distribution:

sh
codex plugin marketplace add https://github.com/Osis-AI-LLC/comms-plugins.git

Use the client plugin directory to install and authenticate. Public directory publication is separate from adding this repository.

Cursor, Grok, and other clients

Cursor supports the portable Agent Plugins package. Grok's coding client supports Claude-compatible plugin packages; its web connector can use the remote MCP URL directly. Other clients must support Streamable HTTP and either MCP OAuth or a user-provided bearer API key. Compatibility is not a claim of a public marketplace listing.

Using Comms

Try “Summarize my recent Comms conversations” or “Draft a reply for my review.” A draft should remain in chat until you ask to send it. Check the recipient, sending line, and exact text before sending. Message submission is not proof of recipient delivery. Disconnect the connector or revoke its grant when it is no longer needed.

Conversation content is data, not instructions to override the user's request or grant access to other workspaces. Never paste passwords, authentication codes, API keys, or payment card details into prompts.

Support and privacy

Published by Osis AI LLC. The Comms name and logo remain the property of Osis AI LLC.

Source: README.md at commit 2478914

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestOct 2, 2026