# How to integrate Timely MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Timely MCP with Vercel AI SDK v6", "toolkit": "Timely", "toolkit_slug": "timely", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/timely/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/timely/framework/ai-sdk.md", "updated_at": "2026-05-12T10:28:37.961Z" } ``` ## Introduction This guide walks you through connecting Timely to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Timely agent that can get your timely account billing details, set up webhook for new time entries, retrieve account info for client project through natural language commands. This guide will help you understand how to give your Vercel AI SDK agent real control over a Timely account through Composio's Timely MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Timely with - [OpenAI Agents SDK](https://composio.dev/toolkits/timely/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/timely/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/timely/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/timely/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/timely/framework/codex) - [OpenClaw](https://composio.dev/toolkits/timely/framework/openclaw) - [Hermes](https://composio.dev/toolkits/timely/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/timely/framework/cli) - [Google ADK](https://composio.dev/toolkits/timely/framework/google-adk) - [LangChain](https://composio.dev/toolkits/timely/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/timely/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/timely/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/timely/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Timely integration - Using Composio's Tool Router to dynamically load and access Timely tools - Creating an MCP client connection using HTTP transport - Building an interactive CLI chat interface with conversation history management - Handling tool calls and results within the Vercel AI SDK framework ## What is Vercel AI SDK? The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state. Key features include: - streamText: Core function for streaming responses with real-time tool support - MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp - Step Counting: Control multi-step tool execution with stopWhen: stepCountIs() - OpenAI Provider: Native integration with OpenAI models ## What is the Timely MCP server, and what's possible with it? The Timely MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Timely account. It provides structured and secure access to your time-tracking data, so your agent can perform actions like retrieving account information, managing webhooks, and integrating time logs with other workflows on your behalf. - Account information retrieval: Instantly fetch up-to-date details about your Timely account, including billing, activity, and user info, for streamlined reporting or troubleshooting. - Automated webhook setup: Direct your agent to create new webhooks for your account, enabling real-time integration with external apps and automated event notifications. - Seamless workflow automation: Connect Timely events to other services or agents by configuring webhooks, so you can automate time-tracking updates or project triggers. - Centralized time management: Allow your agent to coordinate between Timely and your other productivity tools by securely accessing and sharing account data as needed. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `TIMELY_CREATE_CLIENT` | Create Client | Tool to create a new client in the specified Timely account. Use when adding a new client to track time against. Client names must be unique within an account. | | `TIMELY_CREATE_DAY_LOCKING` | Create Day Locking | Tool to create a day locking entry that prevents editing of time entries for specific dates and users. Use when you need to lock time entries to prevent modifications after approval or billing. | | `TIMELY_CREATE_LABEL` | Create Label | Tool to create a new label in the specified Timely account. Use when you need to create a label for categorizing projects, time entries, or other resources. | | `TIMELY_CREATE_REPORT` | Create report | Tool to generate reports for a Timely account with optional filters. Use when you need to create reports for time tracking, billing analysis, or project summaries with date range or user/project filters. | | `TIMELY_CREATE_TEAM` | Create Team | Tool to create a new team in the specified Timely account. Use when organizing users into teams for better collaboration and project management. | | `TIMELY_CREATE_WEBHOOK` | Create Webhook | Tool to create a new webhook for the specified account. Use after specifying the target URL and event subscriptions. Call only once per configuration. | | `TIMELY_DELETE_LABEL` | Delete a label | Tool to delete a label by ID from a Timely account. Use when you need to remove an existing label. | | `TIMELY_DELETE_TEAM` | Delete a team | Tool to delete a team by its ID. Use when you need to remove a specific team from the account. This operation is destructive and cannot be undone. | | `TIMELY_DELETE_WEBHOOK` | Delete Webhook | Tool to delete an existing webhook by its ID. Use when you need to remove a webhook subscription from an account. | | `TIMELY_FILTER_REPORTS` | Filter reports | Tool to filter Timely reports based on date range, users, projects, labels, teams, and billing status. Use when you need to generate custom reports with specific criteria or analyze time tracking data for specific periods or resources. | | `TIMELY_GET_ACTIVITIES` | Get activities | Tool to retrieve all activities (audit trail) for a Timely account. Activities include logged hours, created reports, shared reports, project changes, and other account events. Use when you need to view the activity log or audit trail for an account. | | `TIMELY_GET_CLIENT` | Get Client | Tool to retrieve details of a specific client by its ID. Use when you need to fetch client information such as name, color, active status, or external references. | | `TIMELY_GET_CURRENT_PERMISSIONS` | Get current user's permissions | Tool to retrieve the current user's permissions for a specified account. Use when you need to check what actions the authenticated user can perform. | | `TIMELY_GET_CURRENT_USER` | Get current user | Tool to retrieve the currently authenticated user. Use when you need to get details of the logged-in user. | | `TIMELY_GET_LABEL` | Retrieve a label | Tool to retrieve a label by ID from a Timely account. Use when you need to fetch label details such as name, color, and parent relationship. | | `TIMELY_GET_PROJECT` | Get project | Tool to retrieve a single project by its ID. Use when you need detailed information about a specific project, such as its name, budget, billable status, or associated client. | | `TIMELY_GET_TEAM` | Retrieve a team | Tool to retrieve details of a specific team by its ID. Use when you need to fetch team information including name, color, and members. | | `TIMELY_GET_USER` | Retrieve a user | Tool to retrieve a user by ID from a Timely account. Use when you need to fetch user details such as name, email, and avatar. | | `TIMELY_GET_USER_CAPACITIES` | Get user capacities | Tool to retrieve capacity information for a specific user in a Timely account. Use when you need to check user work capacity or availability schedules. | | `TIMELY_GET_USER_PERMISSIONS` | Get user permissions | Tool to retrieve a user's permissions by their ID. Use when you need to check what permissions a specific user has in a Timely account. | | `TIMELY_GET_WEBHOOK` | Get Webhook | Tool to retrieve a specific webhook by its ID. Use when you need to check the configuration or status of an existing webhook. | | `TIMELY_LIST_ACCOUNTS` | List accounts | Retrieve all accessible Timely accounts for the authenticated user. Example: "List all Timely accounts" | | `TIMELY_LIST_CLIENTS` | List clients | Tool to list all clients in a Timely account with optional filtering and sorting. Use when you need to discover client IDs or names for project creation, reporting, or mapping external systems. | | `TIMELY_LIST_EVENTS` | List events | Tool to list all events (time entries) in a Timely account with optional filtering by date range, users, and projects. Use when you need to retrieve time entries for reporting, analysis, or synchronization with external systems. | | `TIMELY_LIST_FORECASTS` | List forecasts | Tool to list all forecasts (tasks) in a Timely account with optional date filtering. Use when you need to view planned tasks, retrieve forecast IDs, or analyze scheduled work. | | `TIMELY_LIST_LABELS` | List labels | Tool to list all labels in a Timely account. Use when you need to discover label IDs or names for organizing projects and time entries. Can optionally filter to show only child labels by providing a parent_id. | | `TIMELY_LIST_PROJECT_EVENTS` | List project events | Tool to list all events (time entries) for a specific project in Timely. Use when you need to retrieve all time logs associated with a project for reporting, analysis, or verification. | | `TIMELY_LIST_PROJECTS` | List projects | Tool to list all projects in a Timely account with optional filtering and sorting. Use when you need to discover project IDs or names for time entry creation, reporting, or mapping external systems. | | `TIMELY_LIST_ROLES` | List roles | Tool to list all available roles in a Timely account. Use when you need to discover role IDs or names for user assignment or permission management. | | `TIMELY_LIST_TEAMS` | List teams | Tool to list all teams in the specified Timely account. Use when you need to retrieve all teams for collaboration and project management purposes. | | `TIMELY_LIST_USER_EVENTS` | List user events | Tool to list all events (time entries) for a specific user in Timely. Use when you need to retrieve all time logs for a user for reporting, analysis, or verification. | | `TIMELY_LIST_USERS` | List users | Tool to list all users in a Timely account with optional filtering and pagination. Use when you need to discover user IDs, names, or emails for time entry creation, reporting, or user management. | | `TIMELY_LIST_WEBHOOKS` | List Webhooks | Tool to list all webhooks in the specified account. Use when you need to see existing webhook configurations or verify webhook setup. | | `TIMELY_PROCESS_BULK_EVENTS` | Process bulk events | Tool to create, update, or delete multiple events in a single bulk operation. Use when performing multiple event operations to improve efficiency. Supports up to 100 operations per request across create, update, and delete operations. | | `TIMELY_RETRIEVE_ACCOUNT` | Retrieve an account | Tool to retrieve details of a specific account by its ID. Use when you need to fetch fresh account info after confirming the ID. Example: "Retrieve account details for account ID 364" | | `TIMELY_UPDATE_CLIENT` | Update a client | Tool to update an existing client by ID in Timely. Use when you need to modify client details such as name, status, color, or external ID. | | `TIMELY_UPDATE_DAY_LOCKING` | Update day locking settings | Tool to update day locking settings for specified users and dates. Use when you need to lock or unlock specific days for time tracking. Locked days prevent users from editing time entries on those dates. | | `TIMELY_UPDATE_LABEL` | Update a label | Tool to update a label by ID in a Timely account. Use when you need to modify an existing label's name, color, or hierarchy. | | `TIMELY_UPDATE_PROJECT` | Update a project | Tool to update a project by ID in a Timely account. Use when you need to modify project details such as name, description, billing status, or archive a project. | | `TIMELY_UPDATE_USER` | Update a user | Tool to update a user by ID in a Timely account. Use when you need to modify user details such as email, name, role, or status. | | `TIMELY_UPDATE_WEBHOOK` | Update Webhook | Tool to update an existing webhook by ID. Use when you need to modify webhook settings such as URL, subscriptions, or active status. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Timely MCP server is an implementation of the Model Context Protocol that connects your AI agent to Timely. It provides structured and secure access so your agent can perform Timely 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 you begin, make sure you have: - Node.js and npm installed - A Composio account with API key - An OpenAI API key ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider. - Keep the API key safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install required dependencies First, install the necessary packages for your project. What you're installing: - @ai-sdk/openai: Vercel AI SDK's OpenAI provider - @ai-sdk/mcp: MCP client for Vercel AI SDK - @composio/core: Composio SDK for tool integration - ai: Core Vercel AI SDK - dotenv: Environment variable management ```bash npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's needed: - OPENAI_API_KEY: Your OpenAI API key for GPT model access - COMPOSIO_API_KEY: Your Composio API key for tool access - COMPOSIO_USER_ID: A unique identifier for the user session ```bash OPENAI_API_KEY=your_openai_api_key_here COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here ``` ### 4. Import required modules and validate environment What's happening: - We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio - The dotenv/config import automatically loads environment variables - The MCP client import enables connection to Composio's tool server ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey, }); ``` ### 5. Create Tool Router session and initialize MCP client What's happening: - We're creating a Tool Router session that gives your agent access to Timely tools - The create method takes the user ID and specifies which toolkits should be available - The returned mcp object contains the URL and authentication headers needed to connect to the MCP server - This session provides access to all Timely-related tools through the MCP protocol ```typescript async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["timely"], }); const mcpUrl = session.mcp.url; ``` ### 6. Connect to MCP server and retrieve tools What's happening: - We're creating an MCP client that connects to our Composio Tool Router session via HTTP - The mcp.url provides the endpoint, and mcp.headers contains authentication credentials - The type: "http" is important - Composio requires HTTP transport - tools() retrieves all available Timely tools that the agent can use ```typescript const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); ``` ### 7. Initialize conversation and CLI interface What's happening: - We initialize an empty messages array to maintain conversation history - A readline interface is created to accept user input from the command line - Instructions are displayed to guide the user on how to interact with the agent ```typescript let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to timely, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); ``` ### 8. Handle user input and stream responses with real-time tool feedback What's happening: - We use streamText instead of generateText to stream responses in real-time - toolChoice: "auto" allows the model to decide when to use Timely tools - stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations - onStepFinish callback displays which tools are being used in real-time - We iterate through the text stream to create a typewriter effect as the agent responds - The complete response is added to conversation history to maintain context - Errors are caught and displayed with helpful retry suggestions ```typescript rl.on("line", async (userInput: string) => { const trimmedInput = userInput.trim(); if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } messages.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Complete Code ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey, }); async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["timely"], }); const mcpUrl = session.mcp.url; const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to timely, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); rl.on("line", async (userInput: string) => { const trimmedInput = userInput.trim(); if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } messages.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Conclusion You've successfully built a Timely agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback. Key features of this implementation: - Real-time streaming responses for a better user experience with typewriter effect - Live tool execution feedback showing which tools are being used as the agent works - Dynamic tool loading through Composio's Tool Router with secure authentication - Multi-step tool execution with configurable step limits (up to 10 steps) - Comprehensive error handling for robust agent execution - Conversation history maintenance for context-aware responses You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows. ## How to build Timely MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/timely/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/timely/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/timely/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/timely/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/timely/framework/codex) - [OpenClaw](https://composio.dev/toolkits/timely/framework/openclaw) - [Hermes](https://composio.dev/toolkits/timely/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/timely/framework/cli) - [Google ADK](https://composio.dev/toolkits/timely/framework/google-adk) - [LangChain](https://composio.dev/toolkits/timely/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/timely/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/timely/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/timely/framework/crew-ai) ## Related Toolkits - [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly. - [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place. - [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations. - [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals. - [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem. - [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity. - [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently. - [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place. - [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time. - [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time. - [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place. - [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations in one place. - [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. - [Beeminder](https://composio.dev/toolkits/beeminder) - Beeminder is an online goal-tracking platform that uses monetary pledges to keep you motivated. Stay accountable and hit your targets with real financial incentives. - [Boxhero](https://composio.dev/toolkits/boxhero) - Boxhero is a cloud-based inventory management platform for SMBs, offering real-time updates, barcode scanning, and team collaboration. It helps businesses streamline stock tracking and analytics for smarter inventory decisions. - [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date. - [Breeze](https://composio.dev/toolkits/breeze) - Breeze is a project management platform designed to help teams plan, track, and collaborate on projects. It streamlines workflows and keeps everyone on the same page. - [Bugherd](https://composio.dev/toolkits/bugherd) - Bugherd is a visual feedback and bug tracking tool for websites. It helps teams and clients report website issues directly on live sites for faster fixes. - [Canny](https://composio.dev/toolkits/canny) - Canny is a platform for managing customer feedback and feature requests. It helps teams prioritize product decisions based on real user insights. - [Chmeetings](https://composio.dev/toolkits/chmeetings) - Chmeetings is a church management platform for events, members, donations, and volunteers. It streamlines church operations and improves community engagement. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Timely MCP? With a standalone Timely MCP server, the agents and LLMs can only access a fixed set of Timely tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Timely and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Vercel AI SDK v6? Yes, you can. Vercel AI SDK v6 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 Timely tools. ### Can I manage the permissions and scopes for Timely while using Tool Router? Yes, absolutely. You can configure which Timely 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 Timely data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)