What was built
The Brain MCP is the connective layer between Claude and everything Derek Rose runs internally. Instead of switching between Pipedrive, spreadsheets and the reporting stack, the team asks a question in chat and the MCP goes and gets the answer.
The core system is a Model Context Protocol server hosted on the client VPS. It exposes the CRM, ERP and order data as tools Claude can call directly: look up a customer, pull order history, check inventory state by style code, cross reference a stockist against recent activity. Every tool call runs through access checks, so what a person can see in chat matches what they can see in the CRM.
The report builder is the feature the team uses most. Someone describes the report they want in plain language, the MCP resolves it against live data, and Claude returns the finished output. No SQL, no export and reformat cycle. We tested it against real reporting requests from the commercial side before rolling it out.
Alongside the tools sit the playbooks. We consolidated a scattered set of Claude projects into a single Git repository so prompts, skills and company context live in version control rather than in individual chat windows. Push a change to the repo and the server picks it up automatically. That deploy pipeline was the unlock: it turned the brain from something one person maintained by hand into infrastructure the whole team relies on.
The best part: Founder and CEO picked the approach up immediately and extended the functionality himself. We only assisted on right ways to prompt. We provided the core, CEO took it beyond our imagination and created both MCP tools and web UI for his team to access.
We also hardened the surrounding setup: secrets moved into encrypted storage, and we designed and shipped a backup strategy that pushes the VPS databases to remote storage on a schedule. The brain holds real business data, so it gets treated like production infrastructure.
Tech stack
- MCP server on the client VPS, connected to Claude Desktop and Claude web
- Pipedrive API for CRM, deal and order data
- Business Central for ERP and order data
- Git based deployment with automatic rollout on push
- Scheduled database backups to remote storage
- Custom skills for report generation with per user access checks
Other projects in this case study
Ongoing Support
Ongoing Support covers the continuous operation and evolution of Derek Rose's Make.com automation stack from 2024 through present. The work spans three main areas: regular break recovery on the…
Read case studyJotForm + AI Agent
We ran a scoped evaluation of JotForm's built-in AI agent feature to determine whether it could replace or reduce manual data collation work inside Derek Rose's existing Pipedrive and Make.com stack.
Read case studyImage Automation
The Image Automation project automated Derek Rose's product image collection workflow by style code. The system retrieves product identifiers from Pipedrive deals, searches Microsoft…
Read case studyAutomatic Imports
Automatic Imports is Derek Rose's largest and most complex project: a sophisticated multi-scenario inventory import system that processes product catalog data from upstream sources and syncs it into…
Read case studyPipedrive Onboarding
The Pipedrive onboarding project established the foundational CRM infrastructure for Derek Rose's sales operations. Work included configuring the Pipedrive instance with custom fields, deal pipelines…
Read case study