How to Use the Campaign Monitor MCP in LlamaIndex

Q: How do I index Campaign Monitor list statistics in LlamaIndex?

You run getliststatistics via the MCP tool spec and pass the output to your LlamaIndex document parser. This indexes your active subscriber counts and bounce rates so your LlamaIndex agent can search and analyze list health.

Q: Can LlamaIndex update a Campaign Monitor list during a query session?

Yes, your LlamaIndex FunctionAgent can invoke addsubscriber if a user requests to join a Campaign Monitor list. The LlamaIndex agent executes the tool call and immediately updates the index with the new subscriber status.

Q: How does this Campaign Monitor MCP Server handle multiple clients in LlamaIndex?

The LlamaIndex agent calls listclients to find the correct ID, then filters downstream Campaign Monitor queries. LlamaIndex keeps these client contexts separate within your vector store using metadata tags.

Q: Can I filter which Campaign Monitor tools LlamaIndex can access?

Setting up the allowedtools filter when configuring the MCP tool spec in LlamaIndex lets you restrict access. This lets you restrict your LlamaIndex agent to read-only Campaign Monitor tools like listsentcampaigns while blocking write actions.

Index Campaign Monitor performance and subscriber data directly into your LlamaIndex RAG pipeline.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Campaign Monitor MCP to LlamaIndex

Create your Vinkius account to connect Campaign Monitor to LlamaIndex and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Campaign Monitor with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Query Campaign Monitor metrics with LlamaIndex RAG

Retrieving raw performance metrics from Campaign Monitor and feeding them straight into your LlamaIndex vector store is the job of the `get_campaign_analytics` tool. Your LlamaIndex pipeline indexes these Campaign Monitor email open and click rates, making live marketing data searchable via natural language queries. Instead of guessing which Campaign Monitor campaigns worked, your LlamaIndex agent queries the indexed results to find historical trends. This MCP integration turns raw Campaign Monitor API responses into a grounded LlamaIndex knowledge base that prevents your LLM from hallucinating past performance.

Build a dynamic Campaign Monitor subscriber knowledge base

Fetching profile data and history from Campaign Monitor for any given email address inside your LlamaIndex index is done via the `get_subscriber_details` tool. LlamaIndex ingests this structured Campaign Monitor data, allowing your agent to answer specific questions about user engagement during support search queries. Combining this with `get_list_statistics` lets you index general Campaign Monitor list health alongside individual profiles in LlamaIndex. Your LlamaIndex query engine matches subscriber actions with overall Campaign Monitor list trends to give you a complete picture of audience behavior.

Map marketing structures via MCP Server tools

Mapping out how your Campaign Monitor audiences are segmented across different client accounts inside LlamaIndex relies on the `list_subscriber_lists` tool. LlamaIndex uses this structural Campaign Monitor data to route user queries to the correct list context during search tasks. By calling `list_clients` first, your LlamaIndex indexer builds a clear map of your entire Campaign Monitor account hierarchy. The resulting LlamaIndex index ensures your agent always queries the right Campaign Monitor client list without mixing up customer data.

Setup guide

Set up Campaign Monitor MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Campaign Monitor MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Campaign Monitor tools.",
)
response = await agent.run("List recent Campaign Monitor data")

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Campaign Monitor. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Campaign Monitor now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Campaign Monitor MCP in LlamaIndex

You run `get_list_statistics` via the MCP tool spec and pass the output to your LlamaIndex document parser. This indexes your active subscriber counts and bounce rates so your LlamaIndex agent can search and analyze list health.

Yes, your LlamaIndex FunctionAgent can invoke `add_subscriber` if a user requests to join a Campaign Monitor list. The LlamaIndex agent executes the tool call and immediately updates the index with the new subscriber status.

The LlamaIndex agent calls `list_clients` to find the correct ID, then filters downstream Campaign Monitor queries. LlamaIndex keeps these client contexts separate within your vector store using metadata tags.

Setting up the allowed_tools filter when configuring the MCP tool spec in LlamaIndex lets you restrict access. This lets you restrict your LlamaIndex agent to read-only Campaign Monitor tools like `list_sent_campaigns` while blocking write actions.

Raw Campaign Monitor subscriber profiles and email addresses are processed in memory and never persist on Vinkius servers. You control where LlamaIndex writes the final vector embeddings, ensuring your customer data stays in your secure database.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript