Finage Automation

What This Skill Does

• This skill automates Finage operations using the Composio Finage toolkit via Rube MCP.
• It allows users to retrieve financial data, such as stock prices and market information, programmatically. It is designed for developers and data analysts who need to integrate Finage data into automated processes.

When to Use

• Retrieve real-time stock quotes.
• Fetch historical financial data. Monitor market trends automatically. Integrate financial data into reports. Build automated trading strategies. Analyze financial data programmatically.

Key Features

• Uses Rube MCP for tool discovery and execution.
• Requires an active Finage connection. Employs RUBE_SEARCH_TOOLS to find available tools. Executes tools via RUBE_MULTI_EXECUTE_TOOL. Supports session management for workflows. Provides documentation for the Finage toolkit.

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedFinage Automation via Rube MCP

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

• Toolkit docs: composio.
• dev/toolkits/finage.

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Finage connection via RUBE_MANAGE_CONNECTIONS with toolkit finage 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 finage 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: "Finage 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 Finage task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["finage"] 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