Finmei Automation
This skill automates Finmei operations using the Composio Finmei toolkit via Rube MCP.
Install
npx promptshop add finmei-automationDetails
What This Skill Does
- This skill automates Finmei operations using the Composio Finmei toolkit via Rube MCP.
- It allows users to streamline Finmei tasks by discovering and executing tools through a standardized workflow. This skill is designed for users familiar with Finmei and Rube MCP.
When to Use
Automate invoice processingManage financial transactionsGenerate financial reportsCheck Finmei connection statusDiscover available Finmei toolsExecute specific Finmei tasks
Key Features
Uses Rube MCP to connect to FinmeiRequires active Finmei connectionDiscovers available tools via RUBE_SEARCH_TOOLSChecks connection status with RUBE_MANAGE_CONNECTIONSExecutes tools with RUBE_MULTI_EXECUTE_TOOLProvides a standardized workflow for Finmei automation
Manual Installation
Manual installationView Full Skill ContentThe complete markdown content that gets installedFinmei Automation via Rube MCP
Automate Finmei operations through Composio's Finmei toolkit via Rube MCP.
- Toolkit docs: composio.
- dev/toolkits/finmei.
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Finmei connection via RUBE_MANAGE_CONNECTIONS with toolkit finmei 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 finmei 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: "Finmei 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 Finmei task"}] session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["finmei"] 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 Finmei-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit finmei |
| 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 |