How to integrate Simplekpi MCP with CrewAI

Framework Integration Gradient
Simplekpi Logo
CrewAI Logo
divider

Introduction

This guide walks you through connecting Simplekpi to CrewAI using the Composio tool router. By the end, you'll have a working Simplekpi agent that can show me top performing kpis this month, add a new kpi for sales pipeline, generate a report on marketing metrics through natural language commands.

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

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

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Simplekpi connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Simplekpi
  • Build a conversational loop where your agent can execute Simplekpi operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

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

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

Supported Tools & Triggers

Tools
Add User Group ItemTool to assign a group item to a user in SimpleKPI.
Add User KPITool to assign a KPI to a user in SimpleKPI.
Create Category KPITool to create a new KPI within a category in SimpleKPI.
Create GroupTool to create a new group in SimpleKPI.
Create Group ItemTool to create a new item within a group in SimpleKPI.
Create KPITool to create a new KPI with specified configuration.
Create KPI CategoryTool to create a new KPI category in SimpleKPI.
Create KPI UnitTool to create a new KPI unit in SimpleKPI.
Batch KPI EntriesTool to batch create or update multiple KPI entries at once.
Create UserTool to create a new user account in SimpleKPI.
Delete Category KPITool to delete a KPI from a category.
Delete GroupTool to delete a group by ID.
Delete Group ItemTool to delete a group item by ID.
Delete KPITool to delete a KPI by ID.
Delete KPI CategoryTool to delete a KPI category by its ID.
Delete KPI EntryTool to delete a KPI entry by ID.
Delete KPI UnitTool to delete a KPI unit by its ID.
Delete UserTool to delete a user account by ID.
Delete User Group ItemTool to remove a group item assignment from a user.
Delete User KPITool to remove a KPI assignment from a user.
Get All Data EntriesTool to retrieve processed KPI data entries for reports including calculated KPIs.
Get Category KPITool to retrieve a specific KPI within a category.
Get GroupTool to get a specific group by ID from SimplekPI.
Get Group ItemTool to retrieve a specific group item by ID.
Get KPI by IDTool to retrieve a specific KPI by ID from SimpleKPI.
Get KPI CategoryTool to get a specific KPI category by ID from SimpleKPI.
Get KPI EntryTool to retrieve a specific KPI entry by ID.
Get KPI FrequencyTool to get a specific KPI frequency by ID from SimplekPI.
Get KPI Icon by IDTool to retrieve a specific KPI icon by ID.
Get KPI UnitTool to get a specific KPI unit by ID from SimpleKPI.
Get User by IDTool to retrieve a specific user by ID.
Get User Group ItemTool to get a specific group item assigned to a user.
Get User KPITool to retrieve a specific KPI assigned to a user.
List Category KPIsTool to retrieve all KPIs within a specific category.
List Group ItemsTool to get all items within a group.
List GroupsTool to retrieve all groups from SimpleKPI.
List KPI CategoriesTool to get all KPI categories.
List KPI EntriesTool to get all KPI entries filtered by date range and optional criteria.
List KPI FrequenciesTool to get all KPI frequencies.
List KPI IconsTool to retrieve all KPI icons from SimpleKPI.
List All KPIsTool to retrieve all KPIs from a SimpleKPI account.
List All KPI UnitsTool to retrieve all KPI units from a SimpleKPI account.
List User Group ItemsTool to get all group items assigned to a user.
List User KPIsTool to get all KPIs assigned to a specific user.
Update Category KPITool to update a KPI within a category.
Update GroupTool to update an existing group in SimpleKPI.
Update Group ItemTool to update an existing item in a SimpleKPI group.
Update KPITool to update an existing KPI in SimpleKPI.
Update KPI EntryTool to update an existing KPI entry in SimpleKPI.
Update KPI UnitTool to update an existing KPI unit in SimpleKPI.
Update UserTool to update an existing user account in SimpleKPI.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router 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:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Simplekpi connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Simplekpi via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
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 with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model

Import dependencies

python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Simplekpi MCP URL

Create a Composio Tool Router session for Simplekpi

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["simplekpi"])

url = session.mcp.url
What's happening:
  • You create a Simplekpi only session through Composio
  • Composio returns an MCP HTTP URL that exposes Simplekpi tools

Initialize the MCP Server

python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
What's Happening:
  • Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
  • MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
  • Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
  • Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
  • Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.

Create a CLI Chatloop and define the Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's Happening:
  • Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
  • Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
  • Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
  • Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
  • Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
  • Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

Here's the complete code to get you started with Simplekpi and CrewAI:

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["simplekpi"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Simplekpi through Composio's Tool Router. The agent can perform Simplekpi operations through natural language commands.

Next steps:

  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations

How to build Simplekpi MCP Agent with another framework

FAQ

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

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

Can I use Tool Router MCP with CrewAI?

Yes, you can. CrewAI 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 Simplekpi tools.

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

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