How to integrate Clickmeeting MCP with Mastra AI

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Clickmeeting logo
Mastra AI logo
divider

Introduction

This guide walks you through connecting Clickmeeting to Mastra AI using the Composio tool router. By the end, you'll have a working Clickmeeting agent that can schedule a new webinar for next week, add attendee to upcoming training session, generate pdf report for yesterday's session through natural language commands.

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

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

Also integrate Clickmeeting with

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 Clickmeeting tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Clickmeeting 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 Clickmeeting 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 Clickmeeting MCP server, and what's possible with it?

The Clickmeeting MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Clickmeeting account. It provides structured and secure access to your webinars and meetings, so your agent can perform actions like scheduling conferences, managing contacts, generating reports, handling recordings, and more—all on your behalf.

  • Automated conference creation and scheduling: Seamlessly instruct your agent to create new meetings or webinars, helping you organize virtual events in seconds.
  • Contact management and attendee registration: Have your agent add or pre-register participants as contacts before scheduling or starting events, ensuring a smooth entry process.
  • Recording management and cleanup: Direct your agent to delete specific recordings or clear all session recordings for a conference room, keeping your account tidy and compliant.
  • Instant session analytics and reporting: Ask your agent to generate detailed PDF reports for any session, so you can quickly access valuable insights and analytics.
  • Easy access and participation links: Let your agent generate autologin URLs for participants, allowing direct, hassle-free entry to your meetings without manual logins.

Supported Tools & Triggers

Tools
Create Access TokensTool to generate access tokens for conference participants.
Create ConferenceTool to create a new conference.
Create ContactTool to create a new contact in your ClickMeeting account.
Delete ConferenceTool to delete a specific conference.
Delete FilePermanently delete a file from the ClickMeeting file library.
Delete RecordingPermanently delete a specific recording from a conference room.
Delete RecordingsTool to delete all recordings for a conference room.
Download FileDownload the content of a specific file from the ClickMeeting file library.
Generate Autologin HashGenerate an autologin hash for a conference participant.
Generate Session PDF ReportGenerates a PDF report containing analytics and details for a specific conference session.
Get Chat DetailsTool to retrieve details of a specific chat session.
Get ChatsTool to retrieve a list of all chat sessions.
Get Conference DetailsRetrieve detailed information about a specific ClickMeeting conference room.
Get Conference FilesRetrieves the list of files uploaded to a specific conference room's file library.
Get ConferencesRetrieve a list of conference rooms from your ClickMeeting account filtered by status.
Get Conference SessionsRetrieves past sessions for a conference room.
Get Conference SkinsRetrieves a list of available conference room skins that can be used to customize the appearance of webinar/meeting rooms.
Get File DetailsRetrieve detailed information about a specific file from the ClickMeeting file library.
Get File LibraryRetrieve a list of files from the ClickMeeting file library.
Get Phone GatewaysRetrieve available phone dial-in numbers for ClickMeeting webinars.
Ping APITool to check API service status.
Get RegistrationsTool to retrieve registrations for a conference room by status.
Get Session AttendeesRetrieves the list of attendees who participated in a specific session of a conference room.
Get Session DetailsRetrieve detailed statistics for a specific past conference session.
Get Session Poll DetailsTool to retrieve details of a specific poll conducted during a session.
Get Session Q&A HistoryTool to retrieve the Q&A history for a specific session.
Get Session RecordingsRetrieve all recordings for a conference room.
Get Session RegistrationsRetrieve registrations for a specific session within a conference room.
Get Session Survey DetailsTool to retrieve details of a specific survey/poll conducted during a session.
Get Session SurveysRetrieves the list of surveys conducted during a specific conference session.
Get Time Zone ListRetrieves all available time zones supported by ClickMeeting.
Get Time Zone List by CountryRetrieve available time zones for a specific country by ISO 3166-1 alpha-2 country code.
Get Token By EmailTool to retrieve access tokens assigned to a specific email address for a token-protected conference room.
List Access TokensTool to retrieve all generated access tokens for a token-protected conference room.
List Registrations By StatusTool to retrieve registered participants of a conference room filtered by registration status.
Register ParticipantTool to register a participant for a conference room.
Send InvitationTool to send invitation emails to participants for a ClickMeeting conference.
Update ConferenceTool to update an existing conference room's parameters.
Upload FileUpload a file to the ClickMeeting file library.

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:
  • 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 Clickmeeting 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 Clickmeeting

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

  const composioMCPUrl = session.mcp.url;
  console.log("Clickmeeting MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "clickmeeting" for Clickmeeting 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 Clickmeeting toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "clickmeeting-mastra-agent",
    instructions: "You are an AI agent with Clickmeeting 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: {
        clickmeeting: 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 Clickmeeting 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 Clickmeeting 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: ["clickmeeting"],
  });

  const composioMCPUrl = session.mcp.url;

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

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "clickmeeting-mastra-agent",
    instructions: "You are an AI agent with Clickmeeting 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: { clickmeeting: 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 Clickmeeting 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

How to build Clickmeeting MCP Agent with another framework

FAQ

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

With a standalone Clickmeeting MCP server, the agents and LLMs can only access a fixed set of Clickmeeting tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Clickmeeting and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Mastra AI?

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 Clickmeeting tools.

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

Yes, absolutely. You can configure which Clickmeeting 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 Clickmeeting 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.