Solo Unicorn Club logo

Integration Stacks

Sales Stack

HubSpot, Calendly, and email wired for CRM-driven outreach

revops teamsSDR managersfounders running outbound

Why buy

Revenue teams buy integrations when they remove coordination debt across the stack they already pay for.

// First 7 days

What can be running fast.

01

sync CRM actions

02

Ship a usable package with 13 included files and working structure.

03

Move from purchase to first setup in about 10 min.

// Included files

What is inside the package.

mcp-servers.json
servers/hubspot/config.json
servers/hubspot/auth-setup.md
servers/hubspot/permissions.md
servers/calendly/config.json
servers/calendly/auth-setup.md
servers/email/config.json
servers/email/auth-setup.md
docker-compose.yaml
env.example
scripts/setup.sh
scripts/test-connections.sh
README.md

Description

What is Sales Stack?

MCP servers: HubSpot (contacts, deals, pipelines), Calendly (scheduling), and email (outreach). Scoped permissions for CRM read/write.

solo-unicornclaude-code

Upgrade path

  • 01Start with this package and validate the workflow.
  • 02Add specialized skills or bundles once the core system is stable.
  • 03Use the community to sharpen positioning, demos, and feedback loops.
Previewmcp-servers.json
// mcp-servers.json
{
  "mcpServers": {
    "hubspot": {
      "command": "npx",
      "args": ["-y", "@mcp/hubspot-server"],
      "env": {
        "HUBSPOT_ACCESS_TOKEN": "${HUBSPOT_ACCESS_TOKEN}",
        "HUBSPOT_PORTAL_ID": "${HUBSPOT_PORTAL_ID}"
      }
    },
    "calendly": {
      "command": "npx",
      "args": ["-y", "@mcp/calendly-server"],
      "env": {
        "CALENDLY_API_KEY": "${CALENDLY_API_KEY}"
      }
    },
    "email": {
      "command": "npx",
      "args": ["-y", "@mcp/email-server"],
      "env": {
        "SMTP_HOST": "${SMTP_HOST}",
        "SMTP_USER": "${SMTP_USER}",
        "SMTP_PASS": "${SMTP_PASS}"
      }
    }
  }
}

// Community acceleration

Use the room after the purchase.

Bring your workflow into the Solo Unicorn community for sharper feedback, operator critique, and more visibility once the system is live.

Discuss implementation