# How to integrate Slackbot MCP with Google ADK

```json
{
  "title": "How to integrate Slackbot MCP with Google ADK",
  "toolkit": "Slackbot",
  "toolkit_slug": "slackbot",
  "framework": "Google ADK",
  "framework_slug": "google-adk",
  "url": "https://composio.dev/toolkits/slackbot/framework/google-adk",
  "markdown_url": "https://composio.dev/toolkits/slackbot/framework/google-adk.md",
  "updated_at": "2026-05-12T10:26:32.742Z"
}
```

## Introduction

This guide walks you through connecting Slackbot to Google ADK using the Composio tool router. By the end, you'll have a working Slackbot agent that can send daily standup reminder to #engineering, add a custom emoji for our new logo, archive the #old-projects channel this week through natural language commands.
This guide will help you understand how to give your Google ADK agent real control over a Slackbot account through Composio's Slackbot MCP server.
Before we dive in, let's take a quick look at the key ideas and tools involved.

## Also integrate Slackbot with

- [ChatGPT](https://composio.dev/toolkits/slackbot/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/slackbot/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/slackbot/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/slackbot/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/slackbot/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/slackbot/framework/codex)
- [Cursor](https://composio.dev/toolkits/slackbot/framework/cursor)
- [VS Code](https://composio.dev/toolkits/slackbot/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/slackbot/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/slackbot/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/slackbot/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/slackbot/framework/cli)
- [LangChain](https://composio.dev/toolkits/slackbot/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/slackbot/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/slackbot/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/slackbot/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/slackbot/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get a Slackbot account set up and connected to Composio
- Install the Google ADK and Composio packages
- Create a Composio Tool Router session for Slackbot
- Build an agent that connects to Slackbot through MCP
- Interact with Slackbot using natural language

## What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.
Key features include:
- Gemini Integration: Native support for Google's Gemini models
- MCP Toolset: Built-in support for Model Context Protocol tools
- Streamable HTTP: Connect to external services through streamable HTTP
- CLI and Web UI: Run agents via command line or web interface

## What is the Slackbot MCP server, and what's possible with it?

The Slackbot MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Slackbot account. It provides structured and secure access to your Slack workspace, so your agent can automate reminders, manage conversations, add emoji reactions, organize channels, and streamline team notifications on your behalf.
- Automated reminders and notifications: Ask your agent to create timely Slack reminders for you or your team using natural language or custom schedules—never miss a deadline or meeting again.
- Message reactions and engagement: Let your agent add emoji reactions to messages, star important items, or highlight key conversations to keep team morale up and draw attention where needed.
- Channel and conversation management: Have your agent archive inactive channels, close direct messages, or organize your workspace by cleaning up conversations—all with just a simple command.
- Custom emoji and file integration: Direct your agent to add new custom emoji, set emoji aliases, or reference external files (like Google Drive docs) for richer, more expressive communication.
- Participant and workflow automation: Empower your agent to add call participants, automate onboarding flows, or handle repetitive Slack tasks to keep your team focused and productive.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `SLACKBOT_ADD_CALL_PARTICIPANTS` | Add call participants | Registers new participants added to a Slack call. |
| `SLACKBOT_ADD_REACTION_TO_AN_ITEM` | Add reaction to message | Adds a specified emoji reaction to an existing message in a Slack channel, identified by its timestamp; does not remove or retrieve reactions. |
| `SLACKBOT_ADD_A_REMOTE_FILE_FROM_A_SERVICE` | Add a remote file | Adds a reference to an external file (e.g., Google Drive, Dropbox) to Slack for discovery and sharing, requiring a unique `external_id` and an `external_url` accessible by Slack. |
| `SLACKBOT_ARCHIVE_CONVERSATION` | Archive a Slack conversation | Archives a Slack conversation by its ID, rendering it read-only and hidden while retaining history, ideal for cleaning up inactive channels; be aware that some channels (like #general or certain DMs) cannot be archived and this may impact connected integrations. |
| `SLACKBOT_CLOSE_DM` | Close conversation channel | Closes a Slack direct message (DM) or multi-person direct message (MPDM) channel, removing it from the user's sidebar without deleting history; this action affects only the calling user's view. |
| `SLACKBOT_CREATE_A_REMINDER` | Create a reminder | Creates a Slack reminder with specified text and time; time accepts Unix timestamps, seconds from now, or natural language (e.g., 'in 15 minutes', 'every Thursday at 2pm'). |
| `SLACKBOT_CREATE_CANVAS` | Create Slack Canvas | Creates a new Slack Canvas with the specified title and optional content. |
| `SLACKBOT_CREATE_CHANNEL` | Create channel | Initiates a public or private channel-based conversation in a Slack workspace. Immediately creates the channel; invoke only after explicit user confirmation. |
| `SLACKBOT_CREATE_USER_GROUP` | Create a Slack user group | Creates a new User Group (often referred to as a subteam) in a Slack workspace. |
| `SLACKBOT_CUSTOMIZE_URL_UNFURL` | Customize URL unfurl | Customizes URL previews (unfurling) in a specific Slack message using a URL-encoded JSON in `unfurls` to define custom content or remove existing previews. |
| `SLACKBOT_DELETE_CANVAS` | Delete Slack Canvas | Deletes a Slack Canvas permanently and irreversibly. Always confirm with the user before calling this tool. |
| `SLACKBOT_DELETE_FILE` | Delete a file by ID | Permanently deletes an existing file from a Slack workspace using its unique file ID; this action is irreversible and also removes any associated comments or shares. |
| `SLACKBOT_DELETE_FILE_COMMENT` | Delete file comment | Deletes a specific comment from a file in Slack; this action is irreversible. |
| `SLACKBOT_DELETE_REMINDER` | Delete a Slack reminder | Deletes an existing Slack reminder, typically when it is no longer relevant or a task is completed; this operation is irreversible. |
| `SLACKBOT_DELETES_A_MESSAGE_FROM_A_CHAT` | Delete a message from a chat | Deletes a message, identified by its channel ID and timestamp, from a Slack channel, private group, or direct message conversation; the authenticated user or bot must be the original poster. |
| `SLACKBOT_DELETE_SCHEDULED_MESSAGE` | Delete scheduled chat message | Deletes a pending, unsent scheduled message from the specified Slack channel, identified by its `scheduled_message_id`. |
| `SLACKBOT_DISABLE_USER_GROUP` | Disable a Slack user group | Disables a specified, currently enabled Slack User Group by its unique ID, effectively archiving it by setting its 'date_delete' timestamp; the group is not permanently deleted and can be re-enabled. |
| `SLACKBOT_DOWNLOAD_FILE` | Download Slack file | Tool to download Slack file content and convert it to a publicly accessible URL. Use when you need to retrieve and download files that have been shared in Slack channels or conversations. |
| `SLACKBOT_EDIT_CANVAS` | Edit Slack Canvas | Edits a Slack Canvas with granular control over content placement. Supports replace, insert (before/after/start/end) operations for flexible content management. |
| `SLACKBOT_ENABLE_PUBLIC_SHARING_OF_A_FILE` | Share file public url | Enables public sharing for an existing Slack file by generating a publicly accessible URL; this action does not create new files. Once enabled, the file is accessible to anyone with the URL — verify intent before sharing sensitive or confidential files. |
| `SLACKBOT_ENABLE_USER_GROUP` | Enable a user group | Enables a disabled User Group in Slack using its ID, reactivating it for mentions and permissions; this action only changes the enabled status and cannot create new groups or modify other properties. |
| `SLACKBOT_END_CALL` | End a call | Ends an ongoing Slack call, identified by its ID (obtained from `calls.add`), optionally specifying the call's duration. |
| `SLACKBOT_FETCH_CONVERSATION_HISTORY` | Fetch conversation history | Fetches a chronological list of messages and events from a specified Slack conversation, accessible by the authenticated user/bot, with options for pagination and time range filtering. IMPORTANT LIMITATION: This action only returns messages from the main channel timeline. Threaded replies are NOT returned by this endpoint. To retrieve threaded replies, use the SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION action (conversations.replies API) instead. The oldest/latest timestamp filters work reliably for filtering the main channel timeline, but cannot be used to retrieve individual threaded replies - even if you know the exact reply timestamp, setting oldest=latest to that timestamp will return an empty messages array. To get threaded replies: 1. Use this action to get parent messages (which include thread_ts, reply_count, latest_reply fields) 2. Use SLACK_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION with the parent's thread_ts to fetch all replies in that thread |
| `SLACKBOT_FETCH_ITEM_REACTIONS` | Fetch item reactions | Fetches reactions for a Slack message, file, or file comment. Exactly one identifier path must be provided: `channel`+`timestamp`, `file`, or `file_comment`. Mixing identifiers (e.g., providing both `channel`+`timestamp` and `file`) causes errors. If the response omits the `reactions` field, the item has zero reactions. |
| `SLACKBOT_FETCH_MESSAGE_THREAD_FROM_A_CONVERSATION` | Retrieve conversation replies | Retrieves replies to a specific parent message in a Slack conversation, using the channel ID and the parent message's timestamp (`ts`). Note: The parent message in the response contains metadata (reply_count, reply_users, latest_reply) that indicates expected thread activity. If the returned messages array contains fewer replies than reply_count indicates, check: (1) has_more=true means pagination is needed, (2) recently posted replies may have timing delays, (3) some replies may be filtered by permissions or deleted. The composio_execution_message field will warn about any detected mismatches. |
| `SLACKBOT_FETCH_TEAM_INFO` | Fetch team info | Fetches comprehensive metadata about the current Slack team, or a specified team if the provided ID is accessible. |
| `SLACKBOT_FIND_CHANNELS` | Find channels | Find channels in a Slack workspace by any criteria - name, topic, purpose, or description. Returns channel IDs (C*/G* prefixed) required by most Slack tools — always resolve names to IDs here before passing to other tools. NOTE: This action searches channels and conversations visible to the authenticated user. Empty results may indicate: - No channels match the search query in name, topic, or purpose - The target private channel or DM is not accessible to the authenticated user because they are not a member - The connection lacks required read scopes (channels:read, groups:read, im:read, mpim:read). If empty, retry with exact_match=false or exclude_archived=false to avoid false negatives. In large workspaces, paginate using next_cursor to avoid missing matches. Check 'composio_execution_message' and 'total_channels_searched' in the response for details. |
| `SLACKBOT_FIND_USER_BY_EMAIL_ADDRESS` | Lookup users by email | Retrieves the Slack user object for an active user by their registered email address; requires the users:read.email OAuth scope. Fails with 'users_not_found' if the email is unregistered, the user is inactive, the account is a guest, or the email is hidden by workspace privacy settings. |
| `SLACKBOT_FIND_USERS` | Find users | Find users in a Slack workspace by any criteria - email, name, display name, or other text. Includes optimized email lookup for exact email matches. Zero results may reflect email visibility restrictions or workspace policies, not global absence. Repeated calls may trigger HTTP 429; honor the Retry-After header. |
| `SLACKBOT_GET_BOT_USER` | Fetch bot user information | Fetches information for a specified, existing Slack bot user; will not work for regular user accounts or other integration types. |
| `SLACKBOT_GET_CALL_INFO` | Retrieve call information | Retrieves a point-in-time snapshot of a specific Slack call's information. |
| `SLACKBOT_GET_REMINDER` | Get reminder information | Retrieves detailed information for an existing Slack reminder specified by its ID; this is a read-only operation. |
| `SLACKBOT_GET_REMOTE_FILE` | Get remote file | Retrieve information about a remote file added to Slack via the files.remote API. Does not work for standard Slack-hosted file uploads. |
| `SLACKBOT_GET_TEAM_PROFILE` | Retrieve team profile details | Retrieves all profile field definitions for a Slack team, optionally filtered by visibility, to understand the team's profile structure. |
| `SLACKBOT_GET_USER_DND_STATUS` | Get team DND status | Retrieves a user's current Do Not Disturb status. |
| `SLACKBOT_GET_USER_PRESENCE` | Retrieve user presence | Retrieves a Slack user's current real-time presence (e.g., 'active', 'away') to determine their availability, noting this action does not provide historical data or status reasons. |
| `SLACKBOT_INVITE_USERS_TO_A_CHANNEL` | Invite users to a Slack channel | Invites users to an existing Slack channel using their valid Slack User IDs. Response is always HTTP 200; inspect `ok`, `error`, and `errors` fields to confirm users were added. |
| `SLACKBOT_JOIN_AN_EXISTING_CONVERSATION` | Join conversation by channel id | Joins an existing Slack conversation (public channel, private channel, or multi-person direct message) by its ID, if the authenticated user has permission. Joining an already-joined channel returns a non-fatal no-op response. Private or restricted channel joins may fail with a permission error. |
| `SLACKBOT_LEAVE_CONVERSATION` | Leave conversation channel | Leaves a Slack conversation given its channel ID; fails if leaving as the last member of a private channel or if used on a Slack Connect channel. |
| `SLACKBOT_LIST_ALL_CHANNELS` | List all channels | Lists conversations available to the user with various filters and search options. Always use resolved `channel_id` (not display names) for downstream operations, as names may be non-unique. The `created` field in results is a Unix epoch timestamp (UTC). Pagination across large workspaces may return HTTP 429 with a `Retry-After` header; honor the delay and resume from the last successful cursor. |
| `SLACKBOT_LIST_ALL_USERS` | List all users | Retrieves a paginated list of all users with profile details, status, and team memberships in a Slack workspace; data may not be real-time. Filter response fields `is_bot`, `is_app_user`, and `deleted` to build human-only rosters. Profile fields like `email` and `phone` may be absent depending on OAuth scopes and workspace privacy settings. Guest/restricted accounts may be omitted based on scopes—do not treat results as a complete directory. High-frequency calls risk HTTP 429; honor the `Retry-After` header and throttle to ~1–2 requests/second. Use stable user IDs rather than display names for mapping. Prefer SLACK_FIND_USERS for targeted lookups; cache results to avoid full-workspace fetches. |
| `SLACKBOT_LIST_CONVERSATIONS` | List conversations | List conversations (channels/DMs) accessible to a specified user (or the authenticated user if no user ID is provided), respecting shared membership for non-public channels. Returns conversation IDs (C* for channels, G* for group DMs), not display names. Absence of private channels, DMs, or MPIMs from results indicates token scope or membership limits, not that the conversation is nonexistent. |
| `SLACKBOT_LIST_CUSTOM_EMOJIS` | List team custom emojis | Retrieves all custom emojis for the Slack workspace (image URLs or aliases), not standard Unicode emojis; does not include usage statistics or creation dates. |
| `SLACKBOT_LIST_FILES_WITH_FILTERS_IN_SLACK` | List Slack files | Lists files and their metadata within a Slack workspace, filterable by user, channel, timestamp, or type; returns metadata only, not file content. Results are limited to files visible to the authenticated user — files in private channels or restricted to certain members require appropriate membership and permissions. For large workspaces, check `paging.pages` in the response to determine total pages when paginating. |
| `SLACKBOT_LIST_PINNED_ITEMS` | List pinned items in a channel | Retrieves all messages and files pinned to a specified channel; the caller must have access to this channel. |
| `SLACKBOT_LIST_REMINDERS` | List reminders | Lists all reminders with their details for the authenticated Slack user; returns an empty array if no reminders exist (valid state, not an error). Reminder text is not unique—perform client-side matching on returned objects before extracting a reminder ID for use with SLACK_DELETE_A_SLACK_REMINDER. |
| `SLACKBOT_LIST_REMOTE_FILES` | List remote files | Retrieve information about a team's remote files. |
| `SLACKBOT_LIST_USER_GROUP_MEMBERS` | List all users in a user group | Retrieves a list of all user IDs within a specified Slack user group, with an option to include users from disabled groups. |
| `SLACKBOT_LIST_USER_GROUPS` | List user groups | Lists user groups in a Slack workspace, including user-created and default groups; results for large workspaces may be paginated. |
| `SLACKBOT_LIST_USER_REACTIONS` | List user reactions | Lists all reactions added by a specific user to messages, files, or file comments in Slack, useful for engagement analysis when the item content itself is not required. Results are paginated; check `response_metadata.next_cursor` and iterate with the `cursor` parameter to retrieve complete reaction history. |
| `SLACKBOT_LOOKUP_CANVAS_SECTIONS` | Lookup Canvas Sections | Looks up section IDs in a Slack Canvas for use with targeted edit operations. Section IDs are needed for insert_after, insert_before, delete, and section-specific replace operations. |
| `SLACKBOT_OPEN_DM` | Open DM | Opens or resumes a Slack direct message (DM) or multi-person direct message (MPIM) by providing either user IDs or an existing channel ID. Returns `already_open=true` when the DM exists — treat as success and reuse the returned `channel.id` (starts with 'D') for subsequent SLACK_SEND_MESSAGE calls; passing a username, email, or user ID directly to SLACK_SEND_MESSAGE causes `channel_not_found`. Avoid redundant calls when an existing DM channel ID is available. |
| `SLACKBOT_PIN_ITEM` | Pin an item to a channel | Pins a message to a specified Slack channel; the message must not already be pinned. |
| `SLACKBOT_REMOVE_CALL_PARTICIPANTS` | Remove call participants | Registers participants removed from a Slack call. |
| `SLACKBOT_REMOVE_REACTION_FROM_ITEM` | Remove reaction from item | Removes an emoji reaction from a message, file, or file comment in Slack. Provide exactly one targeting method: channel+timestamp together, file, or file_comment. Mixing methods or omitting all returns invalid_arguments. |
| `SLACKBOT_REMOVE_REMOTE_FILE` | Remove remote file | Removes the Slack reference to an external file (which must have been previously added via the remote files API), specified by either its `external_id` or `file` ID (one of which is required), without deleting the actual external file. |
| `SLACKBOT_REMOVE_USER_FROM_CONVERSATION` | Remove user from conversation | Removes a specified user from a Slack conversation (channel); the caller must have permissions to remove users and cannot remove themselves using this action. |
| `SLACKBOT_RENAME_CONVERSATION` | Rename a conversation | Renames a Slack channel, automatically adjusting the new name to meet naming conventions (e.g., converting to lowercase), which may affect integrations using the old name. |
| `SLACKBOT_RETRIEVE_CONVERSATION_INFORMATION` | Retrieve conversation information | Retrieves metadata for a Slack conversation by ID (e.g., name, purpose, creation date, with options for member count/locale), excluding message content. The `channel` parameter is effectively required. Private channels, DMs, or channels where the app lacks membership may return restricted data; check `is_archived` and `is_member` fields in the response to diagnose access issues. Bulk lookups may trigger HTTP 429 rate limiting; honor the `Retry-After` response header. |
| `SLACKBOT_RETRIEVE_CONVERSATION_MEMBERS_LIST` | Get conversation members | Retrieves a paginated list of active member IDs (not names, emails, or presence) for a specified Slack public channel, private channel, DM, or MPIM. Returns only user IDs; use a user-lookup tool to enrich member data. |
| `SLACKBOT_RETRIEVE_CURRENT_USER_DND_STATUS` | Retrieve user DND status | Retrieves a Slack user's current Do Not Disturb (DND) status to determine their availability before interaction; any specified user ID must be a valid Slack user ID. |
| `SLACKBOT_RETRIEVE_DETAILED_INFORMATION_ABOUT_A_FILE` | Retrieve detailed file information | Retrieves detailed metadata and paginated comments for a specific Slack file ID; does not download file content. |
| `SLACKBOT_RETRIEVE_DETAILED_USER_INFORMATION` | Retrieve detailed user information | Retrieves comprehensive information for a valid Slack user ID, excluding message history and channel memberships. Sensitive fields like `email` and `phone` require the `users:read.email` scope and may be silently omitted based on workspace privacy policies. |
| `SLACKBOT_RETRIEVE_USER_PROFILE_INFORMATION` | Retrieve user profile information | Retrieves profile information for a specified Slack user (defaults to the authenticated user if `user` ID is omitted); a provided `user` ID must be valid. Sensitive fields like email and phone may be silently omitted if required scopes (e.g., `users:read.email`) are not granted or workspace privacy policies restrict access. |
| `SLACKBOT_REVOKE_FILE_PUBLIC_SHARING` | Revoke a file's public url | Revokes a Slack file's public URL, making it private; this is a no-op if not already public and is irreversible. |
| `SLACKBOT_SCHEDULE_MESSAGE` | Schedule message | Schedules a message to a Slack channel, DM, or private group for a future time (`post_at`), requiring `text`, `blocks`, or `attachments` for content; scheduling is limited to 120 days in advance. |
| `SLACKBOT_SEARCH_ALL` | Search all content | Tool to search all messages and files. Use when you need unified content search across channels and files in one call. Results are scoped to content visible to the authenticated token; missing hits in private or restricted channels reflect permission/membership gaps. Response separates messages and files into distinct sections — explicitly read the files section for document results. Results are index-based and may lag several minutes behind real-time; use SLACK_FETCH_CONVERSATION_HISTORY for near-real-time per-channel coverage. Paginated searches exceeding ~1 req/sec may return HTTP 429 too_many_requests; honor the Retry-After header and resume from the last page. |
| `SLACKBOT_SEARCH_MESSAGES` | Search messages | Workspace‑wide Slack message search with date ranges and filters. Use `query` modifiers (e.g., in:#channel, from:@user, before/after:YYYY-MM-DD), sorting (score/timestamp), and pagination. |
| `SLACKBOT_SEND_EPHEMERAL_MESSAGE` | Send ephemeral message | Sends an ephemeral message visible only to the specified `user` in a channel; other channel members cannot see it. Both the bot and the target user must be members of the specified channel. |
| `SLACKBOT_SEND_ME_MESSAGE` | Share a me message in a channel | Sends a 'me message' (e.g., '/me is typing') to a Slack channel, where it's displayed as a third-person user action; messages are plain text and the channel must exist and be accessible. |
| `SLACKBOT_SEND_MESSAGE` | Send message | Posts a message to a Slack channel, DM, or private group; requires at least one content field (`markdown_text`, `text`, `blocks`, or `attachments`) — omitting all causes a `no_text` error. Fails with `not_in_channel`, `channel_not_found`, or `channel_is_archived` if the bot lacks access. Body limit ~4000 characters. Rate-limited at ~1 req/sec (HTTP 429, honor `Retry-After`). Not idempotent — duplicate calls post duplicate messages. |
| `SLACKBOT_SET_CONVERSATION_PURPOSE` | Set a conversation's purpose | Sets the purpose (a short description of its topic/goal, displayed in the header) for a Slack conversation; the calling user must be a member. |
| `SLACKBOT_SET_READ_CURSOR_IN_A_CONVERSATION` | Set conversation read cursor | Marks a message, specified by its timestamp (`ts`), as the most recently read for the authenticated user in the given `channel`, provided the user is a member of the channel and the message exists within it. |
| `SLACKBOT_SET_THE_TOPIC_OF_A_CONVERSATION` | Set conversation topic | Sets or updates the topic for a specified Slack conversation. |
| `SLACKBOT_SET_USER_PRESENCE` | Set user presence | Manually sets a user's Slack presence, overriding automatic detection; this setting persists across connections but can be overridden by user actions or Slack's auto-away (e.g., after 10 mins of inactivity). |
| `SLACKBOT_SHARE_REMOTE_FILE` | Share a remote file in channels | Shares a remote file, which must already be registered with Slack, into specified Slack channels or direct message conversations. |
| `SLACKBOT_START_CALL` | Start call | Registers a new call in Slack using `calls.add` for third-party call integration; `created_by` is required if not using a user-specific token. |
| `SLACKBOT_UNARCHIVE_CHANNEL` | Unarchive channel | Reverses conversation archival. |
| `SLACKBOT_UNPIN_ITEM` | Unpin message from channel | Unpins a message, identified by its timestamp, from a specified channel if the message is currently pinned there; this operation is destructive. |
| `SLACKBOT_UPDATE_CALL_INFO` | Update call information | Updates the title, join URL, or desktop app join URL for an existing Slack call identified by its ID. |
| `SLACKBOT_UPDATE_REMOTE_FILE` | Update an existing remote file | Updates metadata or content details for an existing remote file in Slack; this action cannot upload new files or change the fundamental file type. |
| `SLACKBOT_UPDATES_A_MESSAGE` | Update a Slack message | Updates a Slack message, identified by `channel` ID and `ts` timestamp, by modifying its `text`, `attachments`, or `blocks`; provide at least one content field, noting `attachments`/`blocks` are replaced if included (`[]` clears them). |
| `SLACKBOT_UPDATE_USER_GROUP` | Update Slack user group | Updates an existing Slack User Group, which must be specified by an existing `usergroup` ID, with new optional details such as its name, description, handle, or default channels. |
| `SLACKBOT_UPDATE_USER_GROUP_MEMBERS` | Update user group members | Replaces all members of an existing Slack User Group with a new list of valid user IDs. |
| `SLACKBOT_UPLOAD_OR_CREATE_A_FILE_IN_SLACK` | Upload or create a file in Slack | Upload files, images, screenshots, documents, or any media to Slack channels or threads. Supports all file types including images (PNG, JPG, JPEG, GIF), documents (PDF, DOCX, TXT), code files, and more. Can share files publicly in channels or as thread replies with optional comments. Large files may fail with `upload_too_large`; use SLACK_ADD_A_REMOTE_FILE_FROM_A_SERVICE for large uploads. If the API returns `ok=false` with `method_deprecated`, fall back to SLACK_ADD_A_REMOTE_FILE_FROM_A_SERVICE or SLACK_SEND_MESSAGE with a URL. |

## Supported Triggers

| Trigger slug | Name | Description |
|---|---|---|
| `SLACKBOT_CHANNEL_CREATED` | New Channel Created Trigger | Triggered when a new channel is created in Slack. |
| `SLACKBOT_CHANNEL_MESSAGE_RECEIVED` | Channel Message Received | Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages. |
| `SLACKBOT_DIRECT_MESSAGE_RECEIVED` | Direct Message Received | Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels. |
| `SLACKBOT_MESSAGE_REACTION_ADDED` | Message Reaction Added | Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name. |
| `SLACKBOT_REACTION_ADDED` | Reaction Added Trigger | DEPRECATED: use `SLACK_MESSAGE_REACTION_ADDED` instead. Triggered when a reaction is added to a message in Slack. |
| `SLACKBOT_REACTION_REMOVED` | Reaction Removed Trigger | DEPRECATED. Triggered when a reaction is removed from a message. |
| `SLACKBOT_RECEIVE_BOT_MESSAGE` | New Bot Message Received Trigger | DEPRECATED: use `SLACK_CHANNEL_MESSAGE_RECEIVED` with `is_bot_message=true` instead. Triggered when a new bot message is posted to a Slack channel. |
| `SLACKBOT_RECEIVE_MESSAGE` | New Message Received Trigger | DEPRECATED: use `SLACK_CHANNEL_MESSAGE_RECEIVED` instead. Triggered when a new message is posted to a Slack channel. |

## Creating MCP Server - Stand-alone vs Composio SDK

The Slackbot MCP server is an implementation of the Model Context Protocol that connects your AI agent to Slackbot. It provides structured and secure access so your agent can perform Slackbot operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- A Google API key for Gemini models
- A Composio account and API key
- Python 3.9 or later installed
- Basic familiarity with Python

### 1. Getting API Keys for Google and Composio

Google API Key
- Go to [Google AI Studio](https://aistudio.google.com/app/apikey) and create an API key.
- Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
- Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.

### 2. Install dependencies

Inside your virtual environment, install the required packages.
What's happening:
- google-adk is Google's Agents Development Kit
- composio connects your agent to Slackbot via MCP
- python-dotenv loads environment variables
```bash
pip install google-adk composio python-dotenv
```

### 3. Set up ADK project

Set up a new Google ADK project.
What's happening:
- This creates an agent folder with a root agent file and .env file
```bash
adk create my_agent
```

### 4. Set environment variables

Save all your credentials in the .env file.
What's happening:
- GOOGLE_API_KEY authenticates with Google's Gemini models
- COMPOSIO_API_KEY authenticates with Composio
- COMPOSIO_USER_ID identifies the user for session management
```bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email
```

### 5. Import modules and validate environment

What's happening:
- os reads environment variables
- Composio is the main Composio SDK client
- GoogleProvider declares that you are using Google ADK as the agent runtime
- Agent is the Google ADK LLM agent class
- McpToolset lets the ADK agent call MCP tools over HTTP
```python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")
```

### 6. Create Composio client and Tool Router session

What's happening:
- Authenticates to Composio with your API key
- Declares Google ADK as the provider
- Spins up a short-lived MCP endpoint for your user and selected toolkit
- Stores the MCP HTTP URL for the ADK MCP integration
```python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["slackbot"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
```

### 7. Set up the McpToolset and create the Agent

What's happening:
- Connects the ADK agent to the Composio MCP endpoint through McpToolset
- Uses Gemini as the model powering the agent
- Lists exact tool names in instruction to reduce misnamed tool calls
```python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Slackbot operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
```

### 8. Run the agent

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.
What's happening:
- adk run runs the agent in CLI mode
- adk web . opens a web UI for interactive testing
```bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web
```

## Complete Code

```python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["slackbot"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Slackbot operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
```

## Conclusion

You've successfully integrated Slackbot with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Slackbot using natural language commands.
Key takeaways:
- The Tool Router approach dynamically routes requests to the appropriate Slackbot tools
- Environment variables keep your credentials secure and separate from code
- Clear agent instructions reduce tool calling errors
- The ADK web UI provides an interactive interface for testing and development
You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

## How to build Slackbot MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/slackbot/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/slackbot/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/slackbot/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/slackbot/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/slackbot/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/slackbot/framework/codex)
- [Cursor](https://composio.dev/toolkits/slackbot/framework/cursor)
- [VS Code](https://composio.dev/toolkits/slackbot/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/slackbot/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/slackbot/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/slackbot/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/slackbot/framework/cli)
- [LangChain](https://composio.dev/toolkits/slackbot/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/slackbot/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/slackbot/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/slackbot/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/slackbot/framework/crew-ai)

## Related Toolkits

- [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable.
- [Outlook](https://composio.dev/toolkits/outlook) - Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management.
- [Slack](https://composio.dev/toolkits/slack) - Slack is a channel-based messaging platform for teams and organizations. It helps people collaborate in real time, share files, and connect all their tools in one place.
- [Gong](https://composio.dev/toolkits/gong) - Gong is a platform for video meetings, call recording, and team collaboration. It helps teams capture conversations, analyze calls, and turn insights into action.
- [Microsoft teams](https://composio.dev/toolkits/microsoft_teams) - Microsoft Teams is a collaboration platform that combines chat, meetings, and file sharing within Microsoft 365. It keeps distributed teams connected and productive through seamless virtual communication.
- [2chat](https://composio.dev/toolkits/_2chat) - 2chat is an API platform for WhatsApp and multichannel text messaging. It streamlines chat automation, group management, and real-time messaging for developers.
- [Agent mail](https://composio.dev/toolkits/agent_mail) - Agent mail provides AI agents with dedicated email inboxes for sending, receiving, and managing emails. It empowers agents to communicate autonomously with people, services, and other agents—no human intervention needed.
- [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place.
- [Chatwork](https://composio.dev/toolkits/chatwork) - Chatwork is a team communication platform with group chats, file sharing, and task management. It helps businesses boost collaboration and streamline productivity.
- [Clickmeeting](https://composio.dev/toolkits/clickmeeting) - ClickMeeting is a cloud-based platform for running online meetings and webinars. It helps businesses and individuals host, manage, and engage virtual audiences with ease.
- [Confluence](https://composio.dev/toolkits/confluence) - Confluence is Atlassian's team collaboration and knowledge management platform. It helps your team organize, share, and update documents and project content in one secure workspace.
- [Dailybot](https://composio.dev/toolkits/dailybot) - DailyBot streamlines team collaboration with chat-based standups, reminders, and polls. It keeps work flowing smoothly in your favorite messaging platforms.
- [Dialmycalls](https://composio.dev/toolkits/dialmycalls) - Dialmycalls is a mass notification service for sending voice and text messages to contacts. It helps teams and organizations quickly broadcast urgent alerts and updates.
- [Dialpad](https://composio.dev/toolkits/dialpad) - Dialpad is a cloud-based business phone and contact center system for teams. It unifies voice, video, messaging, and meetings across your devices.
- [Discord](https://composio.dev/toolkits/discord) - Discord is a real-time messaging and VoIP platform for communities and teams. It lets users chat, share media, and collaborate across public and private channels.
- [Discordbot](https://composio.dev/toolkits/discordbot) - Discordbot is an automation tool for Discord servers that handles moderation, messaging, and user engagement. It helps communities run smoothly by automating routine and complex tasks.
- [Echtpost](https://composio.dev/toolkits/echtpost) - Echtpost is a secure digital communication platform for encrypted document and message exchange. It ensures confidential data stays private and protected during transmission.
- [Egnyte](https://composio.dev/toolkits/egnyte) - Egnyte is a cloud-based platform for secure file sharing, storage, and governance. It helps teams collaborate efficiently while maintaining data compliance and security.
- [Google Meet](https://composio.dev/toolkits/googlemeet) - Google Meet is a secure video conferencing platform for virtual meetings, chat, and screen sharing. It helps teams connect, collaborate, and communicate seamlessly from anywhere.
- [Heartbeat](https://composio.dev/toolkits/heartbeat) - Heartbeat is a plug-and-play platform for building and managing online communities. It helps you organize users, channels, events, and discussions in one place.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Slackbot MCP?

With a standalone Slackbot MCP server, the agents and LLMs can only access a fixed set of Slackbot tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Slackbot and many other apps based on the task at hand, all through a single MCP endpoint.

### Can I use Tool Router MCP with Google ADK?

Yes, you can. Google ADK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Slackbot tools.

### Can I manage the permissions and scopes for Slackbot while using Tool Router?

Yes, absolutely. You can configure which Slackbot scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

### How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Slackbot data and credentials are handled as safely as possible.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)