How to integrate Neo4J MCP with Google ADK

This guide walks you through connecting Neo4J to Google ADK 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 Google ADK 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 Google ADK 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 Google ADK 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 Neo4J account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Neo4J
  • Build an agent that connects to Neo4J through MCP
  • Interact with Neo4J using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

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

Prerequisites

Before starting, make sure you have:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python
2

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.
3

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Neo4J via MCP
  • python-dotenv loads environment variables
4

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file
5

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management
6

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

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.")
What's happening:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP
7

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["neo4j"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration
8

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Neo4J operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls
9

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

Here's the complete code to get you started with Neo4J and Google ADK:

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

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.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["neo4j"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Neo4J operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Neo4J with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Neo4J using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Neo4J tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

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. Google ADK 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