Back to Home

mcp-marketing-sales

Verified Safe

by JEflyer

Overview

A comprehensive Marketing and Sales automation suite providing tools for CRM, analytics, task management, invoicing, payments, document management, and various communication channels (email, SMS, calls).

Installation

Run Command
docker-compose up --build

Environment Variables

  • POSTGRES_USER
  • POSTGRES_PASSWORD
  • POSTGRES_DB
  • DATABASE_URL
  • DEMO_MODE
  • DEMO_MODE_CONFIRMED
  • GMAIL_CLIENT_ID
  • GMAIL_CLIENT_SECRET
  • GMAIL_REFRESH_TOKEN
  • TWILIO_ACCOUNT_SID
  • TWILIO_AUTH_TOKEN
  • TWILIO_PHONE_NUMBER
  • GOOGLE_CALENDAR_CLIENT_ID
  • GOOGLE_CALENDAR_CLIENT_SECRET
  • GOOGLE_CALENDAR_REFRESH_TOKEN
  • STRIPE_SECRET_KEY
  • STRIPE_WEBHOOK_SECRET
  • S3_BUCKET
  • S3_ENDPOINT
  • S3_ACCESS_KEY
  • S3_SECRET_KEY
  • DOCUMENTS_STORAGE_PATH
  • MCP_API_KEY_HASH
  • MCP_API_USER_ID
  • MCP_API_PERMISSIONS
  • ENCRYPTION_SECRET
  • ENCRYPTION_SALT
  • RATE_LIMIT_ENABLED
  • RATE_LIMIT_WINDOW_MS
  • RATE_LIMIT_MAX_REQUESTS

Security Notes

The server suite uses environment variables for sensitive API keys (Google, Twilio, Stripe, AWS S3), which is a good practice for secrets management. Input validation is performed using Zod schemas for all tool inputs. The `safeTemplateSubstitute` function in the SMS server explicitly avoids regex on user-supplied input to prevent ReDoS attacks. A `DEMO_MODE` is implemented to bypass actual external API calls and use mock data, which is beneficial for testing and development without live credentials. However, the `docker-compose.yml` utilizes default, weak PostgreSQL credentials that are exposed and critically must be overridden for any production deployment. Improper management of the numerous external API keys required for full functionality could lead to security vulnerabilities.

Similar Servers

Stats

Interest Score0
Security Score9
Cost ClassMedium
Avg Tokens500
Stars0
Forks0
Last Update2025-11-27

Tags

CRMSalesMarketingAnalyticsCommunication