How to integrate Nango MCP with Google ADK

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Nango logo
Google ADK logo
divider

Introduction

This guide walks you through connecting Nango to Google ADK using the Composio tool router. By the end, you'll have a working Nango agent that can list all connected crm accounts, trigger manual sync with salesforce provider, get configuration for all available scripts through natural language commands.

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

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

Also integrate Nango with

TL;DR

Here's what you'll learn:
  • Get a Nango account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Nango
  • Build an agent that connects to Nango through MCP
  • Interact with Nango 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 Nango MCP server, and what's possible with it?

The Nango MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Nango account. It provides structured and secure access to your integrations, so your agent can perform actions like triggering syncs, managing connections, listing providers, and executing workflow actions across 250+ external APIs on your behalf.

  • Connection management and discovery: Effortlessly list all your existing Nango connections, view metadata, or retrieve connection information without exposing sensitive credentials.
  • Provider information and browsing: Ask your agent to list all available providers or fetch detailed configuration info for a specific provider, making it easy to discover and set up new integrations.
  • Triggering workflow actions: Direct your agent to execute custom workflow actions by specifying the connection, provider, and action identifiers—unlocking advanced automation across connected platforms.
  • Manual sync initiation: Have your agent trigger sync processes for any established connection, ensuring your data stays up-to-date across all integrated services.
  • Script configuration retrieval: Let your agent fetch Nango scripts configuration and triggers, enabling more tailored and automated integration flows.

Supported Tools & Triggers

Tools
Trigger Nango ActionTrigger a Nango action to execute a workflow or operation.
Add ConnectionTool to add a connection with existing credentials to Nango.
List ConnectionsList all Nango connections without credentials.
Create Connect SessionTool to create a new connect session with a 30-minute lifespan for enabling connection creation via Connect UI.
Create IntegrationTool to create a new integration in Nango.
Delete ConnectionTool to delete a specific Nango connection.
Delete IntegrationTool to delete a specific integration by its unique key.
Edit ConnectionTool to edit a connection's tags and metadata.
Get Connection with CredentialsRetrieve a specific connection with its credentials.
Get Environment VariablesTool to retrieve environment variables from the Nango dashboard.
Get IntegrationRetrieve detailed configuration for a specific Nango integration by its unique key.
Proxy GET RequestTool to make a GET request with Nango's Proxy to forward requests to external APIs while managing authentication.
Get Sync StatusTool to get the status of specified sync(s) for a connection or all connections.
List ConnectionsTool to list all connections without credentials.
List IntegrationsTool to retrieve a list of all configured integrations.
Get Provider DetailsRetrieve detailed configuration for a specific Nango provider by its unique key.
List ProvidersTool to retrieve a list of all available providers.
Proxy PUT RequestTool to make a PUT request with the Nango Proxy to forward requests to external APIs while managing authentication.
Reconnect SessionCreate a new connect session to reconnect to a specific integration.
Get Integration Functions ConfigurationRetrieve all integration functions configuration from Nango.
Set Connection MetadataTool to set custom metadata for one or more Nango connections.
Trigger SyncTool to trigger sync process(es) manually.
Update Connection MetadataTool to edit custom metadata for one or multiple connections.
Update IntegrationTool to update an existing integration's configuration.

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

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

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.

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 Nango via MCP
  • python-dotenv loads environment variables

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

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

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

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=["nango"],
)

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

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 Nango 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

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 Nango 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=["nango"],
)

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 Nango operations."
    ),  
    tools=[composio_toolset],
)

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

Conclusion

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

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Nango 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.

How to build Nango MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Nango MCP with ChatGPT

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Nango MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Nango MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Nango MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Nango MCP with Claude Cowork

Codex logo

Codex

Use Nango MCP with Codex

Cursor logo

Cursor

Use Nango MCP with Cursor

OpenClaw logo

OpenClaw

Use Nango MCP with OpenClaw

Hermes logo

Hermes

Use Nango MCP with Hermes

CLI logo

CLI

Use Nango MCP with CLI

LangChain logo

LangChain

Use Nango MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Nango MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Nango MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Nango MCP with LlamaIndex

CrewAI logo

CrewAI

Use Nango MCP with CrewAI

OpenCode logo

OpenCode

Use Nango MCP with OpenCode

VS Code logo

VS Code

Use Nango MCP with VS Code

FAQ

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

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

Can I use Tool Router MCP with Google ADK?

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

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

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

Get started for freeGet a demo↗