# How to integrate Ynab MCP with OpenAI Agents SDK

```json
{
  "title": "How to integrate Ynab MCP with OpenAI Agents SDK",
  "toolkit": "Ynab",
  "toolkit_slug": "ynab",
  "framework": "OpenAI Agents SDK",
  "framework_slug": "open-ai-agents-sdk",
  "url": "https://composio.dev/toolkits/ynab/framework/open-ai-agents-sdk",
  "markdown_url": "https://composio.dev/toolkits/ynab/framework/open-ai-agents-sdk.md",
  "updated_at": "2026-05-12T10:30:56.806Z"
}
```

## Introduction

This guide walks you through connecting Ynab to the OpenAI Agents SDK 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 OpenAI Agents SDK 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

- [Claude Agent SDK](https://composio.dev/toolkits/ynab/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/ynab/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/ynab/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/ynab/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/ynab/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/ynab/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/ynab/framework/cli)
- [Google ADK](https://composio.dev/toolkits/ynab/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/ynab/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/ynab/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/ynab/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/ynab/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/ynab/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Install the necessary dependencies
- Initialize Composio and create a Tool Router session for Ynab
- Configure an AI agent that can use Ynab as a tool
- Run a live chat session where you can ask the agent to perform Ynab operations

## What is OpenAI Agents SDK?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.
Key features include:
- Hosted MCP Tools: Connect to external services through hosted MCP endpoints
- SQLite Sessions: Persist conversation history across interactions
- Simple API: Clean interface with Agent, Runner, and tool configuration
- Streaming Support: Real-time response streaming for interactive applications

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

| Tool slug | Name | Description |
|---|---|---|
| `YNAB_CREATE_ACCOUNT` | Create a new account in a budget | Tool to create a new account in a budget. Use when you need to add a manual (non-linked) account to a specific budget. |
| `YNAB_CREATE_SCHEDULED_TRANSACTION` | Create Scheduled Transaction | Creates a scheduled (recurring) transaction in a YNAB budget. Use this to set up bills, recurring expenses, or income that repeats on a schedule. Requires an account_id (from YNAB_LIST_ACCOUNTS), a date, frequency, and amount in milliunits. |
| `YNAB_DELETE_SCHEDULED_TRANSACTION` | Delete Scheduled Transaction | Permanently deletes a scheduled transaction from a YNAB budget. Use this when a recurring transaction is no longer needed. This action cannot be undone. Obtain the scheduled_transaction_id from list_scheduled_transactions or get_scheduled_transaction_by_id before calling this. |
| `YNAB_GET_ACCOUNT_BY_ID` | Get Account by ID | Tool to retrieve a single account resource. Use when you need details of a specific account by its ID after determining the budget. |
| `YNAB_GET_BUDGET_BY_ID` | Get Budget By ID | Retrieve a complete budget export by ID, including all accounts, categories, payees, and transactions. Use this tool when you need comprehensive budget data. The response includes: - Budget metadata (name, date/currency formats) - All accounts with balances - Category groups and categories with budgeted amounts and balances - All payees - All transactions and scheduled transactions (optional, may be large) For incremental syncing, use last_knowledge_of_server to only fetch changes since your last request. Note: Currency amounts are in 'milliunits' format (divide by 1000 for standard units). |
| `YNAB_GET_BUDGET_MONTH` | Get Budget Month | Tool to retrieve a specific budget month. Use when you need detailed summary and category budgets for a given month after confirming the budget ID. Monetary amounts are returned in milliunits (divide by 1000 for standard currency). Response includes high-level aggregates and a nested category array within the month payload for per-category budget analysis. |
| `YNAB_GET_BUDGET_SETTINGS` | Get Budget Settings | Tool to retrieve budget-level settings. Use when you need to fetch currency and date formatting preferences for a specific budget. |
| `YNAB_GET_CATEGORY_BY_ID` | Get Category by ID | Retrieve a single YNAB budget category by its ID. Use this to get detailed category information including budgeted amounts, activity, balance, and goal settings. Amounts are returned for the current budget month (UTC). Requires both budget_id and category_id - use 'last-used' or 'default' for budget_id if you don't have a specific budget ID. |
| `YNAB_GET_MONTH_CATEGORY_BY_ID` | Get Month Category By ID | Tool to retrieve a single category for a specific budget month. Use after selecting the budget and month when you need month-specific category details. |
| `YNAB_GET_PAYEE_BY_ID` | Get Payee by ID | Tool to retrieve a single payee by its ID. Use when you need full details of a payee after confirming the budget and payee selection. |
| `YNAB_GET_SCHEDULED_TRANSACTION_BY_ID` | Get Scheduled Transaction by ID | Tool to retrieve a single scheduled transaction. Use when you need details of a specific scheduled transaction by its ID after confirming the budget. |
| `YNAB_GET_TRANSACTION_BY_ID` | Get Transaction by ID | Tool to retrieve a single transaction by its ID. Use when you need detailed information for a specific transaction after confirming the budget. |
| `YNAB_GET_USER` | Get Authorized User | Tool to retrieve the authorized user's information. Use after authentication to get current user details. |
| `YNAB_LIST_ACCOUNTS` | List Accounts | Retrieves all accounts for a specified YNAB budget. Use this tool to: - Get a complete list of accounts (checking, savings, credit cards, loans, etc.) in a budget - Retrieve account IDs for use with other YNAB account-related operations - Monitor account balances (current, cleared, and uncleared) - Perform efficient delta syncing by passing last_knowledge_of_server Returns account details including balances in milliunits (1000 milliunits = 1 currency unit). For example, a balance of 150000 milliunits equals $150.00. Note: Use 'default' or 'last-used' as budget_id for convenience, or obtain specific budget UUIDs from the List Budgets endpoint. |
| `YNAB_LIST_BUDGETS` | List Budgets | Retrieves all budgets accessible to the authenticated YNAB user. Use this tool to: - Get a list of all budgets in the user's YNAB account - Retrieve budget IDs for use with other YNAB operations - Optionally include account details for each budget Returns budget summaries including name, last modification time, date range, and formatting preferences. Budget IDs from this response are required for most other YNAB API operations. |
| `YNAB_LIST_CATEGORIES` | List Categories | Tool to list all category groups and their categories for a budget. Use when you need the full set of budget categories or only those changed since last sync. Category names may include emojis or near-identical labels; always use category_id from the response in downstream requests. |
| `YNAB_LIST_MONTHS` | List Budget Months | Tool to list months for a budget with summary information. Use when you need an overview of all months or only changed months since a given knowledge value (delta requests). |
| `YNAB_LIST_PAYEE_LOCATIONS` | List Payee Locations | Retrieves all GPS locations associated with payees in a budget. Payee locations are recorded when transactions are saved using the YNAB mobile apps, storing GPS coordinates to help pre-populate nearby payees. Use this tool when you need to find all recorded locations for payees in a budget. Note: Not all payees will have locations recorded. |
| `YNAB_LIST_PAYEE_LOCATIONS_BY_PAYEE` | List Payee Locations by Payee | Retrieves all GPS locations associated with a specific payee in a budget. Payee locations are recorded when transactions are saved using the YNAB mobile apps, storing GPS coordinates to help pre-populate nearby payees. Use this tool when you need to find where a payee's transactions typically occur. Note: Not all payees will have locations recorded. |
| `YNAB_LIST_PAYEES` | List payees in a budget | Tool to list payees in a budget. Use when you need all payees or only those changed since a known server knowledge value. |
| `YNAB_LIST_SCHEDULED_TRANSACTIONS` | List Scheduled Transactions | List all scheduled (recurring) transactions for a YNAB budget. Returns future-dated transactions that repeat on a schedule (e.g., rent, subscriptions, paychecks). Supports delta sync to fetch only changes since a previous request using the server_knowledge value. |
| `YNAB_LIST_TRANSACTIONS` | List Transactions | Tool to list transactions in a budget. Use when you need all or delta-filtered transactions after confirming the budget. Omitting all filters returns the full transaction history, which may produce large payloads; prefer since_date, type, or last_knowledge_of_server to scope results. |
| `YNAB_LIST_TRANSACTIONS_BY_ACCOUNT` | List Transactions by Account | Tool to list transactions for a specific account. Use when you need all or delta-filtered transactions for a given account after confirming the budget and account ID. |
| `YNAB_LIST_TRANSACTIONS_BY_CATEGORY` | List Transactions by Category | Tool to list transactions for a specific category (excludes pending). Use when you need completed transactions for a given category after obtaining budget_id and category_id. Response includes deleted transactions; filter client-side using the deleted boolean field. |
| `YNAB_LIST_TRANSACTIONS_BY_PAYEE` | List Transactions by Payee | Tool to list transactions for a specific payee in a budget. Use when you need to fetch all non-pending transactions for a payee after confirming budget and payee IDs. |
| `YNAB_UPDATE_PAYEE` | Update Payee | Tool to update a payee. Use when you need to rename an existing payee. |
| `YNAB_UPDATE_SCHEDULED_TRANSACTION` | Update Scheduled Transaction | Update an existing scheduled transaction in YNAB. Allows modifying the date, frequency, amount, payee, category, memo, or account of a scheduled transaction. Use YNAB_LIST_SCHEDULED_TRANSACTIONS first to get the scheduled_transaction_id. Amounts should be in milliunits (negative for expenses, positive for income). |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Ynab MCP server is an implementation of the Model Context Protocol that connects your AI agent to Ynab. It provides structured and secure access so your agent can perform Ynab operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Composio API Key and OpenAI API Key
- Primary know-how of OpenAI Agents SDK
- A live Ynab project
- Some knowledge of Python or Typescript

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings and copy your API key.

### 2. Install dependencies

Install the Composio SDK and the OpenAI Agents SDK.
```python
pip install composio_openai_agents openai-agents python-dotenv
```

```typescript
npm install @composio/openai-agents @openai/agents dotenv
```

### 3. Set up environment variables

Create a .env file and add your OpenAI and Composio API keys.
```bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com
```

### 4. Import dependencies

What's happening:
- You're importing all necessary libraries.
- The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Ynab.
```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';
```

### 5. Set up the Composio instance

No description provided.
```python
load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
```

```typescript
dotenv.config();

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});
```

### 6. Create a Tool Router session

What is happening:
- You give the Tool Router the user id and the toolkits you want available. Here, it is only ynab.
- The router checks the user's Ynab connection and prepares the MCP endpoint.
- The returned session.mcp.url is the MCP URL that your agent will use to access Ynab.
- This approach keeps things lightweight and lets the agent request Ynab tools only when needed during the conversation.
```python
# Create a Ynab Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["ynab"]
)

mcp_url = session.mcp.url
```

```typescript
// Create Tool Router session for Ynab
const session = await composio.create(userId as string, {
  toolkits: ['ynab'],
});
const mcpUrl = session.mcp.url;
```

### 7. Configure the agent

No description provided.
```python
# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Ynab. "
        "Help users perform Ynab operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)
```

```typescript
// Configure agent with MCP tool
const agent = new Agent({
  name: 'Assistant',
  model: 'gpt-5',
  instructions:
    'You are a helpful assistant that can access Ynab. Help users perform Ynab operations through natural language.',
  tools: [
    hostedMcpTool({
      serverLabel: 'tool_router',
      serverUrl: mcpUrl,
      headers: { 'x-api-key': composioApiKey },
      requireApproval: 'never',
    }),
  ],
});
```

### 8. Start chat loop and handle conversation

No description provided.
```python
print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
// Keep conversation state across turns
const conversationSession = new OpenAIConversationsSession();

// Simple CLI
const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: 'You: ',
});

console.log('\nComposio Tool Router session created.');
console.log('\nChat started. Type your requests below.');
console.log("Commands: 'exit', 'quit', or 'q' to end\n");

try {
  const first = await run(agent, 'What can you help me with?', { session: conversationSession });
  console.log(`Assistant: ${first.finalOutput}\n`);
} catch (e) {
  console.error('Error:', e instanceof Error ? e.message : e, '\n');
}

rl.prompt();

rl.on('line', async (userInput) => {
  const text = userInput.trim();

  if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
    console.log('Goodbye!');
    rl.close();
    process.exit(0);
  }

  if (!text) {
    rl.prompt();
    return;
  }

  try {
    const result = await run(agent, text, { session: conversationSession });
    console.log(`\nAssistant: ${result.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();
});

rl.on('close', () => {
  console.log('\n👋 Session ended.');
  process.exit(0);
});
```

## Complete Code

```python
import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["ynab"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Ynab. "
        "Help users perform Ynab operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
```

```typescript
import 'dotenv/config';
import { Composio } from '@composio/core';
import { OpenAIAgentsProvider } from '@composio/openai-agents';
import { Agent, hostedMcpTool, run, OpenAIConversationsSession } from '@openai/agents';
import * as readline from 'readline';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.USER_ID;

if (!composioApiKey) {
  throw new Error('COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key');
}
if (!userId) {
  throw new Error('USER_ID is not set');
}

// Initialize Composio
const composio = new Composio({
  apiKey: composioApiKey,
  provider: new OpenAIAgentsProvider(),
});

async function main() {
  // Create Tool Router session
  const session = await composio.create(userId as string, {
    toolkits: ['ynab'],
  });
  const mcpUrl = session.mcp.url;

  // Configure agent with MCP tool
  const agent = new Agent({
    name: 'Assistant',
    model: 'gpt-5',
    instructions:
      'You are a helpful assistant that can access Ynab. Help users perform Ynab operations through natural language.',
    tools: [
      hostedMcpTool({
        serverLabel: 'tool_router',
        serverUrl: mcpUrl,
        headers: { 'x-api-key': composioApiKey },
        requireApproval: 'never',
      }),
    ],
  });

  // Keep conversation state across turns
  const conversationSession = new OpenAIConversationsSession();

  // Simple CLI
  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: ',
  });

  console.log('\nComposio Tool Router session created.');
  console.log('\nChat started. Type your requests below.');
  console.log("Commands: 'exit', 'quit', or 'q' to end\n");

  try {
    const first = await run(agent, 'What can you help me with?', { session: conversationSession });
    console.log(`Assistant: ${first.finalOutput}\n`);
  } catch (e) {
    console.error('Error:', e instanceof Error ? e.message : e, '\n');
  }

  rl.prompt();

  rl.on('line', async (userInput) => {
    const text = userInput.trim();

    if (['exit', 'quit', 'q'].includes(text.toLowerCase())) {
      console.log('Goodbye!');
      rl.close();
      process.exit(0);
    }

    if (!text) {
      rl.prompt();
      return;
    }

    try {
      const result = await run(agent, text, { session: conversationSession });
      console.log(`\nAssistant: ${result.finalOutput}\n`);
    } catch (e) {
      console.error('Error:', e instanceof Error ? e.message : e, '\n');
    }

    rl.prompt();
  });

  rl.on('close', () => {
    console.log('\nSession ended.');
    process.exit(0);
  });
}

main().catch((err) => {
  console.error('Fatal error:', err);
  process.exit(1);
});
```

## Conclusion

This was a starter code for integrating Ynab MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Ynab.
Key features:
- Hosted MCP tool integration through Composio's Tool Router
- SQLite session persistence for conversation history
- Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

## How to build Ynab MCP Agent with another framework

- [Claude Agent SDK](https://composio.dev/toolkits/ynab/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/ynab/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/ynab/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/ynab/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/ynab/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/ynab/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/ynab/framework/cli)
- [Google ADK](https://composio.dev/toolkits/ynab/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/ynab/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/ynab/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/ynab/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/ynab/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/ynab/framework/crew-ai)

## Related Toolkits

- [Stripe](https://composio.dev/toolkits/stripe) - Stripe is a global online payments platform offering APIs for managing payments, customers, and subscriptions. Trusted by businesses for secure, efficient, and scalable payment processing worldwide.
- [Alpha vantage](https://composio.dev/toolkits/alpha_vantage) - Alpha Vantage is a financial data platform offering real-time and historical stock market APIs. Get instant, reliable access to equities, forex, and technical analysis data for smarter trading decisions.
- [Altoviz](https://composio.dev/toolkits/altoviz) - Altoviz is a cloud-based billing and invoicing platform for businesses. It streamlines online payments, expense tracking, and customizable invoice management.
- [Benzinga](https://composio.dev/toolkits/benzinga) - Benzinga provides real-time financial news and data APIs for market coverage. It helps you track breaking news and actionable market insights instantly.
- [Brex](https://composio.dev/toolkits/brex) - Brex provides corporate credit cards and spend management tailored for startups and tech businesses. It helps optimize company cash flow, streamline accounting, and accelerate business growth.
- [Chaser](https://composio.dev/toolkits/chaser) - Chaser is accounts receivable automation software that sends invoice reminders and helps businesses get paid faster. It streamlines the collections process to save time and improve cash flow.
- [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time.
- [Coinbase](https://composio.dev/toolkits/coinbase) - Coinbase is a platform for buying, selling, and storing cryptocurrency. It makes exchanging and managing crypto simple and secure for everyone.
- [Coinranking](https://composio.dev/toolkits/coinranking) - Coinranking is a comprehensive cryptocurrency market data platform offering access to real-time coin prices, market caps, and historical data. Get accurate, up-to-date stats for thousands of digital assets in one place.
- [Coupa](https://composio.dev/toolkits/coupa) - Coupa is a business spend management platform for procurement, invoicing, and expenses. It helps organizations streamline purchasing, control costs, and gain complete visibility over financial operations.
- [CurrencyScoop](https://composio.dev/toolkits/currencyscoop) - CurrencyScoop is a developer-friendly API for real-time and historical currency exchange rates. Easily access fiat and crypto data for smart, up-to-date financial applications.
- [Daffy](https://composio.dev/toolkits/daffy) - Daffy is a modern charitable giving platform with a donor-advised fund. Easily set aside funds, grow them tax-free, and donate to over 1.7 million U.S. charities.
- [Eagle doc](https://composio.dev/toolkits/eagle_doc) - Eagle doc is an AI-powered OCR API for invoices and receipts. It delivers fast, reliable, and accurate document data extraction for seamless automation.
- [Elorus](https://composio.dev/toolkits/elorus) - Elorus is an online invoicing and time-tracking software for freelancers and small businesses. Easily manage finances, bill clients, and track work in one place.
- [Eodhd apis](https://composio.dev/toolkits/eodhd_apis) - Eodhd apis delivers comprehensive financial data, including live and historical stock prices, via robust APIs. Easily access reliable, up-to-date market insights to power your apps, dashboards, and analytics.
- [Fidel api](https://composio.dev/toolkits/fidel_api) - Fidel api is a secure platform for linking payment cards to web and mobile apps. It enables real-time card transaction monitoring and event-based automation for businesses.
- [Finage](https://composio.dev/toolkits/finage) - Finage is a secure API platform delivering real-time and historical financial data for stocks, forex, crypto, indices, and commodities. It empowers developers and businesses to access, analyze, and act on market data instantly.
- [Finmei](https://composio.dev/toolkits/finmei) - Finmei is an invoicing tool that simplifies billing, invoice management, and expense tracking. Ideal for automating and organizing your business finances in one place.
- [Fixer](https://composio.dev/toolkits/fixer) - Fixer is a currency data API offering real-time and historical exchange rates for 170 currencies. Instantly access accurate, up-to-date forex data for your applications and workflows.
- [Fixer io](https://composio.dev/toolkits/fixer_io) - Fixer.io is a lightweight API for real-time and historical foreign exchange rates. It makes global currency conversion fast, accurate, and hassle-free.

## Frequently Asked Questions

### 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 OpenAI Agents SDK?

Yes, you can. OpenAI Agents SDK 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.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)