Twelve Data Automation

What This Skill Does

• This skill automates Twelve Data operations through Composio's Twelve Data toolkit via Rube MCP.
• It allows users to access real-time and historical financial data for analysis and integration into applications. This is beneficial for financial analysts, traders, and developers building financial applications.

When to Use

• Fetch real-time stock prices for a portfolio.
• Get historical data for a specific stock. Calculate moving averages and other indicators. Monitor market trends and identify opportunities. Integrate financial data into trading algorithms. Automate financial reporting processes.

Key Features

• Automates Twelve Data tasks via Rube MCP.
• Uses Composio's Twelve Data toolkit. Requires an active Twelve Data connection. Discovers available tools using RUBE_SEARCH_TOOLS. Checks connection status with RUBE_MANAGE_CONNECTIONS. Executes tools with RUBE_MULTI_EXECUTE_TOOL.

Manual Installation

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

Automate Twelve Data operations through Composio's Twelve Data toolkit via Rube MCP.

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

Prerequisites

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

Step 2: Check Connection

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