# How to integrate Timelinesai MCP with Google ADK ```json { "title": "How to integrate Timelinesai MCP with Google ADK", "toolkit": "Timelinesai", "toolkit_slug": "timelinesai", "framework": "Google ADK", "framework_slug": "google-adk", "url": "https://composio.dev/toolkits/timelinesai/framework/google-adk", "markdown_url": "https://composio.dev/toolkits/timelinesai/framework/google-adk.md", "updated_at": "2026-05-12T10:28:34.037Z" } ``` ## Introduction This guide walks you through connecting Timelinesai to Google ADK using the Composio tool router. By the end, you'll have a working Timelinesai agent that can get the last 10 messages from sales chat, list all unread whatsapp chats assigned to me, create webhook for new incoming messages through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a Timelinesai account through Composio's Timelinesai MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Timelinesai with - [OpenAI Agents SDK](https://composio.dev/toolkits/timelinesai/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/timelinesai/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/timelinesai/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/timelinesai/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/timelinesai/framework/codex) - [OpenClaw](https://composio.dev/toolkits/timelinesai/framework/openclaw) - [Hermes](https://composio.dev/toolkits/timelinesai/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/timelinesai/framework/cli) - [LangChain](https://composio.dev/toolkits/timelinesai/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/timelinesai/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/timelinesai/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/timelinesai/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/timelinesai/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get a Timelinesai account set up and connected to Composio - Install the Google ADK and Composio packages - Create a Composio Tool Router session for Timelinesai - Build an agent that connects to Timelinesai through MCP - Interact with Timelinesai 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 Timelinesai MCP server, and what's possible with it? The Timelinesai MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Timelinesai account. It provides structured and secure access to your WhatsApp communications, so your agent can retrieve chat messages, manage files, automate webhook workflows, and keep your team’s communication organized—all on your behalf. - WhatsApp chat management: Fetch recent or historical messages from specific chats, or list all active and unread chats to help you stay on top of conversations. - Automated webhook integration: Set up, review, or delete webhook subscriptions to automate notifications and keep your workflows synced across tools. - File and attachment handling: List uploaded files, retrieve file details or secure download links, and delete files when they’re no longer needed. - WhatsApp account verification: Quickly list and verify all WhatsApp accounts connected to your workspace for streamlined onboarding and troubleshooting. - Workspace insight and cleanup: Get a comprehensive view of all webhooks or uploaded files, making workspace management and housekeeping a breeze. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `TIMELINESAI_DELETE_FILE` | Delete File | Tool to delete an uploaded file by its UID. Use after confirming the file is no longer needed. | | `TIMELINESAI_DELETE_WEBHOOK` | Delete Webhook | Tool to delete a webhook subscription by its ID. Use when you need to remove an existing webhook after confirming the webhook ID. Example: "Delete the webhook with ID '9f6a8c3d-56b7-4a1e-8f2e-abcdef123456'." | | `TIMELINESAI_GET_CHAT_MESSAGES` | Get Chat Messages | Tool to get messages from a specific chat in TimelinesAI. Use when you need to retrieve message history or recent messages from a chat. Example: "Get the last 20 messages from chat 'chat_123abc'." | | `TIMELINESAI_GET_CHATS` | Get Chats | Tool to get full or filtered list of all chats. Use when you need to browse or search chats with optional filters. Example: "List all unread chats assigned to me." | | `TIMELINESAI_GET_FILE_DETAILS` | Get File Details | Tool to retrieve metadata and temporary download URL for an uploaded file. Use after uploading a file or when needing its URL. | | `TIMELINESAI_GET_WEBHOOK` | Get Webhook | Retrieves detailed information about a specific webhook subscription by its ID. Use this action to: - Check webhook configuration (URL, event type, enabled status) - Monitor webhook health (error counter) - Verify webhook existence before updating or deleting Prerequisites: You must have a valid webhook ID. Use the Get Webhooks action to list all available webhooks first. | | `TIMELINESAI_GET_WEBHOOKS` | Get Webhooks | Retrieves all webhook subscriptions configured for the workspace. Webhooks notify external systems about events (e.g., 'message:new', 'chat:new') in real-time. Use this to view existing webhook configurations, check their status, or retrieve webhook IDs for updates/deletion. Supports optional pagination via limit and offset parameters. | | `TIMELINESAI_GET_WHATSAPP_ACCOUNTS` | Get WhatsApp Accounts | Tool to list all WhatsApp accounts connected to the workspace. Use after configuring WhatsApp integration to verify accounts. | | `TIMELINESAI_LIST_UPLOADED_FILES` | List Uploaded Files | Tool to list files uploaded in your TimelinesAI workspace. Use when you need to retrieve all uploaded files. | | `TIMELINESAI_POST_MESSAGE` | Send WhatsApp Message to Number | Tool to send a WhatsApp text message to a phone number via TimelinesAI. Use this to send messages to any recipient phone number using one of your connected WhatsApp accounts as the sender. The message will be delivered immediately if the recipient number is reachable on WhatsApp. Example: Send 'Hello, how can I help you today?' from +15105566777 to +14151231234. | | `TIMELINESAI_POST_WEBHOOK` | Create Webhook Subscription | Tool to create a new webhook subscription. Use when you have the event type and callback URL ready. | | `TIMELINESAI_PUT_WEBHOOK` | Update Webhook | Tool to update an existing webhook subscription. Use after confirming the webhook ID when you need to change the URL, subscribed event types, or enable/disable a webhook. | | `TIMELINESAI_SEND_MESSAGE` | Send Message to Chat | Send a WhatsApp message to an existing chat in TimelinesAI. Use this action when you have a chat ID from the Get Chats action and want to send a message to that conversation. For sending messages to new phone numbers (not existing chats), use the 'Send WhatsApp Message to Number' action instead. Example: "Send message 'Hello world' to chat with ID 'chat_123abc'." | ## Supported Triggers | Trigger slug | Name | Description | |---|---|---| | `TIMELINESAI_NEW_MESSAGE_RECEIVED` | New WhatsApp Message Received | Polling trigger that monitors for new messages received in TimelinesAI WhatsApp chats. | ## Creating MCP Server - Stand-alone vs Composio SDK The Timelinesai MCP server is an implementation of the Model Context Protocol that connects your AI agent to Timelinesai. It provides structured and secure access so your agent can perform Timelinesai 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 Timelinesai 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=["timelinesai"], ) 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 Timelinesai 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=["timelinesai"], ) 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 Timelinesai operations." ), tools=[composio_toolset], ) print("\nAgent setup complete. You can now run this agent directly ;)") ``` ## Conclusion You've successfully integrated Timelinesai with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Timelinesai using natural language commands. Key takeaways: - The Tool Router approach dynamically routes requests to the appropriate Timelinesai 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 Timelinesai MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/timelinesai/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/timelinesai/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/timelinesai/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/timelinesai/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/timelinesai/framework/codex) - [OpenClaw](https://composio.dev/toolkits/timelinesai/framework/openclaw) - [Hermes](https://composio.dev/toolkits/timelinesai/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/timelinesai/framework/cli) - [LangChain](https://composio.dev/toolkits/timelinesai/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/timelinesai/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/timelinesai/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/timelinesai/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/timelinesai/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. - [Slackbot](https://composio.dev/toolkits/slackbot) - Slackbot is a conversational automation tool for Slack that handles reminders, notifications, and automated responses. It boosts team productivity by streamlining onboarding, answering FAQs, and managing timely alerts—all right inside Slack. - [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. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Timelinesai MCP? With a standalone Timelinesai MCP server, the agents and LLMs can only access a fixed set of Timelinesai tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Timelinesai 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 Timelinesai tools. ### Can I manage the permissions and scopes for Timelinesai while using Tool Router? Yes, absolutely. You can configure which Timelinesai 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 Timelinesai data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)