How to integrate Everhour MCP with LangChain

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Everhour logo
LangChain logo
divider

Introduction

This guide walks you through connecting Everhour to LangChain 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 LangChain 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 OpenAI and Composio API keys
  • Connect your Everhour project to Composio
  • Create a Tool Router MCP session for Everhour
  • Initialize an MCP client and retrieve Everhour tools
  • Build a LangChain agent that can interact with Everhour
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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 this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard 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.
  • 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-langchain langchain-mcp-adapters langchain python-dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • composio-langchain provides Composio integration for LangChain
  • langchain-mcp-adapters enables MCP client connections
  • langchain is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models

Import dependencies

from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Everhour functionality through MCP

Initialize Composio client

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))

    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Everhour tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding

Create a Tool Router session

# Create Tool Router session for Everhour
session = composio.create(
    user_id=os.getenv("COMPOSIO_USER_ID"),
    toolkits=['everhour']
)

url = session.mcp.url
What's happening:
  • We're creating a Tool Router session that gives your agent access to Everhour tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Everhour tools as needed

Configure the agent with the MCP URL

client = MultiServerMCPClient({
    "everhour-agent": {
        "transport": "streamable_http",
        "url": session.mcp.url,
        "headers": {
            "x-api-key": os.getenv("COMPOSIO_API_KEY")
        }
    }
})

tools = await client.get_tools()

agent = create_agent("gpt-5", tools)
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Everhour MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • get_tools() retrieves all available Everhour tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model

Set up interactive chat interface

conversation_history = []

print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Everhour related question or task to the agent.\n")

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ['exit', 'quit', 'bye']:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_history.append({"role": "user", "content": user_input})
    print("\nAgent is thinking...\n")

    response = await agent.ainvoke({"messages": conversation_history})
    conversation_history = response['messages']
    final_response = response['messages'][-1].content
    print(f"Agent: {final_response}\n")
What's happening:
  • We initialize an empty conversation_history list to maintain context across interactions
  • A while loop continuously accepts user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the ainvoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully

Run the application

if __name__ == "__main__":
    asyncio.run(main())
What's happening:
  • We call the main() function using asyncio.run() to start the application

Complete Code

Here's the complete code to get you started with Everhour and LangChain:

from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain.agents import create_agent
from dotenv import load_dotenv
from composio import Composio
import asyncio
import os

load_dotenv()

async def main():
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    
    if not os.getenv("COMPOSIO_API_KEY"):
        raise ValueError("COMPOSIO_API_KEY is not set")
    if not os.getenv("COMPOSIO_USER_ID"):
        raise ValueError("COMPOSIO_USER_ID is not set")
    
    session = composio.create(
        user_id=os.getenv("COMPOSIO_USER_ID"),
        toolkits=['everhour']
    )

    url = session.mcp.url
    
    client = MultiServerMCPClient({
        "everhour-agent": {
            "transport": "streamable_http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    })
    
    tools = await client.get_tools()
  
    agent = create_agent("gpt-5", tools)
    
    conversation_history = []
    
    print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
    print("Ask any Everhour related question or task to the agent.\n")
    
    while True:
        user_input = input("You: ").strip()
        
        if user_input.lower() in ['exit', 'quit', 'bye']:
            print("\nGoodbye!")
            break
        
        if not user_input:
            continue
        
        conversation_history.append({"role": "user", "content": user_input})
        print("\nAgent is thinking...\n")
        
        response = await agent.ainvoke({"messages": conversation_history})
        conversation_history = response['messages']
        final_response = response['messages'][-1].content
        print(f"Agent: {final_response}\n")

if __name__ == "__main__":
    asyncio.run(main())

Conclusion

You've successfully built a LangChain agent that can interact with Everhour through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.

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 LangChain?

Yes, you can. LangChain 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.