Altoviz Automation via Rube MCP

SkillSearch

This skill lets an AI automate business tasks in Altoviz. Once added, your AI can figure out the right tools for each job and run them, checking the latest tool details before it acts.

Available today. Use it from your connected AI after setup.

Add the skill, then tell your AI which Altoviz task you want done. It will search for the right tools first to make sure it works with the current setup.

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

What your AI can do with it

  • Discover the right tools for each Altoviz business task
  • Run those tools automatically to complete the work
  • Check current tool details first so tasks use up-to-date steps
  • Automate routine Altoviz work from start to finish

What this skill tells your AI

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

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

Toolkit docs: composio.dev/toolkits/altoviz

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["altoviz"]
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 Altoviz-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit altoviz
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
16k
Forks
2k
Last commit
Jul 2026

Others that do the same job

Advanced
Catalog kind
skill
Gateway key
altoviz-automation
Source
github.com/composio-community/awesome-codex-skills