SIGN UPLOG IN
X (Twitter)LinkedInGitHubDiscordYouTube

How to integrate Everhour MCP with Claude Agent SDK

Connect Claude Agent SDK to Everhour MCP. List all clients for this workspace, retrieve expense categories for new report, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Everhour logoEverhour
Api Key

Everhour is a time tracking and expense management platform for teams and individuals. Gain insight into hours, costs, and budgets for smarter planning and resource allocation.

51 Tools

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 start timers, clock in and out, manage clients and projects, review timecards and timesheets, and list expenses and invoices 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.

For exact tool slugs and parameter tables, see the tool catalog in the Composio docs.

Also integrate Everhour with

Claude CodeClaude CoworkOpenAI Agents SDKGrok BotCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

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.

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

Step by step09 STEPS
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
2

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.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

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
5

Import dependencies

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();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Everhour functionality
6

Create a Composio instance and Tool Router session

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;
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
7

Configure Claude Agent with MCP

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,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: '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
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

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?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

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

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.
TOOLS

Supported Tools

Every Everhour action and event your agent gets out of the box.

Add Time

Add or upsert tracked time for a task, user, and date.

Create Client

Creates a new client in Everhour for tracking billable work, invoicing, and project organization.

Delete a client

Tool to delete a client.

List Clients

Retrieves all clients in the Everhour workspace.

Clock In User

Tool to clock in a user for time tracking.

Clock Out User

Tool to clock out a user for time tracking.

Create Webhook

Tool to create a new webhook for event notifications in Everhour.

Delete Webhook

Tool to delete a webhook.

Delete a timecard

Delete a user's timecard for a specific date in Everhour.

Delete Time Record

Remove tracked time by record ID while retaining its history trail.

Discard Timesheet Approval

Withdraw the authenticated user's previously submitted timesheet approval request for a week.

List Expenses

List expense records logged by the authenticated user in Everhour.

Get Client by ID

Tool to retrieve a specific client by ID.

Get Current Timer

Get the authenticated Everhour user's current timer state.

Get Project

Tool to retrieve a specific project.

Get Projects Report

Return aggregated Everhour project time and financial metrics.

Get Section

Retrieve details of a specific section by its ID.

Get Task

Retrieve one native or integration-backed Everhour task by ID.

Get Task Time Records

Lists tracked-time records for an Everhour task with date and page filters.

Get Timecard

Tool to retrieve a specific timecard for a user on a date.

Get Authenticated User Profile

Tool to retrieve profile information of the authenticated user.

Get User Time Records

List one Everhour user's tracked-time records.

Get Webhook

Retrieve details of a specific webhook by its ID.

List Expense Categories

Lists all expense categories available in your Everhour account.

List Webhooks

List webhooks created with the Everhour API key, including their target URLs, subscribed events, active status, and timestamps.

List Invoices

Retrieves all invoices from your Everhour workspace.

List projects

Lists Everhour projects accessible to the authenticated user, with optional name, status, platform, and result-limit parameters.

List Project Tasks

List tasks in an Everhour project with optional filters and pagination.

List Project Time Records

List tracked-time records for an Everhour project.

List Sections

Lists all sections within a specific Everhour project.

List Tags

List all tags in the Everhour workspace.

List Team Members

Retrieves team members in the authenticated Everhour workspace, including IDs, names, roles, and statuses.

List Teams

Retrieves information about the authenticated team/workspace in Everhour.

List Team Time Records

List team time records for a date range; without dates, return only today.

List Timecards

Retrieves team timecards, including clock-in/out data and work hours, with optional date filtering.

List User Timecards

Retrieves a specific user's timecards, including clock-in/out data and work hours, with optional date filtering.

List User Timesheets

Tool to retrieve timesheets for a specific user.

Create Project

Tool to create a new project in Everhour.

Delete a project

Permanently deletes an Everhour project by ID, including its tasks and associated time records.

Request Timesheet Approval

Tool to request approval for a timesheet or approve a week (for admins).

Search Tasks

Search accessible Everhour tasks, optionally including closed tasks.

Create Section

Tool to create a new section in a project.

Delete a section

Tool to delete a section.

Create Task

Creates a new task in an Everhour project.

Start Timer

Tool to start a new timer for a task.

Update Client

Tool to update an existing client in Everhour.

Update Expense

Partially update an existing Everhour expense.

Update an existing project

Updates an existing Everhour project's settings by project ID, including its name or notes.

Update Timecard

Update or create a user's timecard for a specific date, setting clock-in, clock-out, or break duration.

Update Time Record

Update an existing tracked-time record by its record ID.

Update Webhook

Update an existing Everhour webhook's subscribed events or project filter.

FRAMEWORKS

How to build Everhour MCP Agent with another framework

Claude Code logo

Claude Code

Use Everhour MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Everhour MCP with Claude Cowork

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Everhour MCP with OpenAI Agents SDK

Grok Bot logo

Grok Bot

Use Everhour MCP with Grok Bot

Codex logo

Codex

Use Everhour MCP with Codex

OpenClaw logo

OpenClaw

Use Everhour MCP with OpenClaw

Hermes logo

Hermes

Use Everhour MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Everhour MCP with Atomic Agent

Google ADK logo

Google ADK

Use Everhour MCP with Google ADK

LangChain logo

LangChain

Use Everhour MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Everhour MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Everhour MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Everhour MCP with LlamaIndex

CrewAI logo

CrewAI

Use Everhour MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Everhour MCP with Pydantic AI

AutoGen logo

AutoGen

Use Everhour MCP with AutoGen

FAQ

Frequently asked questions

Start with Everhour.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Everhour tool your agent needs.Free to start.

Start building