Amcards Automation
This skill automates Amcards operations using the Composio Amcards toolkit through Rube MCP.
Install
npx promptshop add amcards-automationDetails
What This Skill Does
This skill automates Amcards operations using the Composio Amcards toolkit through Rube MCP. It's designed for users who need to automate tasks related to sending physical cards and gifts via Amcards. The skill ensures tools are up-to-date and connections are active before executing workflows.
When to Use
- Automate sending personalized cards.
- Manage Amcards contacts and groups.
- Schedule card deliveries for specific dates.
- Track card delivery status.
- Integrate Amcards with CRM systems.
- Automate thank you card sending.
Key Features
- Uses Rube MCP to manage Amcards toolkit.
- Requires active Amcards connection.
- Discovers available tools via RUBE_SEARCH_TOOLS.
- Checks connection status before execution.
- Executes tools using RUBE_MULTI_EXECUTE_TOOL.
- Provides documentation link for the Amcards toolkit.
Manual Installation
Amcards Automation via Rube MCP
Automate Amcards operations through Composio's Amcards toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/amcards
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Amcards connection via RUBE_MANAGE_CONNECTIONS with toolkit amcards 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 amcards 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: "Amcards 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 Amcards task"}] session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["amcards"] 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 Amcards-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit amcards |
| 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 |
Amcards Automation via Rube MCP
Automate Amcards operations through Composio's Amcards toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/amcards