How to integrate Ynab 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

Ynab logo
Google ADK logo
divider

Introduction

This guide walks you through connecting Ynab to Google ADK using the Composio tool router. By the end, you'll have a working Ynab agent that can show your spending by category this week, add a new expense to groceries, list upcoming scheduled transactions through natural language commands.

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

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

Also integrate Ynab with

TL;DR

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

The Ynab MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Ynab account. It provides structured and secure access to your budgeting data, so your agent can perform actions like tracking expenses, creating and adjusting budgets, fetching transaction history, and analyzing spending patterns on your behalf.

  • Automated transaction tracking: Let your agent fetch, categorize, or summarize recent transactions to keep your spending up to date.
  • Budget creation and adjustment: Instruct your agent to set up new budgets, update existing categories, or reallocate funds between envelopes as your needs change.
  • Spending analysis and reporting: Have your agent analyze your expenses, highlight trends, or generate summaries to help you understand where your money goes.
  • Goal monitoring and progress updates: Ask your agent to track progress toward savings or debt payoff goals, and notify you of milestones or needed adjustments.
  • Account and balance synchronization: Enable your agent to pull up-to-date balances from multiple accounts, ensuring your budget always reflects the latest financial picture.

Supported Tools & Triggers

Tools
Create a new account in a budgetTool to create a new account in a budget.
Create Scheduled TransactionCreates a scheduled (recurring) transaction in a YNAB budget.
Delete Scheduled TransactionPermanently deletes a scheduled transaction from a YNAB budget.
Get Account by IDTool to retrieve a single account resource.
Get Budget By IDRetrieve a complete budget export by ID, including all accounts, categories, payees, and transactions.
Get Budget MonthTool to retrieve a specific budget month.
Get Budget SettingsTool to retrieve budget-level settings.
Get Category by IDRetrieve a single YNAB budget category by its ID.
Get Month Category By IDTool to retrieve a single category for a specific budget month.
Get Payee by IDTool to retrieve a single payee by its ID.
Get Scheduled Transaction by IDTool to retrieve a single scheduled transaction.
Get Transaction by IDTool to retrieve a single transaction by its ID.
Get Authorized UserTool to retrieve the authorized user's information.
List AccountsRetrieves all accounts for a specified YNAB budget.
List BudgetsRetrieves all budgets accessible to the authenticated YNAB user.
List CategoriesTool to list all category groups and their categories for a budget.
List Budget MonthsTool to list months for a budget with summary information.
List Payee LocationsRetrieves all GPS locations associated with payees in a budget.
List Payee Locations by PayeeRetrieves all GPS locations associated with a specific payee in a budget.
List payees in a budgetTool to list payees in a budget.
List Scheduled TransactionsList all scheduled (recurring) transactions for a YNAB budget.
List TransactionsTool to list transactions in a budget.
List Transactions by AccountTool to list transactions for a specific account.
List Transactions by CategoryTool to list transactions for a specific category (excludes pending).
List Transactions by PayeeTool to list transactions for a specific payee in a budget.
Update PayeeTool to update a payee.
Update Scheduled TransactionUpdate an existing scheduled transaction in YNAB.

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

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

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

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

Conclusion

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

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Ynab 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 Ynab MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Ynab MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Ynab MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Ynab MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Ynab MCP with Claude Cowork

Codex logo

Codex

Use Ynab MCP with Codex

OpenClaw logo

OpenClaw

Use Ynab MCP with OpenClaw

Hermes logo

Hermes

Use Ynab MCP with Hermes

CLI logo

CLI

Use Ynab MCP with CLI

LangChain logo

LangChain

Use Ynab MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Ynab MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Ynab MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Ynab MCP with LlamaIndex

CrewAI logo

CrewAI

Use Ynab MCP with CrewAI

FAQ

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

With a standalone Ynab MCP server, the agents and LLMs can only access a fixed set of Ynab tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Ynab 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 Ynab tools.

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

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