How to integrate Everhour MCP with Claude Agent SDK

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Everhour logo
Claude Agent SDK logo
divider

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

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 & Triggers

Tools
Create ClientCreates a new client in Everhour for tracking billable work, invoicing, and project organization.
Delete a clientTool to delete a client.
List ClientsRetrieves all clients in the Everhour workspace.
Clock In UserTool to clock in a user for time tracking.
Clock Out UserTool to clock out a user for time tracking.
Create WebhookTool to create a new webhook for event notifications in Everhour.
Delete WebhookTool to delete a webhook.
Delete a timecardTool to delete a timecard for a user on a specific date.
Discard Timesheet ApprovalTool to discard a pending timesheet approval request.
List ExpensesLists expense records from your Everhour workspace.
Get Client by IDTool to retrieve a specific client by ID.
Get ProjectTool to retrieve a specific project.
Get SectionRetrieve details of a specific section by its ID.
Get TimecardTool to retrieve a specific timecard for a user on a date.
Get Authenticated User ProfileTool to retrieve profile information of the authenticated user.
Get WebhookRetrieve details of a specific webhook by its ID.
List Expense CategoriesLists all expense categories available in your Everhour account.
List WebhooksLists all webhooks configured for the Everhour account.
List InvoicesRetrieves all invoices from your Everhour workspace.
List projectsList all Everhour projects accessible by the authenticated user.
List SectionsLists all sections within a specific Everhour project.
List TagsList all tags in the Everhour workspace.
List Team MembersRetrieves all team members in the authenticated Everhour workspace.
List TeamsRetrieves information about the authenticated team/workspace in Everhour.
List TimecardsTool to retrieve all team timecards with optional date filtering.
List User TimecardsTool to retrieve timecards for a specific user with optional date filtering.
List User TimesheetsTool to retrieve timesheets for a specific user.
Create ProjectTool to create a new project in Everhour.
Delete a projectTool to delete a project.
Request Timesheet ApprovalTool to request approval for a timesheet or approve a week (for admins).
Create SectionTool to create a new section in a project.
Delete a sectionTool to delete a section.
Create TaskCreates a new task in an Everhour project.
Start TimerTool to start a new timer for a task.
Update ClientTool to update an existing client in Everhour.
Update an existing projectUpdates an existing Everhour project's settings.
Update TimecardTool to update a timecard for a user on a specific date.
Update WebhookTool to update an existing webhook configuration in Everhour.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

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

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console 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.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

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

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Everhour functionality

Create a Composio instance and Tool Router session

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")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Everhour
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# 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
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Everhour
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# 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()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Everhour and Claude Agent SDK:

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())

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

FAQ

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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.