Jan 14, 2026 - Michael

Work Log

Linear MCP Integration

Set up Linear MCP connection using official server at https://mcp.linear.app/sse
Created "MCP Demo" team for testing natural language task management
Established projects: GTM/Sales, Content Marketing, Product, Internal Ops
Created labels: Thomas, Michael, ✉️ Email, 📞 Call, ✍️ Content, 🔧 Dev, 🔍 Research, ⏳ Blocked, 🗣️ Needs Alignment

Huddle Transcript Processing

Processed Jan 14 huddle transcript into Linear issues (MCP-20 through MCP-28)
Key items captured: Website work, tier-1 outreach batch, email tracking research, hot list system

Email Tracking Research (MCP-22)

Researched Apollo vs Instantly for email tracking with MCP support
Key finding: Apollo MCP only supports search/enrichment, NOT tracking
Instantly has official MCP at https://mcp.instantly.ai/mcp with 31 tools
Created plan doc at ~/.claude/plans/joyful-munching-fox.md
Created Linear document "Email Tracking Research: Instantly vs Apollo"
Recommendation: Use Instantly ($97/mo Hypergrowth plan) for sending/tracking, keep Apollo for enrichment

Task Hierarchy Restructuring

MCP-23 (Hot List System) set as parent task for all outreach prep
Subtasks: MCP-27 (relationship structure design), MCP-28 (compile contact list), MCP-24 (email history storage)
MCP-10, 11, 14, 21 marked as blocked by MCP-23

Items Needing Alignment (2:30 PM Discussion)

1. MCP-27: Relationship Management Structure

Decision needed: How do we store relationship info?

Options: Linear issues per contact? Markdown files? Database?
Needs to handle: ongoing relationships, product linkage, frequent touchpoints, growing context
URL: https://linear.app/daisy-core-2/issue/MCP-27

2. MCP-24: Email History Storage

Decision needed: Where does email history live?

Apollo can't export tracking to Claude Code (MCP limitation)
Options: Store locally? Use Instantly? Manual sync?
Part of MCP-23 (Hot List System)

3. MCP-26: Switch to Instantly?

Decision needed: Add Instantly for email sending + tracking?

Cost: $97/mo (Hypergrowth plan for API access)
Benefit: Full MCP control, never need UI
Trade-off: Additional tool, but Apollo can't do tracking via MCP
Research doc attached to issue
URL: https://linear.app/daisy-core-2/issue/MCP-26

Thinking/Decisions

Why Alignment Matters Here

These aren't just my systems to build - Thomas needs to co-author them. The relationship structure affects how we both interact with contacts. Email history storage affects both our workflows. Tool choices affect our shared budget.

The "🗣️ Needs Alignment" label surfaces these automatically when we query Linear.

Task Flow Logic

Can't send 35 emails → until we know where to store the record
Can't store records → until we design the system
System design → needs joint discussion

This is why MCP-23 (Hot List System) blocks everything else.

Notes

Linear MCP can do full CRUD on issues, projects, documents - cannot delete or create teams
Can query "Needs Alignment" items: mcp__linear__list_issues with label filter
Natural language task management working well - drop transcript, get structured issues
Website still in progress (Thomas) - target was 2:30 PM but may slip