EQ5 Systems Architecture

Back to Creative Hub

8 MCP Connections

3 REST API Connections

2 File-based Sources

Cloudflare Deploy

Connection Type:

MCP Model Context Protocol — Claude reads & writes natively, no code required

API REST API — called via skill or curl

File File-based — repo files read as context

Deploy Shell script / Cloudflare trigger

How the agent loop works

You send a prompt

You type a request in Claude Code (the desktop or CLI app). Claude reads the full repo context — including CLAUDE.md, team files, and any files you mention — before responding.

Claude decides which tools to call

Based on your prompt and the instructions in CLAUDE.md, Claude calls MCP servers (Pipedrive, Slack, Notion, etc.) or REST APIs to pull live data. All tool calls are visible and require approval unless pre-allowed in settings.json.

Claude generates or edits files

Reports, hub pages, client portals, and team files are written directly to the repo on your local machine. Nothing is deployed automatically — Claude stages changes and you run ./deploy.sh when ready.

You deploy

Running ./deploy.sh pushes updates to GitHub, which triggers Cloudflare Pages to publish the hub. Cloudflare Access enforces who can see each page — no separate auth code needed.

End-to-end data flow

Example — Generate the weekly board report

💬
Your Prompt
Claude Code

reads

📋

CLAUDE.md

Runbook rules

API call

🎯

Pipedrive

Live deals + pipeline

writes

📊

Report .md

weekly_board_report/

deploy.sh

🌐

Hub Site

hub.equals5.com

All Connected Systems

🤖

Claude Code

AI Agent · Local App

Internal

The orchestration hub. Runs on your machine, reads the full repo as context, and calls every other system listed here. Powered by the Anthropic API (claude-sonnet-4-6).

Reads from repo

CLAUDE.md — instructions team/{name}/*.md — rep profiles hub/ — all HTML files settings.json — permissions

Writes to repo

hub/ pages reports/*.md news/weekly/ team/*.md updates

Connects to all MCP servers defined in .claude/launch.json. Tool calls require approval unless pre-allowed in settings.json.

🐙

GitHub

Version Control · Source of Truth

File + CLI

The eq5-sales repo stores everything: agent instructions, hub HTML, team profiles, Pipedrive exports, and weekly reports. Git is how changes get tracked and deployed.

What lives here

All hub/ HTML pages CLAUDE.md + settings.json team/ rep files reports/ + archive/ news/weekly/ briefings

Claude uses git via Bash — reads status, diffs, and log. You commit and push; Claude stages but does not push without confirmation.

🎯

Pipedrive

CRM · Deal Intelligence

REST API

The live CRM. Claude queries deals, pipeline stages, contacts, activities, and leads in real time using the /pipedrive skill — no exported files needed for current data.

Data Claude can read

Open + won deals by rep Deal value, stage, probability Brand, Disease, Agency (custom fields) Contacts + organizations Activities (calls, emails, meetings) Leads inbox + conversion status

Accessed via the /pipedrive skill, which loads curl examples and custom field mappings. Prefer live API over snapshot exports — snapshots go stale. Read-only in current setup.

💬

Slack

Team Communications

MCP

Claude can read channels, search message history, read threads, draft messages, and post on your behalf — directly from conversation context.

Data Claude can read

Channel messages + threads User profiles Public search results

Data Claude can write

Messages (draft or send) Scheduled messages Canvases

Connected via MCP server. The hub also pulls a slack-feed.json for the homepage news ticker — separate from the live MCP connection.

📅

Google Calendar

Scheduling · Meeting Management

MCP

Claude can list, create, update, and respond to calendar events — scheduling client calls, rep check-ins, and campaign milestones without leaving the conversation.

Data Claude can read

All calendars + events Attendees + RSVPs Available time slots

Data Claude can write

Create events Update / reschedule RSVP responses

OAuth-authenticated. Confirm before Claude sends invites or modifies shared calendars.

📧

Gmail

Email · Thread Intelligence

MCP

Claude can search threads, read emails, create drafts, and apply labels. Most useful for meeting prep (surfacing relevant client threads) and drafting follow-ups in a rep's voice.

Data Claude can read

Thread search results Full email body + attachments Labels + metadata

Data Claude can write

Draft emails Apply / create labels

Claude creates drafts only — it does not send email autonomously. Always review in Gmail before sending.

📓

Notion

Knowledge Base · Shared Docs

MCP

Used for structured knowledge and team-readable content that lives outside the repo. Claude can read and write pages and databases — campaign briefs, meeting notes, onboarding docs.

Data Claude can read

Pages + sub-pages Database rows + properties Comments

Data Claude can write

Create / update pages Add database rows Post comments

Good for content that needs rich formatting or non-developer access. Repo files remain the source of truth for agent instructions.

✅

ClickUp

Project Management · Tasks

MCP

Task and project tracking for campaigns, deliverables, and rep action items. Claude can read and update tasks — pulling open items into a briefing or logging next steps after a meeting.

Data Claude can read

Tasks + subtasks Assignees + due dates Lists, folders, spaces Time entries

Data Claude can write

Create tasks Update status + assignee Add comments

Full workspace hierarchy is accessible. Useful for campaign kickoff checklists — see internal/campaign_processes/ for templates.

🦋

Fireflies.ai

Meeting Intelligence · Transcription

MCP

Records and transcribes all meetings. Claude can fetch full transcripts, AI summaries, soundbites, and analytics — enabling post-meeting deal updates and action item extraction.

Data Claude can read

Full meeting transcripts AI summaries + action items Soundbites Meeting analytics Participant list

Use after client calls to extract intel, update rep narrative files, or draft Pipedrive activity notes — without re-watching the recording.

🎨

Figma

Design System · Presentation Templates

MCP

Stores the EQ5 Brandbook and SLIDES presentation templates. Primary flow is code→Figma: Claude generates design output and pushes it into Figma for review and refinement.

Data Claude can read

Design context + tokens Component screenshots File metadata

Data Claude can write

Push designs into files Create new frames Upload assets

Two files: SLIDES (zkasJapbZWbZ88TXj5oHSk) and Brandbook (MoIYxNnhadZgmS7uFXr4Bf). Always run /figma-use before calling use_figma.

🌐

EQ5 Hub Site

Internal Dashboard · Client Portals

Deploy

The internal intelligence hub. All pages are static HTML/CSS/JS generated and maintained by Claude, deployed to Cloudflare Pages via ./deploy.sh.

What it contains

Home feed (news + signals) Leaderboard Team pages Client portals (INTERNAL + CLIENT-FACING) Competitive intelligence

Two portal types: INTERNAL (pipeline, pricing, strategy — never share) and CLIENT-FACING (sanitized performance data — safe to share). Each is gated individually by Cloudflare Access.

🔒

Cloudflare

Hosting · Access Control

Deploy

Cloudflare Pages hosts the hub. Cloudflare Access gates every page with email-based allowlists — no login UI to build. Each client portal gets its own Access application.

What it controls

Hosting for hub.equals5.com Per-page access policies Employee + client email allowlists

See internal/access_management/README.md for onboarding/offboarding runbooks. Per-client access is mirrored in hub/clients/{client}/access.md.

Example prompts — what you can ask Claude to do

Pipedrive · API

"What's in Chris Colella's pipeline this week?"

Claude calls the Pipedrive API live, pulls open deals for Chris, groups by stage, and formats a briefing with deal values, next steps, and probability.

Pipedrive + Hub · API + File

"Generate the weekly board report and update the hub."

Pulls live deal data from Pipedrive, writes the board report MD, updates team home pages, then you run ./deploy.sh.

Fireflies · MCP

"Summarize yesterday's Incyte call and update the portal."

Fetches the Fireflies transcript, extracts key topics and action items, updates the client portal with fresh intel.

Slack · MCP

"Draft a Slack message about this week's top opportunity."

Claude reads the pipeline, identifies the highest-probability deal, drafts a message in your voice, and posts after your approval.

Gmail · MCP

"Prep me for my call with Regeneron — pull any recent emails."

Searches Gmail for Regeneron threads, surfaces the most recent, combines with CRM deal data, and generates a pre-call briefing.

ClickUp · MCP

"What are the open campaign tasks for the Opzelura launch?"

Searches ClickUp for Opzelura tasks, returns open items with assignees and due dates, and flags anything overdue.

Google Calendar · MCP

"Schedule a follow-up with Amgen for next Tuesday at 2pm."

Creates the calendar event with attendees, adds deal context from Pipedrive, and returns the event link.

Figma · MCP

"Build a new slide deck for the Zynyz pitch."

Uses the SLIDES Figma template, generates brand-compliant slides with Zynyz messaging, and pushes the result into Figma for review.

Contributing — how to add a new integration

Add the MCP server to .claude/launch.json

Tells Claude Code which MCP servers to connect to at startup. Each entry needs a name, command, and any auth env vars. Restart Claude Code after changes.

Auto-allow safe tool calls in settings.json

Add read-only tool calls to allow so Claude doesn't prompt you every time. Never auto-allow destructive operations (delete, send, post). Run /fewer-permission-prompts to get suggestions.

Document the integration in CLAUDE.md

Add a row to the Reference Materials table and relevant instructions to the matching section. No documentation = Claude won't know the integration exists.

Add a card to this page

Copy a .sys-card block in training/index.html, update the name, category, connection type badge, and data chips to keep the team's mental model current.