Do I need an API key to use Ynab automation via Rube MCP?

No. The setup does not require API keys; you simply add the MCP endpoint (https://rube.app/mcp) and connect the Ynab toolkit.

What if tool slugs or input fields change?

Always search with RUBE_SEARCH_TOOLS first and use the slugs and input schemas provided by the results; do not hardcode.

How do I run multiple Ynab actions in one workflow?

Use RUBE_MULTI_EXECUTE_TOOL with a list of discovered tools, provide memory payload, and reuse a session_id across tools as needed.

ynab-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/ynab-automation --openclaw

Files (1)

SKILL.md

2.8 KB

Ynab Automation via Rube MCP

Automate Ynab operations through Composio's Ynab toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/ynab

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Ynab connection via RUBE_MANAGE_CONNECTIONS with toolkit ynab
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit ynab
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Ynab operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Ynab task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["ynab"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Ynab-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `ynab`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/ynab-automation/SKILL.mdView on GitHub

Overview

This skill automates Ynab operations through Composio's Ynab toolkit via Rube MCP. It standardizes tool discovery, connection checks, and execution with strict schema adherence. Always start by searching for current tool schemas to stay aligned with updates.

How This Skill Works

Discover available Ynab tools with RUBE_SEARCH_TOOLS, verify your Ynab connection using RUBE_MANAGE_CONNECTIONS, then execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL (including memory) and a session_id. You can also fetch full tool schemas via RUBE_GET_TOOL_SCHEMAS to ensure schema compliance.

When to Use It

You need to automate a recurring Ynab operation and want to discover the best-supported tool first.
You must connect to Ynab and confirm the connection is ACTIVE before running any workflow.
You want to execute a discovered Ynab tool with the exact input fields provided by the tool schema.
You intend to run multiple Ynab actions in a single workflow using a shared session.
You need to inspect and update tool schemas by fetching full schemas before implementation.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Run RUBE_SEARCH_TOOLS to discover available Ynab tools.
Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkit "ynab" and execute tools only after ACTIVE status.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas and avoid hardcoding slugs.
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE status before executing tools.
Use exact field names and types from the tool search results; avoid guessing.
Include the memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and handle pagination tokens as you fetch tools.

Example Use Cases

Discover available Ynab tools for your org, select a task slug from the search results, and execute it with proper arguments.
Establish a Ynab connection via RUBE_MANAGE_CONNECTIONS and confirm the status is ACTIVE before running workflows.
Execute a batch of Ynab actions in a single workflow using RUBE_MULTI_EXECUTE_TOOL with a shared session_id and memory payload.
Perform bulk operations using RUBE_REMOTE_WORKBENCH (run_composio_tool) for multiple Ynab tasks.
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to verify schema references and update automation scripts.

Frequently Asked Questions

Add this skill to your agents