Use
COMPOSIOFOR YOU
Give Claude, Codex, or any harness secure access to 1700+ tools
CLI
One command to add tools and auth to your coding agent
Build
DEVELOPER PLATFORM
SDKs, tools, and auth for agents and backend apps
MCP GATEWAY
One managed MCP endpoint for all your tools and agents
ENTERPRISE
SSO, governance, and audit controls for deploying agents org-wide
Features
TRIGGERS
Start background agents from events across your connected apps
FIREWALLNEW
Blocks instructions hidden in tool results before your agent reads them
INSTANTNEW
Audio, video, search, browser and data tools, with no keys to manage
OPTIMIZATION
Lower cost per completed task with optimised tools and skills
FOR AGENTS
CLAUDE CODEX OPENCLAW CURSOR HERMES
BUILT FOR
OFFICE WORK SALES MARKETING PRODUCT & DESIGN CUSTOMER SUPPORT ENGINEERING HR & RECRUITING FINANCE & OPS E-COMMERCE CONTENT & MEDIA IT & SECURITY
ALL USE CASES
DOCS

How to integrate Everhour MCP with Mastra AI

Connect Mastra AI 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 free Get a demo

Everhour

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

Managed auth

Connect Everhour without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Book a call

Explore the MCP Gateway

Introduction

This guide walks you through connecting Everhour to Mastra AI 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 Mastra AI 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 Code Claude Cowork OpenAI Agents SDK Claude Agent SDK Grok Bot Codex OpenClaw Hermes Atomic Agent Google ADK LangChain Vercel AI SDK LlamaIndex CrewAI Pydantic AI AutoGen

TL;DR

Here's what you'll learn:

Set up your environment so Mastra, OpenAI, and Composio work together
Create a Tool Router session in Composio that exposes Everhour tools
Connect Mastra's MCP client to the Composio generated MCP URL
Fetch Everhour tool definitions and attach them as a toolset
Build a Mastra agent that can reason, call tools, and return structured results
Run an interactive CLI where you can chat with your Everhour agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

MCP Client: Built-in support for Model Context Protocol servers
Toolsets: Organize tools into logical groups
Step Callbacks: Monitor and debug agent execution
OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

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:

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

Step-by-step Guide

Step by step09 STEPS

Prerequisites

Before starting, make sure you have:

Node.js 18 or higher
A Composio account with an active API key
An OpenAI API key
Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key

Go to the OpenAI dashboard and create an API key.
You need credits or a connected billing setup to use the models.
Store the key somewhere safe.

Composio API Key

Log in to the Composio dashboard.
Go to Settings and copy your API key.
This key lets your Mastra agent talk to Composio and reach Everhour through MCP.

Install dependencies

bash

npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

@composio/core is the Composio SDK for creating MCP sessions
@mastra/core provides the Agent class
@mastra/mcp is Mastra's MCP client
@ai-sdk/openai is the model wrapper for OpenAI
dotenv loads environment variables from .env

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_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
COMPOSIO_USER_ID tells Composio which user this session belongs to
OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) 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 as string,
});

What's happening:

dotenv/config auto loads your .env so process.env.* is available
openai gives you a Mastra compatible model wrapper
Agent is the Mastra agent that will call tools and produce answers
MCPClient connects Mastra to your Composio MCP server
Composio is used to create a Tool Router session

Create a Tool Router session for Everhour

typescript

async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["everhour"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Everhour MCP URL:", composioMCPUrl);

What's happening:

create spins up a short-lived MCP HTTP endpoint for this user
The toolkits array contains "everhour" for Everhour access
session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript

const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);

What's happening:

MCPClient takes an id for this client and a list of MCP servers
The headers property includes the x-api-key for authentication
getTools fetches the tool definitions exposed by the Everhour toolkit

Create the Mastra agent

typescript

const agent = new Agent({
    name: "everhour-mastra-agent",
    instructions: "You are an AI agent with Everhour tools via Composio.",
    model: "openai/gpt-5",
  });

What's happening:

Agent is the core Mastra agent
name is just an identifier for logging and debugging
instructions guide the agent to use tools instead of only answering in natural language
model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript

let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\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({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        everhour: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});

What's happening:

messages keeps the full conversation history in Mastra's expected format
agent.generate runs the agent with conversation history and Everhour toolsets
maxSteps limits how many tool calls the agent can take in a single run
onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

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

typescript

import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) 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 as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["everhour"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      everhour: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "everhour-mastra-agent",
    instructions: "You are an AI agent with Everhour tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { everhour: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Everhour through Composio's Tool Router. You can extend this further by:

Adding other toolkits like Gmail, Slack, or GitHub
Building a web-based chat interface around this agent
Using multiple MCP endpoints to enable cross-app workflows

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

Use Everhour MCP with Claude Code

Claude Cowork

Use Everhour MCP with Claude Cowork

OpenAI Agents SDK

Use Everhour MCP with OpenAI Agents SDK

Claude Agent SDK

Use Everhour MCP with Claude Agent SDK

Grok Bot

Use Everhour MCP with Grok Bot

Codex

Use Everhour MCP with Codex

OpenClaw

Use Everhour MCP with OpenClaw

Hermes

Use Everhour MCP with Hermes

Atomic Agent

Use Everhour MCP with Atomic Agent

Google ADK

Use Everhour MCP with Google ADK

LangChain

Use Everhour MCP with LangChain

Vercel AI SDK

Use Everhour MCP with Vercel AI SDK

LlamaIndex

Use Everhour MCP with LlamaIndex

CrewAI

Use Everhour MCP with CrewAI

Pydantic AI

Use Everhour MCP with Pydantic AI

AutoGen

Use Everhour MCP with AutoGen

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Google Sheets

Oauth2

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

Oauth2Api Key

Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.

Airtable

Oauth2Api Key

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

Oauth2

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.

FAQ

Frequently asked questions

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.

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

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.

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.

Start with Everhour.It takes 30 seconds.

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

Start building

How to integrate Everhour MCP with Mastra AI

Connect Everhour without auth hassles

Introduction

Also integrate Everhour with

TL;DR

What is Mastra AI?

What is the Everhour MCP server, and what's possible with it?

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for OpenAI and Composio

Install dependencies

Set up environment variables

Import libraries and validate environment

Create a Tool Router session for Everhour

Configure Mastra MCP client and fetch tools

Create the Mastra agent

Set up interactive chat interface

Complete Code

Conclusion

Supported Tools

How to build Everhour MCP Agent with another framework

Claude Code

Claude Cowork

OpenAI Agents SDK

Claude Agent SDK

Grok Bot

Codex

OpenClaw

Hermes

Atomic Agent

Google ADK

LangChain

Vercel AI SDK

LlamaIndex

CrewAI

Pydantic AI

AutoGen

Explore Other Toolkits

Google Sheets

Notion

Airtable

Asana

Frequently asked questions

What are the differences in Tool Router MCP and Everhour MCP?

Can I use Tool Router MCP with Mastra AI?

Can I manage the permissions and scopes for Everhour while using Tool Router?

How safe is my data with Composio Tool Router?

Start with Everhour.It takes 30 seconds.