Do I need API keys to use Rube MCP?

No. You add the MCP server URL (for example, https://rube.app/mcp) and authenticate via built-in flows in Rube.

Why must I call RUBE_SEARCH_TOOLS before executing a tool?

Tool schemas change over time. RUBE_SEARCH_TOOLS fetches the latest tool slugs and arguments to ensure correct execution.

What if a tool slug changes or I get a validation error?

Re-fetch tool schemas with RUBE_SEARCH_TOOLS before retrying; ensure memory and session IDs are included in the request.

microsoft-tenant-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/microsoft-tenant-automation --openclaw

Files (1)

SKILL.md

3.0 KB

Microsoft Tenant Automation via Rube MCP

Automate Microsoft Tenant operations through Composio's Microsoft Tenant toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/microsoft_tenant

Prerequisites

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

Step 2: Check Connection

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

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Microsoft Tenant-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `microsoft_tenant`
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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/microsoft-tenant-automation/SKILL.md

View on GitHub

Overview

Automate Microsoft Tenant operations through Composio's Microsoft Tenant toolkit using Rube MCP. It enables repeatable tenant workflows by discovering current tool schemas first and then securely connecting to the tenant toolkit to execute the chosen tools. Always search tools first to get current schemas.

How This Skill Works

Discover available tools with RUBE_SEARCH_TOOLS using the Microsoft Tenant use_case; review the input schemas and recommended execution plans. Next, verify the connection with RUBE_MANAGE_CONNECTIONS for the microsoft_tenant toolkit and ensure the status is ACTIVE. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL with the required arguments and memory, reusing the session ID as needed.

When to Use It

Perform routine Microsoft Tenant operations (provisioning, auditing, or configuring) using the latest discovered tool schemas.
Automate configuration updates across multiple tenants in a repeatable workflow.
Validate and maintain an ACTIVE connection before running workflows.
Reuse a session across steps within a single automation to maintain context.
Execute bulk operations across tenants or tools via RUBE_REMOTE_WORKBENCH.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client config (no API keys needed) and confirm connectivity.
Step 2: Run RUBE_SEARCH_TOOLS with use_case: 'Microsoft Tenant operations' to fetch current tool schemas.
Step 3: Run RUBE_MANAGE_CONNECTIONS for toolkit 'microsoft_tenant', verify ACTIVE, then execute the tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding slugs.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even when empty.
Reuse session IDs within a workflow; generate new ones for new workflows.

Example Use Cases

Provision a new user in the Microsoft tenant by discovering the proper tool with RUBE_SEARCH_TOOLS and executing it with the required arguments.
Audit admin roles and update policies across tenants using the discovered tool.
Sync app registrations across tenants to keep configurations consistent.
Rotate credentials or update tenant settings via a sequenced tool execution.
Perform batch updates across tenants using RUBE_REMOTE_WORKBENCH to run multiple tools.

Frequently Asked Questions

Add this skill to your agents