How to integrate Clockify MCP with LlamaIndex

This guide walks you through connecting Clockify to LlamaIndex using the Composio tool router. By the end, you'll have a working Clockify agent that can list all your active workspaces, add a new client to marketing workspace, show all users on design team workspace through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Clockify account through Composio's Clockify MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for free Get a demo

Clockify

Api KeyOauth2

Clockify is a free time tracking software for individuals and teams to monitor work hours across projects. Track, manage, and report time for better productivity and transparency.

73 Tools

Managed auth

Connect Clockify without auth hassles

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

Try for free

Introduction

This guide will help you understand how to give your LlamaIndex agent real control over a Clockify account through Composio's Clockify MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Clockify with

OpenAI Agents SDK Claude Agent SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI CrewAI

TL;DR

Here's what you'll learn:

Set your OpenAI and Composio API keys
Install LlamaIndex and Composio packages
Create a Composio Tool Router session for Clockify
Connect LlamaIndex to the Clockify MCP server
Build a Clockify-powered agent using LlamaIndex
Interact with Clockify through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

ReAct Agent: Reasoning and acting pattern for tool-using agents
MCP Tools: Native support for Model Context Protocol
Context Management: Maintain conversation context across interactions
Async Support: Built for async/await patterns

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

The Clockify MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Clockify account. It provides structured and secure access to your team's time tracking data, so your agent can perform actions like managing clients, handling workspace users, setting up webhooks, and retrieving workspace details on your behalf.

Workspace user management: Let your agent list all users in a workspace, filter users by advanced criteria, or find team managers for more efficient team organization.
Client creation and deletion: Easily create new clients or remove existing ones from your workspace, streamlining project onboarding and cleanup.
Webhook automation: Enable your agent to create, delete, and manage webhooks for real-time notifications and integrations with other tools.
Workspace overview and navigation: Retrieve a list of all workspaces you belong to, empowering your agent to access and organize time tracking across multiple teams or projects.
Addon and webhook token management: Generate new webhook tokens and list all addon webhooks, ensuring secure and automated integrations with third-party services.

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 step10 STEPS

Prerequisites

Before you begin, make sure you have:

Python 3.8/Node 16 or higher installed
A Composio account with the API key
An OpenAI API key
A Clockify account and project
Basic familiarity with async Python/Typescript

Getting API Keys for OpenAI, Composio, and Clockify

OpenAI API key (OPENAI_API_KEY)

Go to the OpenAI dashboard
Create an API key if you don't have one
Assign it to OPENAI_API_KEY in .env

Composio API key and user ID

Log into the Composio dashboard
Copy your API key from Settings
- Use this as COMPOSIO_API_KEY
Pick a stable user identifier (email or ID)
- Use this as COMPOSIO_USER_ID

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

@composio/llamaindex: Composio's LlamaIndex integration
@llamaindex/openai: OpenAI LLM integration
@llamaindex/tools: MCP client for LlamaIndex
@llamaindex/workflow: Workflow framework for LlamaIndex
dotenv: Environment variable management

Set environment variables

bash

OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

Authenticate with OpenAI's GPT-5 model
Connect to Composio's Tool Router
Identify your Composio user session for Clockify access

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called clockify_llamaindex_agent.ts and import the required modules:

Key imports:

dotenv.config loads .env at runtime
readline gives us a simple CLI chat loop
Composio is the main Composio SDK client
mcp connects to an MCP endpoint
createAgent builds a LlamaIndex agent
openai configures the LLM backend

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["clockify"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Clockify actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

We create a Composio client using your API key and configure it with the LlamaIndex provider
We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, clockify)
The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
LlamaIndex will connect to this endpoint to dynamically discover and use the available Clockify tools.
The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

We're creating a direct terminal interface to chat with Clockify
The LLM's responses are streamed to the CLI for faster interaction.
The agent uses context to maintain conversation history
The agent processes the request, selects appropriate Clockify tools, and returns a result
We extract the answer from the result data structure and display it to the user
You can type 'quit' or 'exit' to stop the chat loop gracefully
Agent responses and any errors are streamed in a clear, readable format

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

We're orchestrating the entire application flow
The agent gets built with proper error handling
Then we kick off the interactive chat loop so you can start talking to Clockify

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Clockify, then start asking questions.

Complete Code

Here's the complete code to get you started with Clockify and LlamaIndex:

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["clockify"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Clockify actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Clockify to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:

Tool Router dynamically exposes Clockify tools through an MCP endpoint
LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
The agent becomes more capable without increasing prompt size
Async Python provides clean, efficient execution of agent workflows

You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.

TOOLS

Supported Tools

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

Add User to Group

Tool to add a user to a user group in a Clockify workspace.

Create Client

Tool to add a new client to a workspace.

Create New Project

Tool to create a new project in a Clockify workspace.

Create Shared Report

Tool to create a shared report in Clockify.

Create Task

Tool to add a new task to a project in Clockify.

Create Templates On Workspace

Tool to create templates on a Clockify workspace.

Create Time Entry

Tool to create a new time entry in a Clockify workspace.

Create User Group

Tool to create a new user group in a workspace.

Create User Time Entry

Tool to create a time entry for another user in a Clockify workspace.

Create Webhook

Tool to create a new webhook in a workspace.

Create Workspace

Tool to create a new workspace in Clockify.

Delete Client

Permanently deletes a client from a Clockify workspace.

Delete Project

Tool to delete a project from a workspace.

Delete Shared Report

Tool to delete a shared report from a workspace by ID.

Delete Tag

Tool to delete a tag from a Clockify workspace.

Delete Task

Tool to delete a task from a project in Clockify.

Delete Template

Tool to delete a template from a Clockify workspace.

Delete Time Entry

Tool to delete a time entry from a workspace by ID.

Delete User Group

Tool to delete a user group from a workspace.

Delete User Time Entries

Tool to delete multiple time entries for a user in a workspace.

Delete Webhook

Tool to delete a webhook from a workspace.

Duplicate Time Entry

Tool to duplicate an existing time entry in a Clockify workspace.

Filter Workspace Users

Tool to filter users in a workspace by advanced criteria.

Find User's Team Managers

Retrieves the list of team managers assigned to a specific user in a Clockify workspace.

Generate Detailed Report

Tool to generate a detailed time entry report with filtering and pagination.

Generate Expense Report

Tool to generate a detailed expense report for a Clockify workspace.

Generate New Webhook Token

Tool to generate a new webhook token.

Generate Summary Report

Tool to generate a summary report for time entries in a Clockify workspace.

Generate Weekly Report

Tool to generate a weekly time entry report for a workspace with grouped data.

Get All Addon Webhooks

Tool to list all webhooks for an addon in a workspace.

Get All My Workspaces

Tool to list all workspaces the user belongs to.

Get All Webhooks

Tool to list all webhooks in a workspace.

Get Client By ID

Retrieves detailed information about a specific client in a Clockify workspace.

Get Clients

Tool to list clients in a workspace.

Get Created Entities

Tool to retrieve created entities within a workspace (Experimental).

Get Currently Logged In User Info

Tool to retrieve info about the authenticated user.

Get Deleted Entities

Tool to retrieve information about entities deleted within a date range (Experimental API).

Get Holidays

Tool to retrieve all holidays for a workspace.

Get Holidays In Period

Tool to retrieve holidays in a specific period.

Get In Progress Time Entries

Tool to retrieve all currently running time entries in a workspace.

Get member's profile

Tool to get a member's profile in a workspace.

Get Project

Tool to retrieve detailed information about a specific project by ID.

Get Projects

Tool to list projects in a workspace with filtering and pagination.

Get Shared Report

Tool to retrieve a shared report by ID from Clockify.

Get Shared Reports

Tool to retrieve all shared reports in a workspace.

Get Tag By ID

Tool to retrieve detailed information about a specific tag by ID in a Clockify workspace.

Get Tags

Tool to find and list tags in a workspace.

Get Task

Retrieves detailed information about a specific task in a Clockify project.

Get Tasks

Tool to find all tasks on a specific project in a workspace.

Get Templates On Workspace

Tool to list all templates in a workspace.

Get Time Entries

Tool to retrieve historical time entries for a user in a workspace with filters.

Get Time Entry

Tool to retrieve a specific time entry by ID from a workspace.

Get Updated Entities

Tool to retrieve entities that have been updated in a workspace (Experimental).

Get User Groups

Tool to find all user groups in a workspace.

Get Webhook By ID

Retrieves detailed information about a specific webhook in a Clockify workspace.

Get Webhook Logs

Tool to retrieve webhook logs for a specific webhook.

Get Workspace Info

Retrieves detailed information about a specific Clockify workspace.

List Assignments

Tool to retrieve all scheduling assignments in a workspace.

Remove User From Group

Tool to remove a user from a group in Clockify.

Stop User Timer

Tool to stop a currently running timer for a user in a workspace.

Update Client

Tool to update an existing client in a Clockify workspace.

Update Project

Tool to update an existing project in a Clockify workspace.

Update Project Memberships

Tool to update project memberships in Clockify.

Update Project User Hourly Rate

Tool to update a project user's billable rate.

Update Shared Report

Tool to update an existing shared report in Clockify.

Update Tag

Tool to update a tag in a Clockify workspace.

Update Task

Tool to update an existing task on a project in Clockify.

Update Time Entries

Tool to bulk update multiple time entries in a Clockify workspace.

Update Time Entry

Tool to update an existing time entry in a Clockify workspace.

Update User Group

Tool to update an existing user group in a workspace.

Update User Hourly Rate

Tool to update a user's hourly rate in a Clockify workspace.

Update Webhook

Tool to update a webhook in a workspace.

Update Workspace Hourly Rate

Tool to update the workspace billable hourly rate.

FRAMEWORKS

How to build Clockify MCP Agent with another framework

OpenAI Agents SDK

Use Clockify MCP with OpenAI Agents SDK

Claude Agent SDK

Use Clockify MCP with Claude Agent SDK

Claude Code

Use Clockify MCP with Claude Code

Claude Cowork

Use Clockify MCP with Claude Cowork

Codex

Use Clockify MCP with Codex

OpenClaw

Use Clockify MCP with OpenClaw

Hermes

Use Clockify MCP with Hermes

CLI

Use Clockify MCP with CLI

Google ADK

Use Clockify MCP with Google ADK

LangChain

Use Clockify MCP with LangChain

Vercel AI SDK

Use Clockify MCP with Vercel AI SDK

Mastra AI

Use Clockify MCP with Mastra AI

CrewAI

Use Clockify MCP with CrewAI

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 Clockify MCP server, the agents and LLMs can only access a fixed set of Clockify tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Clockify and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. LlamaIndex 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 Clockify tools.

Yes, absolutely. You can configure which Clockify 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 Clockify data and credentials are handled as safely as possible.

Start with Clockify.It takes 30 seconds.

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

Start building

Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREE BOOK A DEMO

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati

Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya

Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave

CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu

Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola

Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche

Co-Founder, Ingram Technologies