check_prospect_responseLABSCO SUMMARY
One deal, five places, entered once.
The cross-platform tools are why this exists: creating a deal writes it into Sheets, Streak, Notion and Drive together, and the sync stops them drifting apart. That also sets the cost — the server holds credentials for five services at once, so scope each grant to what the pipeline actually needs.
What it is
A sales automation server that connects five systems a desk already uses — Gmail, Google Sheets, Google Drive, Streak CRM and Notion — and coordinates them, with working tools on each of the five today.
What you get
- Gmail: check prospect responses, find emails needing a follow-up, search with your own criteria, identify meeting requests, download and organise attachments
- Google Sheets: update a deal in plain language, read pipeline data with summary statistics, add new deals, apply sales formulas
- Google Drive: organise attachments by company, create structured deal folders, search documents, bulk-share files, track recently modified ones
- Streak CRM: sync Gmail threads to deals, update stages and values, create deals carrying the email context, pipeline analytics, find stale deals
- Notion: meeting notes from templates, deal status updates across databases, contact profiles built from email history, weekly reports, search
- Create a deal once and have it appear in Sheets, Streak, Notion and Drive, with bi-directional sync keeping them level
Requirements
Node 18 or newer, Claude Desktop, and an account for each service you want connected — the integrations are independent, so it runs with only the ones you use. Dropbox, Otter.ai transcript processing and automated scheduling are listed as not built yet.
Setup effort
Build from source — git clone https://github.com/hdbookie/nineteen-blocks-sales-automation-mcp
USE CASES
01
Entering a new deal without typing it four times
Create it once and it lands in Sheets, Streak, Notion and Drive, with the folder structure already made.
02
Finding out who has gone quiet
Check prospect responses in Gmail and cross-reference the stale deals in Streak rather than reading the inbox chronologically.
03
Getting attachments out of email and into the right place
Download them and file them by company in Drive automatically, instead of dragging files.
04
Preparing the Monday pipeline review
Read the pipeline with its summary statistics and have the weekly report generated in Notion.
05
Updating a deal mid-conversation
Say what changed in plain language; the update goes to Sheets and the CRM stage and value together.
06
Building a contact record worth reading
Assemble the profile in Notion from the email history rather than from what someone remembered to type in.
8 tools
Listed in project docs. Your client may show a different list.
find_follow_up_neededfind_meeting_requestssearch_emailsquick_deal_updateread_pipeline_dataadd_new_dealadd_smart_formulasBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
Node.js 18+
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
# Clone the repository
git clone https://github.com/hdbookie/nineteen-blocks-sales-automation-mcp
cd nineteen-blocks-sales-automation-mcp
# Install dependencies
npm install
# Copy and configure environment variables
cp config/.env.example config/.env
# Edit config/.env with your credentials
# Verify setup
npm run test:integrationsMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"sales-automation": {
"command": "node",
"args": [
"<YOUR_PATH_TO_NINETEEN_BLOCKS_SALES_AUTOMATION>/src/server.js"
]
}
}
}
