Engineering teams

Daily standup from Trello, Slack, and Gmail

Summarize yesterday's board movement, Slack threads, and inbox follow-ups into one standup draft without switching tools.

Outcome: A ready-to-post standup update sourced from Trello cards, Slack channels, and Gmail threads

Integrations in this workflow

Trello

Slack

Gmail

Example questions

Try asking your AI client

Using my private gateway, prepare today's standup for the Platform Trello board. List cards I moved yesterday, summarize unresolved Slack threads in #engineering from the last 24 hours, and flag Gmail messages I still owe replies on. Output bullets for Done, Today, and Blockers.
Look at the Platform Trello board, #engineering Slack, and my Gmail inbox together. Which customer issues are on a card, still discussed in Slack, and sitting unanswered in email?
Build a Friday retro from Trello cards I completed this week, Slack decisions in #engineering, and Gmail threads I closed. Keep it short enough to paste into Slack - do not send it.
I am blocked on the login timeout. Check the Trello card, the related Slack thread, and any Gmail from Jack about it. Tell me what is missing before I can move the card.
Draft tomorrow's focus list: three Trello cards I should pull, Slack threads I must answer, and Gmail follow-ups that cannot wait. Do not move cards or send messages.

The problem

Standups scatter context across Trello cards, Slack threads, and email. Copy-pasting between apps burns time and drops details.

Gateway tools

Use namespaced tools on the private gateway:

trello__list_boards → trello__list_cards for active work
slack__list_channels → slack__list_messages for channel history
gmail__list_messages → gmail__get_message for follow-ups

Start with list-services-tool if you are unsure which integrations are active.

Governance

Scope Slack channel access with Allowed channels during OAuth connect — agents should not read private channels you did not approve.
Gmail and Trello calls are audited per workspace; review Audit logs before sharing standup output externally.
Prefer read-only tool calls for drafting; ask before sending Slack messages or emails on your behalf.

Connect via private gateway

Activate the integrations above, create an API token scoped to mcp:private-gateway, then add this config to your MCP client.

Config file: ~/.cursor/mcp.json

{
    "mcpServers": {
        "stackgate-private-gateway": {
            "url": "https://stackgate.ai/mcp/private",
            "headers": {
                "Authorization": "Bearer YOUR_API_TOKEN"
            }
        }
    }
}