How to integrate Neo4J MCP with CrewAI

This guide walks you through connecting Neo4J to CrewAI using the Composio tool router. By the end, you'll have a working Neo4J agent that can run cypher queries on customer graph, find shortest paths between accounts, create nodes for new transactions through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Neo4J account through Composio's Neo4J MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Neo4J logoNeo4J
Oauth2BasicApi KeyS2s Oauth2

Neo4J is a graph database platform for storing and querying connected data. Use it to model relationships, run Cypher queries, and power real-time graph analytics.

21 Tools

Introduction

This guide walks you through connecting Neo4J to CrewAI using the Composio tool router. By the end, you'll have a working Neo4J agent that can run cypher queries on customer graph, find shortest paths between accounts, create nodes for new transactions through natural language commands.

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

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

Also integrate Neo4J with

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Neo4J connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Neo4J
  • Build a conversational loop where your agent can execute Neo4J 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 Neo4J MCP server, and what's possible with it?

The Neo4J MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Neo4J account. It provides structured and secure access to your Neo4J Aura resources, so your agent can manage database instances, handle snapshots, review projects and users, monitor Graph Data Science sessions, and configure IP filters on your behalf.

  • Aura instance management: Have your agent list, create, inspect, update, or pause Neo4J Aura instances based on your infrastructure needs.
  • Snapshot and recovery operations: Direct your agent to create snapshots, review available backups, inspect snapshot details, or restore an Aura instance from a snapshot.
  • Project and user oversight: Let the agent list Aura projects, inspect project details, review project users, or retrieve information about an organization user.
  • Graph Data Science planning: Instruct your agent to list active Graph Data Science sessions or estimate session size from node counts, relationship counts, and algorithm categories.
  • Network access and agent review: Have your agent list Aura agents, review organization IP filters, or update an existing IP filter.

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

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Neo4J connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python
2

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.
3

Install dependencies

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

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
5

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 Neo4J MCP URL
6

Create a Composio Tool Router session for Neo4J

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

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

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.
8

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 Neo4J 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=["neo4j"],
)
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 Neo4J through Composio's Tool Router. The agent can perform Neo4J 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
TOOLS

Supported Tools

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

Aggregate Directors Count

Executes a directorsAggregate GraphQL query to count directors in Neo4j.

Create Neo4j Aura Instance

Creates a new Neo4j Aura instance with the specified configuration.

Create Neo4j Aura Snapshot

Create an on-demand snapshot of a Neo4j Aura instance.

Estimate GDS Session Size

Estimate the size of a new GDS (Graph Data Science) session based on node/relationship counts and algorithm categories.

Get Neo4j Aura Instance Details

Retrieves details for a specific Neo4j Aura instance using its unique instance ID.

Get Neo4j Aura Organization User

Retrieves details of a specific user in a Neo4j Aura organization.

Get Neo4j Aura Project Details

Retrieve details of a specific Neo4j Aura project (tenant).

Get Neo4j Aura Project Details (v1beta5)

Retrieve details of a specific Neo4j Aura project (tenant) using the v1beta5 API.

Get Neo4j Aura Snapshot Details

Retrieves details of a specific snapshot for a Neo4j Aura instance.

List Neo4j Aura Agents

List all agents belonging to a specific Neo4j Aura project.

List GDS Sessions

List all Graph Data Science (GDS) sessions for the authenticated Neo4j Aura account.

List Neo4j Aura Instances

Returns a list of Neo4j Aura instances.

List IP Filters

Returns a list of IP filters configured for a Neo4j Aura organization.

List Aura Projects

List all Aura projects (tenants) available to the authenticated user.

List Project Users

List all users in a specific Neo4j Aura project.

List Neo4j Aura Snapshots

Lists available snapshots for a Neo4j Aura instance.

Pause Neo4j Aura Instance

Pauses a Neo4j Aura instance.

Restore Neo4j Aura Instance from Snapshot

Restore a Neo4j Aura instance from a snapshot.

Update Neo4j Aura Instance

Updates a Neo4j Aura instance configuration.

Update Neo4j Aura Instance

Edits the configuration of a Neo4j Aura instance.

Update IP Filter

Updates an existing IP filter for a Neo4j Aura organization.

FAQ

Frequently asked questions

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

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

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

Start with Neo4J.It takes 30 seconds.

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

Start building