$ loading_
Connect and automate Twelve Data workflows through Rube MCP tools.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "twelve-data-automation" skill from askskill: 1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/twelve-data-automation/SKILL.md 2. Save it as ~/.claude/skills/twelve-data-automation/SKILL.md 3. Reload skills and tell me it's ready
First call RUBE_SEARCH_TOOLS to find current tools for Twelve Data operations, including input schemas, recommended execution steps, and pitfalls, then summarize them in a list.
A list of available tools, parameter requirements, recommended flow, and known pitfalls.
Use RUBE_MANAGE_CONNECTIONS to check the twelve_data connection status; if it is not ACTIVE, explain the next step to complete authorization.
The connection status, plus the auth link or next setup step if it is not active.
First search for the right tool for my Twelve Data task, then reuse the same session, verify the connection, and finally call RUBE_MULTI_EXECUTE_TOOL with schema-compliant arguments and an empty memory object.
A completed Twelve Data tool execution following the recommended workflow.
When developers integrate Twelve Data into an automation flow, they can first discover current tool schemas, then verify the connection and execute the right tool to avoid failures from outdated parameters.
When analysts or researchers need to call Twelve Data through Rube MCP, they can follow a consistent sequence of tool discovery, connection verification, and execution.
For multi-step Twelve Data operations, users can reuse the same session and handle details like pagination, schemaRef, and the required memory parameter as noted in the docs.
The document explains how to automate Twelve Data operations through Composio's toolkit via Rube MCP. It covers prerequisites, connection setup, and a standard workflow: search tools first, verify the twelve_data connection, then execute with schema-compliant arguments. It also highlights common pitfalls such as not hardcoding schemas, always including the memory field, reusing session IDs within a workflow, and checking pagination or full schemas when needed.
Automate Twelve Data operations through Composio's Twelve Data toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/twelve_data
RUBE_MANAGE_CONNECTIONS with toolkit twelve_dataRUBE_SEARCH_TOOLS first to get current tool schemasGet 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.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit twelve_dataAlways 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.
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Twelve Data task"}]
session: {id: "existing_session_id"}
RUBE_MANAGE_CONNECTIONS
toolkits: ["twelve_data"]
session_id: "your_session_id"
RUBE_MULTI_EXECUTE_TOOL
tools: [{
tool_slug: "TOOL_SLUG_FROM_SEARCH",
arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
RUBE_SEARCH_TOOLSRUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing toolsmemory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Twelve Data-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit twelve_data |
| 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
It automates Twelve Data operations through Composio's Twelve Data toolkit via Rube MCP. The docs emphasize searching tools first, then checking the connection before execution.
You need Rube MCP connected and RUBE_SEARCH_TOOLS available. You also need an active twelve_data connection set up through RUBE_MANAGE_CONNECTIONS.
Because tool schemas may change, the docs explicitly advise against hardcoding tool slugs or arguments. You should call RUBE_SEARCH_TOOLS first and execute based on the current schema.
Automate Crustdata workflows via Rube MCP with schema-first tool discovery.
Automate Cults queries and management tasks after checking current tool schemas.
Automate Fillout form tasks and workflows through Rube MCP.
Automate customer engagement, segmentation, messaging analytics, and newsletter tracking in Customer.io.
Automate CustomGPT tasks and workflow integrations through Rube MCP.
Automate Crowdin localization and project workflows through Rube MCP tools.
Automate DataRobot tasks through Rube MCP for faster model and data workflows.
Automate Autom workflows via Rube MCP while checking current tool schemas first.
Automate Strava tasks and data workflows through Rube MCP tools.
Automate Composio tasks via Rube MCP with tool schema lookup first.
Automate Baserow table tasks and data workflows through Rube MCP.
Automate Code Interpreter workflows for coding, analysis, and repeatable task execution.