How to integrate Constant Contact MCP with LlamaIndex

This guide walks you through connecting Constant Contact to LlamaIndex using the Composio tool router. By the end, you'll have a working Constant Contact agent that can create newsletter draft for new subscribers, list contacts added this week, segment inactive constant contact subscribers through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Constant Contact account through Composio's Constant Contact MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Constant Contact logoConstant Contact
Oauth2

Constant Contact is an email marketing and automation platform for small businesses. It helps teams build campaigns, manage contacts, and grow customer relationships.

93 Tools

Introduction

This guide walks you through connecting Constant Contact to LlamaIndex using the Composio tool router. By the end, you'll have a working Constant Contact agent that can create newsletter draft for new subscribers, list contacts added this week, segment inactive constant contact subscribers through natural language commands.

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

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

Also integrate Constant Contact with

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 Constant Contact
  • Connect LlamaIndex to the Constant Contact MCP server
  • Build a Constant Contact-powered agent using LlamaIndex
  • Interact with Constant Contact 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 Constant Contact MCP server, and what's possible with it?

The Constant Contact MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Constant Contact account. It provides structured and secure access so your agent can perform Constant Contact operations on your behalf.

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

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 Constant Contact account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Constant Contact

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
3

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
4

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 Constant Contact access
5

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 constant contact_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
6

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.

7

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: ["constant_contact"],
    },
  );

  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 Constant Contact 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, constant contact)
  • 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 Constant Contact tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

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 Constant Contact
  • 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 Constant Contact 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
9

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 Constant Contact
10

Run the agent

npx ts-node llamaindex-agent.ts

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

Complete Code

Here's the complete code to get you started with Constant Contact 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: ["constant_contact"],
    },
  );

  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 Constant Contact 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 Constant Contact to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Constant Contact 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 Constant Contact action and event your agent gets out of the box.

Add Account Email Address

Add a new email address to a Constant Contact account.

Add Contact Taggings

Add Tags to Contacts.

Add list memberships

Add Contacts to Lists creates an activity to add contacts to one or more contact lists.

Copy Event

POST (copy) an existing event in Constant Contact.

Count Contact Consents

GET contact consent counts for a Constant Contact account.

Create Contact

Create a new contact in Constant Contact.

Create contact from sign-up form

Create or Update a Contact via sign-up form.

Create Contact List

Create a new contact list in Constant Contact.

Create contact tag

POST (Create) a Tag.

Create Custom Field

Create a new custom field for contacts in Constant Contact.

Create Email Campaign

Create a new email campaign in Constant Contact.

Create Event

Create a new event with default settings in Constant Contact.

Create Resend to Non-openers

Create a resend to non-openers campaign activity for an email campaign.

Create Social Post

Create a new social media post campaign.

Delete contact

DELETE a specific contact from your Constant Contact account.

Delete Contact List

Permanently deletes a contact list from Constant Contact by its ID.

Create contact delete activity

Delete multiple contacts in bulk by submitting a contact_delete activity.

Delete contact tag

Delete a specific contact tag from your Constant Contact account.

Delete contact tags

Delete one or more tags from contacts in Constant Contact.

Delete custom field

DELETE a specific contact custom field from your Constant Contact account.

Delete custom fields

Delete one or more custom fields from a Constant Contact account.

Delete Email Campaign

DELETE an Email Campaign from your Constant Contact account.

Delete contact list activity

Delete one or more contact lists from your Constant Contact account by submitting a list delete activity.

Delete Segment

Permanently deletes a segment from Constant Contact by its ID.

Export Contacts

Create a bulk activity that exports contacts to a CSV file.

Get account physical address

GET the Physical Address for the Account.

Get account summary

GET a summary of account details for a Constant Contact account.

Get activity status

GET the status of a specific bulk activity.

Get contact

GET a contact by their unique ID.

Get contact activity summary report

GET contact tracking activity summary for a specific contact.

Get Contact List

GET details for a specific contact list by its ID.

Get Contact Open and Click Rates Report

GET average open and click rates for a contact.

Get Contacts Export File

Retrieve the exported contacts file from a completed export contacts activity.

Get Contact SMS Engagement History

GET SMS Engagement History for a Contact.

Get contact tag details

GET Tag Details - Retrieves detailed information about a specific contact tag.

Get custom field

GET a custom field by its unique ID.

Get email campaign details

GET details for a single email campaign using its campaign ID.

Get Email Campaign Activity

GET details for a specific email campaign activity by its ID.

Get email campaign activity preview

GET the HTML Preview of an Email Campaign Activity.

Get Email Campaign Activity Schedule

GET an email campaign activity schedule.

Get email campaign activity send history

GET the send history of an email campaign activity.

Get email campaign ID cross-references

GET a collection of V2 and V3 API Email Campaign ID cross-references.

Get Email Campaign Statistics Report

GET statistics for one or more email campaigns.

Get Event

GET details for a single event by its unique ID.

Get list ID cross-references

GET a collection of V2 and V3 API List IDs cross-references.

Get Partner Webhook Subscription

GET details for a specific Partner Webhook Topic Subscription by its ID.

Get resend to non-openers

GET Details for a Resend to Non-openers Campaign Activity.

Get Segment

GET details for a specific segment by its unique ID.

Import contacts from CSV file

Import contacts into Constant Contact from a CSV file.

Import contacts from JSON

Bulk import contacts into Constant Contact using JSON format.

List account email addresses

GET a Collection of Account Email Addresses.

List account user privileges

Get the user privileges associated with your access token.

List activity statuses

GET a collection of bulk activities.

List Contact Lists

GET all contact lists for the Constant Contact account.

List contacts

GET Contacts Collection to retrieve a list of contacts from Constant Contact.

List contact tags

GET Details for All Tags - Retrieves all contact tags for the account.

List contact custom fields

GET custom_fields Collection to retrieve all contact custom field definitions.

List Email Campaigns

GET a collection of email campaigns from Constant Contact.

List Email Campaign Summaries Report

GET an Email Campaigns Summary Report from Constant Contact.

List Email Did Not Opens Report

GET an Email Did Not Opens Report to retrieve a list of contacts who did not open a specific email campaign.

List email forwards report

GET an Email Forwards Report for a specific email campaign activity.

List email opt-outs report

GET an Email Opt-outs Report for a specific email campaign activity.

List Email Unique Opens Report

GET an email unique opens report for a campaign activity.

List Events

GET a collection of events from Constant Contact.

List event track registrations

GET registrations for an event track to retrieve a list of registrations.

List Landing Page Contact Opens Report

GET a Contacts Opens Landing Page Report.

List Landing Page Unique Contact Adds Report

GET a Unique Contacts Adds Landing Page Report for a specific landing page campaign activity.

List Landing Page Unique Contact Clicks Report

GET unique contact clicks data for a landing page campaign.

List Landing Page Unique Contact Opens Report

GET a Unique Contacts Opens Landing Page Report to retrieve a list of contacts who uniquely opened a specific landing page campaign.

List landing page unique contact updates report

GET a Unique Contacts Updates Landing Page Report for a specific landing page campaign activity.

List Segments

GET all segments for the Constant Contact account.

List SMS Campaign Summaries Report

GET an SMS Campaigns Summary Report.

List Social Connections

GET social network connections for a Constant Contact account.

List Social Hashtag Groups

GET hashtag groups - Retrieves a paginated list of social hashtag groups.

List Social Profiles

GET social media profiles from Constant Contact.

Remove Contact Tagging

Remove tagging from contacts in Constant Contact.

Remove Tags from Contacts

Remove tags from contacts in Constant Contact.

Remove contacts from lists

Create a Remove Contacts from Lists activity to remove contacts from one or more lists.

Rename Email Campaign

PATCH (Update) the name of an existing email campaign in Constant Contact.

Rename Segment

PATCH (rename) an existing segment in Constant Contact.

Resubscribe Contact

Resubscribe an unsubscribed contact to one or more contact lists.

Undo Event Ticket Check-In

Undo check-in for event tickets.

Update Account Details

PUT (update) Account Details for the authenticated user.

Update Account Physical Address

PUT (update) the Physical Address for an Account.

Update Contact

PUT (update) an existing contact in Constant Contact.

Update Contact List

PUT (update) an existing contact list in Constant Contact.

Update Contact Tag

PUT (Update) a Tag.

Update Custom Field

Update an existing contact custom field in Constant Contact.

Update Email Campaign Activity

PUT (Update) an Email Campaign Activity in Constant Contact.

Update Event

PATCH (update) an existing event in Constant Contact.

Update Event Track Registration Payment Status

Update the payment status for event track registrations in Constant Contact.

Update Event Track Registrations

PUT (update) registration status for event track registrations.

Update Segment

PUT (update) an existing segment in Constant Contact.

FAQ

Frequently asked questions

With a standalone Constant Contact MCP server, the agents and LLMs can only access a fixed set of Constant Contact tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Constant Contact 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 Constant Contact tools.

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

Start with Constant Contact.It takes 30 seconds.

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

Start building