# How to integrate Everhour MCP with Claude Agent SDK ```json { "title": "How to integrate Everhour MCP with Claude Agent SDK", "toolkit": "Everhour", "toolkit_slug": "everhour", "framework": "Claude Agent SDK", "framework_slug": "claude-agents-sdk", "url": "https://composio.dev/toolkits/everhour/framework/claude-agents-sdk", "markdown_url": "https://composio.dev/toolkits/everhour/framework/claude-agents-sdk.md", "updated_at": "2026-05-12T10:10:51.465Z" } ``` ## Introduction This guide walks you through connecting Everhour to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Everhour agent that can list all clients for this workspace, retrieve expense categories for new report, get your everhour user profile details through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Everhour account through Composio's Everhour MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Everhour with - [OpenAI Agents SDK](https://composio.dev/toolkits/everhour/framework/open-ai-agents-sdk) - [Claude Code](https://composio.dev/toolkits/everhour/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/everhour/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/everhour/framework/codex) - [OpenClaw](https://composio.dev/toolkits/everhour/framework/openclaw) - [Hermes](https://composio.dev/toolkits/everhour/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/everhour/framework/cli) - [Google ADK](https://composio.dev/toolkits/everhour/framework/google-adk) - [LangChain](https://composio.dev/toolkits/everhour/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/everhour/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/everhour/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/everhour/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/everhour/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get and set up your Claude/Anthropic and Composio API keys - Install the necessary dependencies - Initialize Composio and create a Tool Router session for Everhour - Configure an AI agent that can use Everhour as a tool - Run a live chat session where you can ask the agent to perform Everhour operations ## What is Claude Agent SDK? The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management. Key features include: - Native MCP Support: Built-in support for Model Context Protocol servers - Permission Modes: Control tool execution permissions - Streaming Responses: Real-time response streaming for interactive applications - Context Manager: Clean async context management for sessions ## What is the Everhour MCP server, and what's possible with it? The Everhour MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Everhour account. It provides structured and secure access to your time tracking, client, and expense data, so your agent can perform actions like listing clients, retrieving expenses, managing projects, and fetching user profiles on your behalf. - Comprehensive client management: Ask your agent to list, create, or delete clients to keep your workspace organized and up-to-date. - Expense tracking and review: Effortlessly retrieve all expenses or list available expense categories to monitor spending and streamline expense management. - Project and section insights: Have your agent fetch detailed information about specific projects or sections using their IDs for better resource planning. - Personalized user profile access: Enable your agent to fetch the authenticated user's profile for quick access to account details and preferences. - Webhook configuration overview: List all configured webhooks to monitor integrations and automate notifications within your Everhour environment. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `EVERHOUR_CLIENT_CREATE` | Create Client | Creates a new client in Everhour for tracking billable work, invoicing, and project organization. Use this action when: - Setting up a new customer/client account for time tracking - Organizing projects under a specific client for billing purposes - Creating a client before generating invoices Note: Each project can only be assigned to one client. Attempting to assign a project that is already linked to another client will result in a 400 error. | | `EVERHOUR_CLIENT_DELETE` | Delete a client | Tool to delete a client. Use when you need to permanently remove a client from Everhour after confirming the client ID. | | `EVERHOUR_CLIENT_LIST` | List Clients | Retrieves all clients in the Everhour workspace. Use this action to: - Get an overview of all clients and their IDs - Find client IDs for use with other client-related actions (e.g., get client, update client, delete client) - View client statuses (active/archived), associated projects, and invoice settings Returns a list of all clients with their full details including name, creation date, status, associated projects, and invoice configuration settings. | | `EVERHOUR_CLOCK_IN` | Clock In User | Tool to clock in a user for time tracking. Use when you need to start a user's workday or shift in Everhour. | | `EVERHOUR_CLOCK_OUT` | Clock Out User | Tool to clock out a user for time tracking. Use when you need to end a user's workday or shift in Everhour. | | `EVERHOUR_CREATE_WEBHOOK` | Create Webhook | Tool to create a new webhook for event notifications in Everhour. Use when you need to set up real-time notifications for specific events like task creation, timer starts, or client updates. The target URL must be accessible and respond to Everhour's validation request during setup. | | `EVERHOUR_DELETE_HOOK` | Delete Webhook | Tool to delete a webhook. Use when you need to permanently remove a webhook from Everhour after confirming the webhook ID. | | `EVERHOUR_DELETE_TIMECARD` | Delete a timecard | Tool to delete a timecard for a user on a specific date. Use when you need to permanently remove time entries for a user on a particular date. | | `EVERHOUR_DISCARD_TIMESHEET_APPROVAL` | Discard Timesheet Approval | Tool to discard a pending timesheet approval request. Use when you need to cancel or withdraw a previously submitted approval request for a timesheet. | | `EVERHOUR_EXPENSES_LIST` | List Expenses | Lists expense records from your Everhour workspace. Supports filtering by date range, user, project, category, and billable status. Use this to review expenses, generate reports, or find specific expense entries. Returns expense details including amount, category, date, and billable status. | | `EVERHOUR_GET_CLIENT` | Get Client by ID | Tool to retrieve a specific client by ID. Use when you need detailed client information after obtaining the client's ID. | | `EVERHOUR_GET_PROJECT` | Get Project | Tool to retrieve a specific project. Use after you have the project ID if you need its details. | | `EVERHOUR_GET_SECTION` | Get Section | Retrieve details of a specific section by its ID. Sections are used to organize tasks within Everhour projects. Use List Sections action first to get available section IDs for a project. | | `EVERHOUR_GET_TIMECARD` | Get Timecard | Tool to retrieve a specific timecard for a user on a date. Use when you need to get clock-in, clock-out, break time, and work time details for a team member on a particular day. | | `EVERHOUR_GET_USER_PROFILE` | Get Authenticated User Profile | Tool to retrieve profile information of the authenticated user. Use after providing API key to fetch current user's profile details. | | `EVERHOUR_GET_WEBHOOK` | Get Webhook | Retrieve details of a specific webhook by its ID. Returns the webhook's configuration including target URL, subscribed events, active status, and timestamps. Use this to inspect a webhook's settings or verify its configuration. | | `EVERHOUR_LIST_EXPENSE_CATEGORIES` | List Expense Categories | Lists all expense categories available in your Everhour account. Returns category IDs needed to create or filter expenses. | | `EVERHOUR_LIST_HOOKS` | List Webhooks | Lists all webhooks configured for the Everhour account. Returns details about each webhook including its target URL, subscribed events, active status, and timestamps. Use this to review existing webhook configurations or verify webhook setup. No parameters are required. | | `EVERHOUR_LIST_INVOICES` | List Invoices | Retrieves all invoices from your Everhour workspace. Returns a list of invoice objects with details such as invoice number, client, project, amount, currency, status, and dates. Use this action to get an overview of all invoices for reporting, accounting, or tracking purposes. | | `EVERHOUR_LIST_PROJECTS` | List projects | List all Everhour projects accessible by the authenticated user. Use this tool to: - Retrieve all projects in the workspace - Search for projects by name using the 'query' parameter - Filter projects by status ('open' or 'archived') - Filter projects by integration platform (e.g., 'ev', 'as', 'jira', 'trello') - Limit the number of results returned Returns a list of projects with details including name, ID, status, budget, billing, and more. | | `EVERHOUR_LIST_SECTIONS` | List Sections | Lists all sections within a specific Everhour project. Sections help organize tasks within a project. Returns section details including id, name, position, and status. Use this tool when you need to view, manage, or reference sections before creating tasks or organizing project work. | | `EVERHOUR_LIST_TAGS` | List Tags | List all tags in the Everhour workspace. Returns an array of all tags available in the workspace. Each tag contains: - id: Unique numeric identifier for the tag - name: Display name of the tag (e.g., 'high', 'medium', 'low') - color: Hex color code for visual display (e.g., '#ee7070') Use this action when you need to: - View all available tags for categorizing time entries - Get tag IDs for use in other API calls - Display tag options to users No parameters required. | | `EVERHOUR_LIST_TEAM_MEMBERS` | List Team Members | Retrieves all team members in the authenticated Everhour workspace. Returns detailed information for each member including their ID, name, email, role (admin/member/owner), status, avatar URLs, cost/billing rates, capacity, time tracking policies, and resource planner access permissions. Use this action to: - Get a list of user IDs for assigning tasks or tracking time - View team member roles and permissions - Check team member status (active/inactive) - Access billing information like cost and rate for team members | | `EVERHOUR_LIST_TEAMS` | List Teams | Retrieves information about the authenticated team/workspace in Everhour. Returns comprehensive team details including: - Team ID and name - Owner information - Working days and hours configuration - Billing and subscription status - Available plan features - Enabled applications - Time tracking policies Use this action to: - Get the current team/workspace ID and name - Check team billing status and plan features - View team configuration and settings - Retrieve owner information Note: This returns info about the single workspace associated with the API key. Everhour operates in a single workspace context per API key. | | `EVERHOUR_LIST_TIMECARDS` | List Timecards | Tool to retrieve all team timecards with optional date filtering. Use when you need to get clock-in/out data and work hours for team members. | | `EVERHOUR_LIST_USER_TIMECARDS` | List User Timecards | Tool to retrieve timecards for a specific user with optional date filtering. Use when you need to get clock-in/out data and work hours for a particular team member. | | `EVERHOUR_LIST_USER_TIMESHEETS` | List User Timesheets | Tool to retrieve timesheets for a specific user. Use to get weekly time tracking data including daily time entries, task time, approvals, timecards, and time-off records. First use EVERHOUR_LIST_TEAM_MEMBERS to get the user ID. | | `EVERHOUR_PROJECT_CREATE` | Create Project | Tool to create a new project in Everhour. Use after gathering project details to persist a new project. | | `EVERHOUR_PROJECT_DELETE` | Delete a project | Tool to delete a project. Use when you need to permanently remove a project from Everhour after confirming the project ID. | | `EVERHOUR_REQUEST_TIMESHEET_APPROVAL` | Request Timesheet Approval | Tool to request approval for a timesheet or approve a week (for admins). Use when you need to submit a timesheet for review or when an admin needs to approve submitted timesheets. Regular users can request approval for their own timesheets, while admins can directly approve timesheets. | | `EVERHOUR_SECTION_CREATE` | Create Section | Tool to create a new section in a project. Use when you need to organize tasks under an existing project after confirming the project ID. | | `EVERHOUR_SECTION_DELETE` | Delete a section | Tool to delete a section. Use when you need to permanently remove a section from Everhour after confirming the section ID. | | `EVERHOUR_TASK_CREATE` | Create Task | Creates a new task in an Everhour project. Use this to add tasks for time tracking. Requires a valid project ID (get from EVERHOUR_LIST_PROJECTS) and a task name. Example: Create a task named 'Write unit tests' in project ev:192144450634449. | | `EVERHOUR_TIMER_START` | Start Timer | Tool to start a new timer for a task. Use when you need to begin tracking time on a specific task. | | `EVERHOUR_UPDATE_CLIENT` | Update Client | Tool to update an existing client in Everhour. Use this to modify client details such as name, business details, or status (active/archived). First use 'List Clients' to obtain the client ID. | | `EVERHOUR_UPDATE_PROJECT` | Update an existing project | Updates an existing Everhour project's settings. Use this to modify project name, budget, billing configuration, or notes. Requires a valid project_id (format: 'ev:XXXXXXXXX') - obtain from list_projects or project_create actions first. Only the fields you specify will be updated; omitted fields remain unchanged. | | `EVERHOUR_UPDATE_TIMECARD` | Update Timecard | Tool to update a timecard for a user on a specific date. Use when you need to set or modify clock-in, clock-out times, or break duration for a user's timecard. | | `EVERHOUR_UPDATE_WEBHOOK` | Update Webhook | Tool to update an existing webhook configuration in Everhour. Use this to modify the target URL, subscribed events, or project filter of an existing webhook. First use 'List Webhooks' to obtain the webhook ID. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Everhour MCP server is an implementation of the Model Context Protocol that connects your AI agent to Everhour. It provides structured and secure access so your agent can perform Everhour 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: - Composio API Key and Claude/Anthropic API Key - Primary know-how of Claude Agents SDK - A Everhour account - Some knowledge of Python ### 1. Getting API Keys for Claude/Anthropic and Composio Claude/Anthropic API Key - Go to the [Anthropic Console](https://console.anthropic.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models. - 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 dependencies No description provided. ```python pip install composio-anthropic claude-agent-sdk python-dotenv ``` ```typescript npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's happening: - COMPOSIO_API_KEY authenticates with Composio - USER_ID identifies the user for session management - ANTHROPIC_API_KEY authenticates with Anthropic/Claude ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here ANTHROPIC_API_KEY=your_anthropic_api_key_here ``` ### 4. Import dependencies No description provided. ```python import asyncio from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions import os from composio import Composio from dotenv import load_dotenv load_dotenv() ``` ```typescript import 'dotenv/config'; import readline from 'node:readline'; import { Composio } from '@composio/core'; import { query, type Options } from "@anthropic-ai/claude-agent-sdk"; dotenv.config(); ``` ### 5. Create a Composio instance and Tool Router session No description provided. ```python async def chat_with_remote_mcp(): api_key = os.getenv("COMPOSIO_API_KEY") if not api_key: raise RuntimeError("COMPOSIO_API_KEY is not set") composio = Composio(api_key=api_key) # Create Tool Router session for Everhour mcp_server = composio.create( user_id=os.getenv("USER_ID"), toolkits=["everhour"] ) url = mcp_server.mcp.url if not url: raise ValueError("Session URL not found") ``` ```typescript async function chat() { const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composio = new Composio({ apiKey: COMPOSIO_API_KEY }); // Create Tool Router session for Everhour const session = await composio.create(USER_ID, { toolkits: ['everhour'], }); const mcpUrl = session?.mcp.url; ``` ### 6. Configure Claude Agent with MCP No description provided. ```python # Configure remote MCP server for Claude options = ClaudeAgentOptions( permission_mode="bypassPermissions", mcp_servers={ "composio": { "type": "http", "url": url, "headers": { "x-api-key": os.getenv("COMPOSIO_API_KEY") } } }, system_prompt="You are a helpful assistant with access to Everhour tools via Composio.", max_turns=10 ) ``` ```typescript const options: Options = { permissionMode: 'bypassPermissions', mcpServers: { composio: { type: 'http', url: mcpUrl, headers: { 'x-api-key': COMPOSIO_API_KEY } } }, systemPrompt: 'You are a helpful assistant with access to Everhour tools via Composio.', maxTurns: 10, }; ``` ### 7. Create client and start chat loop No description provided. ```python # Create client with context manager async with ClaudeSDKClient(options=options) as client: print("\nChat started. Type 'exit' or 'quit' to end.\n") # Main chat loop while True: user_input = input("You: ").strip() if user_input.lower() in {"exit", "quit"}: print("Goodbye!") break # Send query await client.query(user_input) # Receive and print response print("Claude: ", end="", flush=True) async for message in client.receive_response(): if hasattr(message, "content"): for block in message.content: if hasattr(block, "text"): print(block.text, end="", flush=True) print() ``` ```typescript const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: 'You: ' }); console.log('\nChat started. Type "exit" to quit.\n'); let isProcessing = false; async function ask(prompt: string) { isProcessing = true; rl.pause(); process.stdout.write('Claude is thinking...'); const stream = query({ prompt, options }); let firstChunk = true; for await (const msg of stream) { const content = (msg as any).message?.content || (msg as any).content; if (Array.isArray(content)) { for (const block of content) { if (block.type === 'text' && block.text) { if (firstChunk) { process.stdout.write('\r\x1b[K'); process.stdout.write('Claude: '); firstChunk = false; } process.stdout.write(block.text); } } } } process.stdout.write('\n\n'); isProcessing = false; rl.resume(); rl.prompt(); } rl.on('line', async (line) => { if (isProcessing) return; const input = line.trim(); if (input === 'exit') { rl.close(); process.exit(0); } if (input) await ask(input); else rl.prompt(); }); await ask('What can you help me with?'); } ``` ### 8. Run the application No description provided. ```python if __name__ == "__main__": asyncio.run(chat_with_remote_mcp()) ``` ```typescript try { await chat(); } catch (error) { console.error(error); process.exit(1); } ``` ## Complete Code ```python import asyncio from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions import os from composio import Composio from dotenv import load_dotenv load_dotenv() async def chat_with_remote_mcp(): api_key = os.getenv("COMPOSIO_API_KEY") if not api_key: raise RuntimeError("COMPOSIO_API_KEY is not set") composio = Composio(api_key=api_key) # Create Tool Router session for Everhour mcp_server = composio.create( user_id=os.getenv("USER_ID"), toolkits=["everhour"] ) url = mcp_server.mcp.url if not url: raise ValueError("Session URL not found") # Configure remote MCP server for Claude options = ClaudeAgentOptions( permission_mode="bypassPermissions", mcp_servers={ "composio": { "type": "http", "url": url, "headers": { "x-api-key": os.getenv("COMPOSIO_API_KEY") } } }, system_prompt="You are a helpful assistant with access to Everhour tools via Composio.", max_turns=10 ) # Create client with context manager async with ClaudeSDKClient(options=options) as client: print("\nChat started. Type 'exit' or 'quit' to end.\n") # Main chat loop while True: user_input = input("You: ").strip() if user_input.lower() in {"exit", "quit"}: print("Goodbye!") break # Send query await client.query(user_input) # Receive and print response print("Claude: ", end="", flush=True) async for message in client.receive_response(): if hasattr(message, "content"): for block in message.content: if hasattr(block, "text"): print(block.text, end="", flush=True) print() if __name__ == "__main__": asyncio.run(chat_with_remote_mcp()) ``` ```typescript import 'dotenv/config'; import readline from 'node:readline'; import { Composio } from '@composio/core'; import { query, type Options } from "@anthropic-ai/claude-agent-sdk"; async function chat() { const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composio = new Composio({ apiKey: COMPOSIO_API_KEY }); const session = await composio.create(USER_ID, { toolkits: ['everhour'] }); const mcp_url = session?.mcp.url; const options: Options = { permissionMode: 'bypassPermissions', mcpServers: { composio: { type: 'http', url: mcp_url, headers: { 'x-api-key': COMPOSIO_API_KEY } } }, systemPrompt: 'You are a helpful assistant with access to Everhour tools via Composio.', maxTurns: 10, }; const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: 'You: ' }); console.log('\nChat started. Type "exit" to quit.\n'); let isProcessing = false; async function ask(prompt: string) { isProcessing = true; rl.pause(); process.stdout.write('Claude is thinking...'); const stream = query({ prompt, options }); let firstChunk = true; for await (const msg of stream) { const content = (msg as any).message?.content || (msg as any).content; if (Array.isArray(content)) { for (const block of content) { if (block.type === 'text' && block.text) { if (firstChunk) { process.stdout.write('\r\x1b[K'); process.stdout.write('Claude: '); firstChunk = false; } process.stdout.write(block.text); } } } } process.stdout.write('\n\n'); isProcessing = false; rl.resume(); rl.prompt(); } rl.on('line', async (line) => { if (isProcessing) return; const input = line.trim(); if (input === 'exit') { rl.close(); process.exit(0); } if (input) await ask(input); else rl.prompt(); }); await ask('What can you help me with?'); } try { await chat(); } catch (error) { console.error(error); process.exit(1); } ``` ## Conclusion You've successfully built a Claude Agent SDK agent that can interact with Everhour through Composio's Tool Router. Key features: - Native MCP support through Claude's agent framework - Streaming responses for real-time interaction - Permission bypass for smooth automated workflows You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent. ## How to build Everhour MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/everhour/framework/open-ai-agents-sdk) - [Claude Code](https://composio.dev/toolkits/everhour/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/everhour/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/everhour/framework/codex) - [OpenClaw](https://composio.dev/toolkits/everhour/framework/openclaw) - [Hermes](https://composio.dev/toolkits/everhour/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/everhour/framework/cli) - [Google ADK](https://composio.dev/toolkits/everhour/framework/google-adk) - [LangChain](https://composio.dev/toolkits/everhour/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/everhour/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/everhour/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/everhour/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/everhour/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 Everhour MCP? With a standalone Everhour MCP server, the agents and LLMs can only access a fixed set of Everhour tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Everhour and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Claude Agent SDK? Yes, you can. Claude Agent SDK 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 Everhour tools. ### Can I manage the permissions and scopes for Everhour while using Tool Router? Yes, absolutely. You can configure which Everhour 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 Everhour data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)