PromptShop

Moneybird Automation

Automate accounting and invoicing workflows via Rube MCP.

Install

npx promptshop add moneybird-automation

Details

What This Skill Does

This skill automates interactions with the Moneybird platform using Composio's Moneybird toolkit through Rube MCP. It allows users to discover available tools, manage connections, and execute Moneybird operations. It's designed for finance professionals and business owners who want to automate their accounting tasks.

When to Use

  • Discover available Moneybird tools.
  • Check the status of the Moneybird connection.
  • Create invoices in Moneybird.
  • Manage contacts in Moneybird.
  • Process payments with Moneybird.
  • Automate Moneybird workflows.

Key Features

  • Automates Moneybird operations via Rube MCP.
  • Uses RUBE_SEARCH_TOOLS to discover available tools.
  • Manages connections using RUBE_MANAGE_CONNECTIONS.
  • Executes tools with RUBE_MULTI_EXECUTE_TOOL.
  • Requires active Moneybird connection.
  • Provides toolkit documentation for reference.

Manual Installation

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

Toolkit docs: composio.dev/toolkits/moneybird

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["moneybird"] 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 Moneybird-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit moneybird
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

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

Toolkit docs: composio.dev/toolkits/moneybird

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["moneybird"] 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 Moneybird-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit moneybird
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