CloudContactAI Ships Native MCP Support

Week of October 20–27, 2026

It’s been a busy week across the platform, headlined by two significant feature launches: a brand-new standard MCP server that opens up CloudContactAI’s toolset to AI agents everywhere, and the backend groundwork for fully managed custom email domains. Here’s what shipped.

Native MCP Support Arrives

The biggest release this week came out of mcpexecutor, where a new /mcp/v1 endpoint now exposes all 48 of CloudContactAI’s tools, contacts, campaigns, SMS, email, stats, and more, over the official Model Context Protocol. That means Claude Code, Claude Desktop, and Kiro can now talk to CloudContactAI natively, alongside the existing Bedrock-format integration.

Shipping a new protocol surface is never just a routing change, so this release came with a platform upgrade too: Java 21, Spring Boot 4, and Kotlin 2.3, backed by 169 new tests to keep the migration honest.

A couple of sharp-eyed fixes followed close behind launch:

• SMS campaigns created with explicit contactIds were silently going out to nobody, a contact lookup bug that’s now fixed by resolving each contact directly.
• MCP clients that inspect schemas were only getting back bare IDs instead of full content; results now include the complete payload.

On the config side, the team also renamed the CHARLIE_REDIS_* environment variables to the standard REDIS_* convention, consolidated MCP auth onto the shared TOKEN_PUBLIC_KEY, and added Claude Sonnet 4.6 and 5.5 to the allowed Bedrock foundation models list.

To support MCP token validation, clientbackendmicroservice also picked up a new GET /api/v1/user/token/validate endpoint, which correctly rejects app tokens and admin keys where they don’t belong.

Managed Email Domains, Backend and Front

In parallel, work continued on letting customers send email from their own managed/custom domains rather than a shared one. This week’s commits covered both ends:

• Backend (emailcampaignmicroservice, emailsendermicroservice): updates to ManagedEmailService plus a new TenantProvisioningService to handle tenant-specific sending setup.
• Frontend (clientfrontend): a new DNS-verification-status component, a reworked email-config screen, and a new managed-email icon, giving users a clear view into whether their domain’s DNS records are properly configured.

Smaller Fixes

A few lower-key but worthwhile changes also landed:

• Inbox contact saving got a markup and styling pass in clientfrontend, paired with adjustments to UnsubscribedPhoneService in contact-microservice.
• A temporary hotfix removed the /api/v1/test/sms test endpoint from clientbackendmicroservice.
• Billing services got a quiet infra fix: paymentprocessormicroservice and stripeintegrator both received the same one-line Dockerfile correction to their amazoncorretto base image.

Looking Ahead

With native MCP support now live and managed email domains taking shape on both ends of the stack, next week will likely bring continued hardening on both fronts, plus whatever else the team decides to pick up next.

8 of ~52 repositories saw activity this week; the rest were quiet.