What we built
Brain MCP is a custom MCP server that connects Claude to CREATIO's core business systems. Instead of the AI just answering questions, it can now execute real operations: create HubSpot deals from inbound leads, send and reassign emails in Missive, organize files into the correct Google Drive project folders, and trigger Make.com scenarios with full blueprint awareness.
The server runs on CREATIO's own infrastructure with push-triggered CI/CD for auto-redeployment. We hit an early blocker — Google's service account keys were blocked by the client's org policy — so we pivoted to user-OAuth authentication mode instead.
A key design decision: runtime-configurable credentials via *_connect tools. This lets the team swap API tokens without redeploying, and keeps secrets managed through Infisical rather than hardcoded.
The repo is mirrored to CREATIO's own GitHub organisation, and we've set up a public vault endpoint at vault.creatio.ch via Caddy vhost. There's also ongoing monthly code review of Claude-generated MCP output by the client's internal engineering team.
Tech stack
- MCP server: Custom TypeScript implementation with RFC-9728 OAuth-discovery security
- Integrations: HubSpot (single-tenant app-token auth), Missive (channels, send, reassign, refolder), Google Drive (user-OAuth), Make.com (scenario listing + blueprint-aware launch)
- Infrastructure: Client-hosted server, Caddy reverse proxy, GitHub Actions CI/CD
Recently touched
- 2026-09-05 Every deploy hits a container-name conflict and takes the MCP server down mid-rebuild Done
- 2026-09-04 Serve the repo slash commands as MCP prompts (layer 3 of the instructions pattern) Done
- 2026-09-04 Repo remotes and deploy docs still point at the pre-transfer GitHub path (dead PAT) Done
- 2026-09-04 Only the GitHub Actions deploy key still reaches the VPS — no human can SSH in, so nothing can recover a failed deploy Open
- 2026-09-03 Monthly code review — September 2026 (Creatio MCP, Claude-generated output) Open