Solo Unicorn Club logo

Integration Stacks

Productivity Stack

Slack, Gmail, and Google Calendar wired together in one config

// First 7 days

What can be running fast.

01

Get a ready-to-run system that replaces blank-page setup.

02

Ship a usable package with 12 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/slack/config.json
servers/slack/auth-setup.md
servers/gmail/config.json
servers/gmail/auth-setup.md
servers/google-calendar/config.json
servers/google-calendar/auth-setup.md
docker-compose.yaml
env.example
scripts/setup.sh
scripts/test-connections.sh
README.md

Description

What is Productivity Stack?

A pre-configured bundle of MCP servers for productivity tools. Includes Slack (read/write channels, DMs, reactions), Gmail (read, compose, label, search), and Google Calendar (read events, create events, check availability). All servers tested together with shared auth scaffolding and a docker-compose for local development.

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": {
    "slack": {
      "command": "npx",
      "args": ["-y", "@mcp/slack-server"],
      "env": {
        "SLACK_BOT_TOKEN": "${SLACK_BOT_TOKEN}",
        "SLACK_TEAM_ID": "${SLACK_TEAM_ID}"
      }
    },
    "gmail": {
      "command": "npx",
      "args": ["-y", "@mcp/gmail-server"],
      "env": {
        "GMAIL_CREDENTIALS_PATH": "./credentials/gmail.json"
      }
    },
    "google-calendar": {
      "command": "npx",
      "args": ["-y", "@mcp/gcal-server"],
      "env": {
        "GCAL_CREDENTIALS_PATH": "./credentials/gcal.json"
      }
    }
  }
}

// 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