Comms
Workspace messaging: conversations, contacts, agents, and connected lines through scoped OAuth.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http comms 'https://comms.osis.co/api/v1/comms/mcp'
{
"mcpServers": {
"comms": {
"type": "http",
"url": "https://comms.osis.co/api/v1/comms/mcp"
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
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
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
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:
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
- Documentation
- Support — support@osis.co
- Privacy policy
- Terms of service
Published by Osis AI LLC. The Comms name and logo remain the property of Osis AI LLC.
Frequently asked questions
What is Comms?
Workspace messaging: conversations, contacts, agents, and connected lines through scoped OAuth.
How do I install Comms?
It runs as a remote server. In Claude Code: claude mcp add --transport http comms 'https://comms.osis.co/api/v1/comms/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Comms need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Comms open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains Comms?
It is published by Osis-AI-LLC. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.