What is Rube MCP and how does it relate to Hashnode automation?

Rube MCP is the framework used to run Composio tool-based workflows. For Hashnode automation, you connect to the Hashnode toolkit, discover current tool schemas, and execute tools through the specified Rube MCP commands.

Why must I always search tools first?

Tool schemas change over time. Searching first ensures you have current slugs and required fields, preventing broken workflows.

What if my Hashnode connection is not ACTIVE?

Complete the authentication flow returned by the tool to activate the connection. Workflows cannot run until the connection status shows ACTIVE.

hashnode-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Hashnode Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/hashnode

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["hashnode"]
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 Hashnode-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `hashnode`
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/hashnode-automation/SKILL.mdView on GitHub

Overview

Automate Hashnode operations using Composio's Hashnode toolkit through Rube MCP. The workflow always starts with discovering current tool schemas to avoid hardcoded slugs and arguments, then manages the Hashnode connection before executing tools.

How This Skill Works

Connect Rube MCP to Hashnode and verify RUBE_SEARCH_TOOLS returns current tool schemas. Discover available tools for your Hashnode task, check the connection status with RUBE_MANAGE_CONNECTIONS, then execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, including a memory payload. This ensures tools, schemas, and sessions stay synchronized throughout the workflow.

When to Use It

You need to automate a specific Hashnode operation from post creation to updates using discovered tools.
You must verify current tool schemas before running any workflow to avoid broken slugs or args.
You want to ensure the Hashnode toolkit connection is ACTIVE before execution.
You are performing a new Hashnode task and want to discover the right tool slugs first.
You plan to run a multi-tool workflow and must include the memory payload for each step.

Quick Start

Step 1: Add the MCP endpoint https://rube.app/mcp as an MCP server in your client; no API keys needed.
Step 2: Run RUBE_SEARCH_TOOLS to confirm tool schemas and select your Hashnode task.
Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkits: ["hashnode"] and then execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, including memory.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Do not hardcode tool slugs or arguments; rely on live search results.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and paginate properly when fetching results.

Example Use Cases

Publish a new Hashnode article by discovering the publish tool and executing it with required inputs.
Update an existing post's content by selecting the update tool from search results and supplying post_id and changes.
Fetch and summarize post analytics using a discovered analytics tool and present the results.
Bulk publish drafts by discovering a set of tools and running them in a controlled session.
Rotate profile fields or bio by using the toolkit’s update tools discovered via RUBE_SEARCH_TOOLS.

Frequently Asked Questions

Add this skill to your agents