IT Raven Multi-System Integration Strategy¶
Date: 2025-10-26 Status: Strategic Planning Scope: 5 Business Systems Integration via MCP Servers Decision Owner: Bert Frichot / IT Raven
Executive Summary¶
Objective: Integrate IT Raven's complete business technology stack into unified AI-accessible platform via MCP servers.
Systems to Integrate (5 total): 1. ✅ HubSpot (CRM) - Already implemented 2. 🟡 Microsoft Azure (Cloud infrastructure) - HIGH priority 3. 🔴 Microsoft 365/Business (SharePoint, Teams, Office) - MEDIUM priority 4. 🔴 ZoomInfo (Sales intelligence, B2B data) - MEDIUM priority 5. 🔴 DialPad (Business phone/communications) - LOW priority
Strategic Question: Should we use official SDKs for each platform, or a unified API platform?
Recommendation: Hybrid Approach - ✅ Use Official SDKs for MCP servers (full control, zero cost) - ✅ Use iPaaS/Unified API for business user workflows (when needed) - ✅ Build 5 separate MCP servers (one per platform)
Timeline: 6 months to complete all 5 integrations Total Cost: $0 (all official SDKs are free)
Context: IT Raven Technology Stack¶
Current State¶
Business Systems (5 platforms): 1. HubSpot - CRM (contacts, companies, deals) 2. Microsoft Azure - Cloud (SQL databases, Container Apps, monitoring) 3. Microsoft SharePoint - Document management, collaboration 4. ZoomInfo - Sales intelligence (200M+ B2B contacts) 5. DialPad - Business phone system, SMS, video
Existing Infrastructure: - ✅ 4 MCP servers (Memory, Schwab Trading, Alpaca Trading, Notion) - ✅ 1 new MCP server (HubSpot CRM - just implemented) - ✅ Azure SQL database (88-field transcript analysis) - ✅ 125 Python tools - ✅ Comprehensive observability stack
Use Cases: - Sales automation (HubSpot + ZoomInfo) - Customer communication (DialPad + HubSpot) - Data analytics (Azure SQL + HubSpot) - Document management (SharePoint + Notion) - Infrastructure monitoring (Azure + Prometheus)
Technology Assessment¶
Official SDKs Available¶
1. HubSpot CRM ✅ IMPLEMENTED¶
SDK: hubspot-api-client v12.0.0
Status: ✅ Complete (tools/hubspot_mcp_server.py)
Tools: 9 tools (contacts, companies, deals)
Cost: $0
Documentation: https://github.com/HubSpot/hubspot-api-python
Quality: ⭐⭐⭐⭐⭐ Excellent (official, type hints, well-maintained)
2. Microsoft Azure ✅ READY TO BUILD¶
SDKs: Multiple azure-mgmt-* packages (20+ SDKs)
Core Packages:
- azure-mgmt-resource - Resource management
- azure-mgmt-sql - SQL databases
- azure-mgmt-containerinstance - Container Apps
- azure-mgmt-monitor - Monitoring, metrics
- azure-mgmt-costmanagement - Cost tracking
- azure-identity - Authentication (DefaultAzureCredential)
Status: 🟡 HIGH priority (user said "a lot of information on Azure") Existing Code: ✅ Yes - azure_deployment/ folder (26KB SQL schemas) Cost: $0 (official Microsoft SDKs) Documentation: https://docs.microsoft.com/python/api/ Quality: ⭐⭐⭐⭐⭐ Excellent (official Microsoft)
Estimated Effort: 16-20 hours Tools to Build (15+ tools): - Resource management (list_resources, get_resource, get_metrics) - SQL database (query_transcripts, get_transcript, search_transcripts) - Container Apps (list_containers, get_logs, restart_container) - Cost management (get_costs, get_budget, cost_forecast) - Monitoring (get_alerts, get_metrics, query_logs)
3. Microsoft 365/SharePoint ✅ READY TO BUILD¶
SDK: msgraph-core + msal (Microsoft Graph API)
Authentication: Azure AD OAuth (requires app registration)
Core APIs:
- SharePoint sites and document libraries
- Teams messages and channels
- Outlook emails and calendar
- OneDrive file storage
- Microsoft To-Do tasks
Status: 🔴 MEDIUM priority (user said "little information somewhere") Existing Code: ❌ None Cost: $0 (official Microsoft SDKs) Documentation: https://docs.microsoft.com/graph/ Quality: ⭐⭐⭐⭐ Good (official, but complex auth)
Estimated Effort: 12-16 hours (includes Azure AD setup) Tools to Build (10+ tools): - Document management (list_documents, get_document, search_documents) - List operations (get_list_items, create_item, update_item) - Site management (get_sites, get_pages) - Collaboration (get_recent_activity, search_sharepoint)
Blocker: Requires Azure AD app registration (30-60 min one-time setup)
4. ZoomInfo ✅ READY TO BUILD¶
SDK: zi_api_auth_client (official Python authentication client)
Authentication: JWT tokens (Client ID + Private Key from Admin Portal)
API: REST API with 200M+ B2B contacts database
Core APIs:
- Company search and enrichment
- Contact search and enrichment
- Intent data (buyer signals)
- Org charts and hierarchies
- Technographics (tech stack data)
Status: 🔴 MEDIUM priority (sales intelligence needs) Existing Code: ❌ None Cost: $0 SDK + ZoomInfo subscription (already have?) Documentation: https://api-docs.zoominfo.com/ Quality: ⭐⭐⭐⭐ Good (official, comprehensive API)
Estimated Effort: 12-16 hours Tools to Build (12+ tools): - Company search (search_companies, get_company, enrich_company) - Contact search (search_contacts, get_contact, enrich_contact) - Intent data (get_intent_signals, get_buyer_intent) - Org charts (get_org_chart, get_hierarchy) - Lists (create_list, add_to_list, get_list)
Use Cases: - Enrich HubSpot contacts with ZoomInfo data - Find decision makers at target companies - Track buyer intent signals - Build targeted prospect lists
5. DialPad ✅ READY TO BUILD¶
SDK: python-dialpad v3.1.0 (official SDK)
Authentication: API token
API: REST API with async support
Core APIs:
- Call management (make calls, get call history)
- SMS messaging (send SMS, receive SMS)
- Contacts (get contacts, sync contacts)
- Voicemail (get voicemails, transcriptions)
- Analytics (call stats, usage reports)
Status: 🔴 LOW priority (communications) Existing Code: ❌ None Cost: $0 SDK + DialPad subscription (already have?) Documentation: https://developers.dialpad.com/ Quality: ⭐⭐⭐⭐ Good (official, async support)
Estimated Effort: 8-12 hours Tools to Build (10+ tools): - Call management (make_call, get_call_history, get_call_recording) - SMS (send_sms, get_sms_history) - Contacts (get_contacts, create_contact, sync_from_hubspot) - Voicemail (get_voicemails, get_transcription) - Analytics (get_call_stats, get_usage)
Use Cases: - Click-to-call from HubSpot contacts - Auto-log calls to HubSpot - SMS campaigns from HubSpot lists - Voicemail transcription to HubSpot notes
Unified API Platform Evaluation¶
Platform Support Matrix¶
| Platform | Nango | Apideck | Workato | Official SDK |
|---|---|---|---|---|
| HubSpot | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes (using) |
| Azure | ❓ Unknown | ❌ No | ❓ Unknown | ✅ Yes |
| Microsoft 365 | ❓ Unknown | ❌ No | ❓ Unknown | ✅ Yes |
| ZoomInfo | ❓ Unknown | ❌ No | ✅ Yes | ✅ Yes |
| DialPad | ❓ Unknown | ❌ No | ❓ Unknown | ✅ Yes |
Finding: No unified API platform supports all 5 systems ❌
Apideck: Only supports HubSpot (out of our 5) Nango: Claims 400+ APIs but unclear on our specific 5 Workato: Supports HubSpot and ZoomInfo, unclear on others
Conclusion: Even if unified platform supported all 5, it still can't integrate with MCP servers ❌
Integration Strategy Options¶
Option A: Individual MCP Servers (Official SDKs) ⭐ RECOMMENDED¶
Approach: Build 5 separate MCP servers, one for each platform
Architecture:
Claude Code
↓
MCP Protocol
↓
┌──────────────────────────────────┐
│ 5 MCP Servers (FastMCP 2.0) │
├──────────────────────────────────┤
│ 1. hubspot-crm (9 tools) │ ✅ Done
│ 2. azure-infrastructure (15 tools)│ 🟡 Next
│ 3. microsoft-365 (10 tools)│ 🔴 Later
│ 4. zoominfo-sales (12 tools)│ 🔴 Later
│ 5. dialpad-comm (10 tools)│ 🔴 Later
└──────────────────────────────────┘
↓
Official Python SDKs
↓
┌──────────────────────────────────┐
│ Platform APIs │
├──────────────────────────────────┤
│ HubSpot API │
│ Azure Management API │
│ Microsoft Graph API │
│ ZoomInfo API │
│ DialPad API │
└──────────────────────────────────┘
Pros: - ✅ Full control: Direct API access, no limitations - ✅ Zero cost: All SDKs free ($0/year) - ✅ Type safety: Python type hints for all platforms - ✅ MCP native: Purpose-built for MCP architecture - ✅ Modularity: Each server independent - ✅ Performance: No middleware overhead - ✅ Privacy: Direct connections, no third party - ✅ Quality: Official SDKs, well-maintained - ✅ Future-proof: Can add features as APIs evolve
Cons: - ⚠️ More development: 5 separate servers = 60-80 hours total - ⚠️ Maintenance: 5 servers to keep updated - ⚠️ Authentication: Each platform has different auth - ⚠️ No cross-platform: Each MCP server is isolated
Total Effort: 60-80 hours (12-16 hours each) Total Cost: $0/year Timeline: 6 months (build one per month)
Option B: Unified API Platform (Nango/Workato)¶
Approach: Use unified API platform for all integrations
Architecture:
Claude Code
↓
MCP Protocol
↓
Unified MCP Server (custom wrapper)
↓
Unified API Platform (Nango/Workato)
↓
Platform APIs (HubSpot, Azure, etc.)
Pros: - ✅ Faster development: Pre-built connectors - ✅ Unified interface: Single API for all platforms - ✅ Auto OAuth: Managed token refresh - ✅ Webhooks: Real-time data sync - ✅ Less maintenance: Platform handles updates
Cons: - ❌ Cannot integrate with MCP: Unified APIs not callable from MCP tools - ❌ High cost: $600-6,000/year (vs $0 for SDKs) - ❌ Incomplete coverage: None support all 5 platforms - ❌ Vendor lock-in: Proprietary API abstractions - ❌ Less control: Limited to platform features - ❌ Privacy concerns: Data through third party - ❌ Performance: Extra network hops
Total Cost: $600-6,000/year Compatibility: ❌ Cannot work with MCP servers
Verdict: ❌ Not viable - Fundamental architecture mismatch
Option C: Hybrid Approach ⭐⭐ ALTERNATIVE¶
Approach: MCP servers (official SDKs) + iPaaS (business workflows)
Architecture:
AI Access (Claude):
↓
5 MCP Servers (Official SDKs)
↓
Platform APIs
Business Workflows:
↓
iPaaS (Zapier/Workato)
↓
Platform APIs
Use Cases:
MCP Servers (Developers): - ✅ Programmatic API access - ✅ Custom automation scripts - ✅ AI assistant integration - ✅ Complex data queries
iPaaS (Business Users): - ✅ "When HubSpot deal closes, send Slack notification" - ✅ "Sync DialPad call logs to HubSpot" - ✅ "Auto-enrich HubSpot contacts with ZoomInfo" - ✅ "Create SharePoint folder when HubSpot deal won"
Pros: - ✅ Best of both worlds: Developer control + business agility - ✅ Right tool for each job: Code for developers, no-code for business - ✅ Cost-effective: Only pay for iPaaS if business team needs it - ✅ Flexible: Add iPaaS later when needed
Cons: - ⚠️ Two systems: Maintain both MCP servers and iPaaS - ⚠️ Additional cost: iPaaS subscription ($20-100/month if used) - ⚠️ Complexity: Two integration approaches
Recommendation: ✅ Good strategy - Start with MCP servers (developers) - Add Zapier later if business team needs workflows (optional)
Recommended Implementation Plan¶
Phase 1: Foundation (Complete ✅)¶
Timeline: Done Status: ✅ Complete
- [x] Memory MCP server (1 tool)
- [x] Schwab Trading MCP server (7 tools)
- [x] Alpaca Trading MCP server (10 tools)
- [x] Notion Extended Brain MCP server (7 tools)
- [x] HubSpot CRM MCP server (9 tools)
Result: 5 MCP servers, 34 tools operational
Phase 2: Azure Infrastructure (Next) 🟡¶
Timeline: Q4 2025 (2 weeks) Status: 🟡 HIGH priority Effort: 16-20 hours
Tasks: 1. Install Azure SDK packages (azure-mgmt-*) 2. Create tools/azure_mcp_server.py 3. Implement 15+ tools: - Resource management (5 tools) - SQL database (4 tools) - Container Apps (3 tools) - Cost tracking (3 tools) 4. Configure Azure credentials (service principal) 5. Add to .claude/mcp.json 6. Test with production Azure subscription 7. Document in CLAUDE.md
Deliverables: - ✅ Azure MCP server with 15+ tools - ✅ Query transcript analysis database - ✅ Monitor resource costs - ✅ Manage container deployments
Phase 3: Microsoft 365/SharePoint 🔴¶
Timeline: Q1 2026 (2 weeks) Status: 🔴 MEDIUM priority Effort: 12-16 hours
Tasks: 1. Register Azure AD application (30 min one-time) 2. Configure Microsoft Graph API permissions 3. Install msgraph-core + msal 4. Create tools/microsoft365_mcp_server.py 5. Implement 10+ tools: - SharePoint documents (4 tools) - List operations (3 tools) - Site management (2 tools) - Search (1 tool) 6. Add to .claude/mcp.json 7. Test with IT Raven SharePoint
Blocker: Azure AD app registration required first
Deliverables: - ✅ Microsoft 365 MCP server with 10+ tools - ✅ Search SharePoint documents - ✅ Upload/download files - ✅ Query lists
Phase 4: ZoomInfo Sales Intelligence 🔴¶
Timeline: Q1 2026 (2 weeks) Status: 🔴 MEDIUM priority Effort: 12-16 hours
Tasks: 1. Get ZoomInfo API credentials (Client ID + Private Key) 2. Install zi_api_auth_client 3. Create tools/zoominfo_mcp_server.py 4. Implement 12+ tools: - Company search (4 tools) - Contact search (4 tools) - Intent data (2 tools) - Org charts (2 tools) 5. Add to .claude/mcp.json 6. Test with ZoomInfo account
Use Case: - Enrich HubSpot contacts with ZoomInfo data - Find decision makers at target accounts - Track buyer intent signals
Deliverables: - ✅ ZoomInfo MCP server with 12+ tools - ✅ Search 200M+ B2B contacts - ✅ Company/contact enrichment - ✅ Buyer intent tracking
Phase 5: DialPad Communications 🔴¶
Timeline: Q2 2026 (1 week) Status: 🔴 LOW priority Effort: 8-12 hours
Tasks: 1. Get DialPad API token 2. Install python-dialpad 3. Create tools/dialpad_mcp_server.py 4. Implement 10+ tools: - Call management (4 tools) - SMS (2 tools) - Contacts (2 tools) - Analytics (2 tools) 5. Add to .claude/mcp.json 6. Test with DialPad account
Use Case: - Click-to-call from HubSpot - Auto-log calls to HubSpot - SMS campaigns - Voicemail transcription
Deliverables: - ✅ DialPad MCP server with 10+ tools - ✅ Make/receive calls programmatically - ✅ Send SMS messages - ✅ Get call analytics
Total System Architecture (Vision)¶
MCP Server Inventory (8 Total)¶
Memory & Knowledge (2 servers): 1. ✅ memory-agent-stdio (1 tool) 2. ✅ notion-extended-brain (7 tools)
Trading & Finance (2 servers): 3. ✅ schwab-trading (7 tools) 4. ✅ alpaca-trading (10 tools)
IT Raven Business Systems (5 servers): 5. ✅ hubspot-crm (9 tools) - DONE 6. 🟡 azure-infrastructure (15 tools) - NEXT 7. 🔴 microsoft-365 (10 tools) - Q1 2026 8. 🔴 zoominfo-sales (12 tools) - Q1 2026 9. 🔴 dialpad-comm (10 tools) - Q2 2026
Missing from Original Roadmap: QuickBooks (pushed to future)
Total Tools: 34 (current) → 90+ (complete)
Cost Analysis¶
Option A: Official SDKs (Recommended)¶
| Component | Annual Cost |
|---|---|
| HubSpot SDK | $0 |
| Azure SDK | $0 |
| Microsoft Graph SDK | $0 |
| ZoomInfo SDK | $0 |
| DialPad SDK | $0 |
| Total Development | $0 |
Development Time: 60-80 hours total Maintenance: ~4 hours/month across all servers Total First Year Cost: $0
Option B: Unified API (Not Viable)¶
| Component | Annual Cost |
|---|---|
| Nango/Workato | $600-6,000 |
| Custom MCP wrapper | Development time |
| Total | $600-6,000 |
Plus: - ❌ Cannot integrate with MCP (architecture mismatch) - ❌ Incomplete platform support - ❌ Less control
Verdict: ❌ Not viable
Option C: Hybrid (Optional)¶
| Component | Annual Cost |
|---|---|
| Official SDKs (5 servers) | $0 |
| Zapier (for business workflows) | $0-240 |
| Total | $0-240 |
When to add Zapier: - IF business team needs no-code workflows - IF event-driven automation needed - ONLY if justified by business need
Current status: Not needed yet ❌
Decision Matrix¶
| Criteria | Official SDKs | Unified API | Hybrid |
|---|---|---|---|
| MCP Integration | ✅ Native | ❌ Not possible | ✅ Native (SDKs) |
| Cost | ✅ $0/year | ❌ $600-6,000 | ⚠️ $0-240 |
| Control | ✅ Full | ❌ Limited | ✅ Full (SDKs) |
| Development Time | ⚠️ 60-80 hrs | ❌ N/A (can't use) | ⚠️ 60-80 hrs |
| Type Safety | ✅ Full | ⚠️ Limited | ✅ Full (SDKs) |
| Performance | ✅ Direct | ⚠️ Extra hop | ✅ Direct (SDKs) |
| Privacy | ✅ Direct | ❌ 3rd party | ✅ Direct (SDKs) |
| Platform Support | ✅ All 5 | ❌ Incomplete | ✅ All 5 |
| Maintenance | ⚠️ 4 hrs/mo | ✅ 1 hr/mo | ⚠️ 4 hrs/mo |
| Flexibility | ✅ Unlimited | ❌ Limited | ✅ Unlimited |
Winner: ✅ Official SDKs (10/10 criteria met)
Final Recommendation¶
Strategic Decision: Build Individual MCP Servers¶
Approach: Create 5 separate MCP servers using official Python SDKs
Priority Order: 1. ✅ HubSpot (DONE) - 9 tools, CRM foundation 2. 🟡 Azure (NEXT) - 15 tools, infrastructure monitoring 3. 🔴 Microsoft 365 (Q1 2026) - 10 tools, document management 4. 🔴 ZoomInfo (Q1 2026) - 12 tools, sales intelligence 5. 🔴 DialPad (Q2 2026) - 10 tools, communications
Timeline: 6 months (November 2025 - April 2026) Total Cost: $0 (all official SDKs free) Total Tools: 34 → 90+ tools
Why This Approach: 1. ✅ Zero cost: Save $600-6,000/year vs unified platforms 2. ✅ Full control: Direct API access, no limitations 3. ✅ MCP native: Purpose-built for MCP architecture 4. ✅ Type safety: Python type hints for all platforms 5. ✅ Performance: No middleware overhead 6. ✅ Privacy: Direct connections, no third party 7. ✅ Quality: Official SDKs, enterprise-grade 8. ✅ Flexibility: Add features as APIs evolve 9. ✅ Modularity: Each server independent 10. ✅ Future-proof: Not locked into vendor
When to Add iPaaS (Optional): - IF business team needs no-code workflows - IF event-driven automation needed - Recommend: Zapier ($19.99/month) when justified
Next Action: Begin Azure MCP server development (Phase 2)
Success Metrics¶
Technical Metrics¶
MCP Server Coverage: - Current: 5 servers (Memory, Trading x2, Notion, HubSpot) - Target: 9 servers (add Azure, M365, ZoomInfo, DialPad) - Progress: 56% complete (5/9)
Tool Coverage: - Current: 34 tools - Target: 90+ tools - Progress: 38% complete
API Coverage: - HubSpot: ✅ Complete (CRM APIs) - Azure: 🟡 Next (15 tools planned) - Microsoft 365: 🔴 Planned (10 tools) - ZoomInfo: 🔴 Planned (12 tools) - DialPad: 🔴 Planned (10 tools)
Business Metrics¶
Integration Value: - Sales automation: HubSpot + ZoomInfo + DialPad - Data analytics: Azure SQL + HubSpot + ZoomInfo - Document management: SharePoint + Notion - Communication: DialPad + HubSpot (call logging) - Infrastructure: Azure monitoring + cost tracking
ROI: - Cost savings: $600-6,000/year (vs unified platforms) - Time savings: AI-assisted operations across all platforms - Data quality: Cross-platform enrichment (ZoomInfo → HubSpot)
References¶
Platform Documentation¶
- HubSpot API: https://developers.hubspot.com/
- Azure SDK: https://docs.microsoft.com/python/api/
- Microsoft Graph: https://docs.microsoft.com/graph/
- ZoomInfo API: https://api-docs.zoominfo.com/
- DialPad API: https://developers.dialpad.com/
Decision Documents¶
- HubSpot Integration Evaluation: docs/decisions/2025-10-26_hubspot-integration-method-evaluation.md
- iPaaS Vendors Evaluation: docs/decisions/2025-10-26_ipaas-vendors-evaluation.md
- MCP Server Roadmap: docs/architecture/MCP_SERVER_ROADMAP.md
Implementation Files¶
- HubSpot MCP Server: tools/hubspot_mcp_server.py (DONE)
- Azure MCP Server: tools/azure_mcp_server.py (NEXT)
- Microsoft 365 MCP Server: tools/microsoft365_mcp_server.py (PLANNED)
- ZoomInfo MCP Server: tools/zoominfo_mcp_server.py (PLANNED)
- DialPad MCP Server: tools/dialpad_mcp_server.py (PLANNED)
Document Version: 1.0 Created: 2025-10-26 Purpose: Strategic planning for IT Raven multi-system integration Decision: Build 5 individual MCP servers using official SDKs Timeline: 6 months (Nov 2025 - Apr 2026) Total Cost: $0/year Next Step: Begin Azure MCP server development