@lssm/app.communicationos-mcp
v3.0.2
Published
MCP server exposing CommunicationOS contracts as AI-callable tools via the Model Context Protocol.
Downloads
77
Readme
CommunicationOS MCP
Governed Model Context Protocol surface for CommunicationOS. It exposes
tenant-scoped thread reads, drafting, summarization, extraction, provider health,
inbound-route inspection, and the canonical Forms operation registry. Forms
tools inherit their contract auth and PII annotations. Direct
communication.reply.send is intentionally
excluded: outbound delivery remains subject to room membership, current
authority, and the approval/send orchestrator.
MailerSend diagnostics
createMailerSendMcpProviderDependencies binds the read-only
integrations.email.provider.health and
integrations.email.inbound-routes.list tools. The host injects a
tenant-and-connection-scoped resolver returning MailerSend credentials and a
domain id. Secrets never appear in MCP tool inputs or outputs.
The default stdio server has no provider resolver or authenticated subject and therefore fails closed. Production hosts must inject an AuthOS-backed subject resolver and a vault-backed connection resolver before tools can execute.
