The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the DragApp MCP Server listing page.
An MCP server for DragApp — AI-powered email & WhatsApp for teams. Read and reply to emails, send WhatsApp messages, search threads, manage boards, and more from Claude, ChatGPT, Cursor, or any MCP-compatible AI tool.
Add this URL as a custom connector:
When you connect, a Drag page opens and asks for your API key once (DragApp → Settings → Integrations). The key is verified and handed to your client as its access token; the service stores nothing, and the connect flow never puts your key in a URL. Works in any client that supports remote MCP connectors (OAuth 2.1 + PKCE, dynamic client registration). Nothing to install.
Go to DragApp → Settings → Integrations → copy your API key.
Claude Desktop — add to ~/Library/Application Support/Claude/claude_desktop_config.json:
Cursor — add to .cursor/mcp.json:
Works with any MCP-compatible client — ChatGPT, Windsurf, Claude Code, etc.
Ask your AI assistant:
list_threads · get_thread · reply_to_thread · send_new_email · search_threads · filter_threads · move_thread · move_threads_bulk
list_boards · get_board · list_columns · list_board_members · list_teams
list_cards_in_column · get_card · create_card · update_card · move_card · archive_card
list_labels · add_label_to_thread · remove_label_from_thread · toggle_labels
search_contacts · get_contact_conversations · create_contact
list_articles · get_article · create_article · update_article · search_knowledge
get_response_times · get_avg_response_time · get_daily_activity · get_closed_activity
list_automations · toggle_automation · toggle_ai_drafts
send_whatsapp_message · send_whatsapp_template · list_whatsapp_templates · get_whatsapp_conversation
add_comment · get_comment
list_tags · add_tag_to_card
create_task
47 tools across 12 categories.
This is a public repository. Before committing, install the pre-commit hook so gitleaks scans your staged changes for secrets (keys, JWTs, tokens):
Run it manually against everything at any time:
The hook uses .gitleaks.toml. The same scan runs in CI on every
push and pull request (.github/workflows/secret-scan.yml), and npm publish runs a
tarball guard (scripts/check-tarball.mjs) that blocks the release if the built
package contains any known-sensitive term.
MIT