DragApp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DRAG_API_KEY | Yes | Your DragApp API key. Get it from DragApp settings → Integrations. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_boardsA | List all DragApp boards the user has access to. Returns board name, owner, unread count, and contributor info. |
| get_boardA | Get details of a specific DragApp board by ID. Returns board name, owner, and members. |
| list_columnsA | List all columns (stages) on a DragApp board. Columns represent workflow stages like To Do, In Progress, Done. Returns label-style IDs (e.g. "Label_1") used by list_threads, filter_threads, and move_thread. |
| list_board_membersB | List all boards with their columns and member info. Returns the main board and secondary boards with columns for each. |
| list_teamsA | List all teams the user belongs to. Returns team IDs needed by knowledge base tools (list_articles, get_article, create_article, update_article). |
| list_threadsA | List items in a specific column of a DragApp board. Call list_columns first to get column IDs — they are strings like "Label_1", not numbers. A column can mix three item types: email threads (have |
| get_threadA | Get a single email message by ID. Returns the HTML body (and a plain-text version), sender, recipients, attachments, and reply-to info for composing a response. You can pass either messageId or threadId — they are the same value. |
| reply_to_threadA | Reply to an existing email thread. Sent from the current user's connected Gmail address (the JWT owner). For single-message threads, threadId works as messageId. For multi-message threads, pass the specific messageId you're replying to — get_thread returns it. |
| send_new_emailA | Compose and send a new email from a DragApp board's connected email address. Creates a new thread in the board. |
| search_threadsA | Search items across a board by content or sender. Returns matches with preview snippets. Matches can be email threads ( |
| filter_threadsA | Filter email threads by criteria such as assignee, tags, or column. More targeted than search — use this when you know specific filter values. |
| move_threadB | Move an email thread to a different column or board. Use this to triage emails — e.g. move from Inbox to In Progress, or to a different team's board. |
| move_threads_bulkA | Move multiple email threads at once to a different column or board. Use this for batch triage operations. |
| list_cards_in_columnA | List all cards in a specific column of a DragApp board. Supports pagination. Cards are email threads or tasks with titles, assignees, due dates, and custom fields. |
| get_cardA | Get full details of a card (task or email thread) by ID. Returns title, status, assignees, due date, column, board, note, and timestamps. |
| create_cardC | Create a new card (task) on a DragApp board. You can set the title, assign it to a team member, and add a note or comment. |
| update_cardB | Update an existing card. Change the title, reassign, add a note, set a due date, or change status. Comments cannot be modified via this tool. |
| move_cardA | Move a card to a different column on the same board, or to another board. newColumnId is the label-style column ID like 'Label_1' (returned by list_columns). |
| archive_cardB | Archive (delete) a card from a DragApp board. |
| list_labelsB | List all shared labels on a board. Labels are coloured markers used to categorise and filter email threads across the team. |
| add_label_to_threadA | Add a shared label to an email thread (or task). Use list_labels first to find available label IDs for the board. |
| remove_label_from_threadC | Remove a shared label from an email thread (or task). |
| toggle_labelsA | Add some labels and/or remove others from a thread in one call. The backend toggle endpoint is one-label-at-a-time, so this iterates internally. |
| add_commentA | Add a comment to a card. Comments are internal team messages attached to cards, visible to all board members. |
| get_commentA | Retrieve a specific comment by its ID. |
| list_tagsA | List all tags (coloured labels) available on a DragApp board. Tags are used to categorise and filter cards. For email thread labels, use list_labels instead. |
| add_tag_to_cardA | Add a tag to a card. Use list_tags first to find available tag IDs for the board. |
| create_taskC | Create a standalone task in DragApp. Tasks are lightweight to-do items that can be assigned, given a due date, and tracked on a board. |
| search_contactsA | Search for contacts by name or email. The search text must not be empty. Returns matching contact records with name, email, phone, and domain. |
| get_contact_conversationsA | Get all email conversations involving a specific contact. Returns thread subjects, dates, and preview text. Use search_contacts first to find the contact ID. |
| create_contactB | Create a new contact record in DragApp with name, email, and optional phone and note. |
| list_articlesA | List all knowledge base articles for a team. Returns article titles, categories, and publication status. Use list_teams to find your team ID first. |
| get_articleA | Get the full content of a knowledge base article by ID, including title, body, category, and publication status. Use list_teams to find your team ID first. |
| create_articleA | Create a new knowledge base article. Articles can be categorised and published for team or public access. Use list_teams to find your team ID first. |
| update_articleA | Update an existing knowledge base article's title, body, or category. Use list_teams to find your team ID first. |
| search_knowledgeA | Search a Help Center knowledge base by keyword. teamId, slug, and query are all optional except query — with no teamId or slug, the first team that has a configured Help Center slug is used. |
| get_response_timesB | Get first response time metrics for a board. Shows how quickly the team responds to new emails. Useful for SLA monitoring and performance reviews. |
| get_avg_response_timeA | Get average response time across all replies on a board for a given period. Complements get_response_times which shows first response only. |
| get_daily_activityA | Get daily email activity counts for a board over a time period. Returns per-day counts useful for volume trends and workload analysis. |
| get_closed_activityA | Get the count of closed/resolved threads per day for a board. Useful for tracking team throughput and resolution rates. |
| list_automationsA | List all automations configured on a board. Shows automation name, trigger type, actions, and whether each is active. Returns an empty array if no automations exist. |
| toggle_automationA | Activate or deactivate a board automation. Pass active=true to enable or active=false to disable. |
| toggle_ai_draftsA | Enable or disable AI-generated draft replies for a board. When enabling, you must choose a category: 'automatic' (drafts created without prompting) or 'manual' (drafts created on demand). |
| get_whatsapp_conversationA | Get the full message history of a WhatsApp conversation (card) on a WhatsApp board. Returns the chat messages in order. Use the cardId returned by list_threads / search_threads on a WhatsApp board (the |
| list_whatsapp_templatesA | List the pre-approved WhatsApp message templates available on a WhatsApp board. Returns each template's name, language, status, category, body text, and how many {{n}} variables it expects. Only APPROVED templates can be sent. |
| send_whatsapp_messageA | Send a free-text WhatsApp message into an existing conversation. Note: WhatsApp only allows free-text messages inside the 24-hour customer service window; outside it, use send_whatsapp_template instead. |
| send_whatsapp_templateA | Send a pre-approved WhatsApp template message into a conversation. Use this to reach a contact outside the 24-hour window. Call list_whatsapp_templates first to get the exact template name and language, and to see how many {{n}} variables it needs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nick-timms/drag-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server