Currents API Automation via Rube MCP

SkillSearch

This skill connects your AI to the Currents API so it can handle tasks there on your behalf. Once added, your AI can search Currents and post activity for you through connected tools.

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

After adding it, ask your AI to search the available tools first so it works from their current setup. Then give it a task, like finding something in Currents or posting an activity.

Then ask your AI: use the Currents API Automation via Rube MCP skill

What your AI can do with it

  • Search Currents for what you need
  • Post activity to Currents for you
  • Automate routine Currents tasks end to end
  • Check the current setup of available tools before acting

What this skill tells your AI

The instructions your AI receives, as published by composio-community/awesome-codex-skills in composio-skills/currents-api-automation/SKILL.md and read by ahel’s review.

Automate Currents API operations through Composio's Currents API toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/currents_api

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Currents API connection via RUBE_MANAGE_CONNECTIONS with toolkit currents_api
  • 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.

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

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Currents API 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 Currents API task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Currents API-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit currents_api
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Powered by Composio

Signals

GitHub stars
17k
Forks
2k
Last commit
Jul 2026
Advanced
Item type
skill
Key
currents-api-automation
Source
github.com/composio-community/awesome-codex-skills