
Api2pdf Automation
- 7 installs
- 71.8k repo stars
- Updated July 24, 2026
- composiohq/awesome-claude-skills
Automate Api2Pdf HTML-to-PDF and document generation from Claude by running the Api2Pdf toolkit through the Composio Rube MCP server.
About
Wraps the Api2Pdf toolkit behind Composio's Rube MCP so Claude can run PDF-generation operations via searched tool schemas. A developer uses it to let an agent create PDFs after connecting the toolkit.
- Requires Rube MCP connected and an ACTIVE Api2Pdf connection
- Always call RUBE_SEARCH_TOOLS first to get current tool schemas
Api2pdf Automation by the numbers
- 7 all-time installs (skills.sh)
- Ranked #1,587 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/composiohq/awesome-claude-skills --skill api2pdf-automationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 7 |
|---|---|
| repo stars | ★ 71.8k |
| Last updated | July 24, 2026 |
| Repository | composiohq/awesome-claude-skills ↗ |
What it does
Automate Api2Pdf HTML-to-PDF and document generation from Claude by running the Api2Pdf toolkit through the Composio Rube MCP server.
Files
Api2pdf Automation via Rube MCP
Automate Api2pdf operations through Composio's Api2pdf toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/api2pdf
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Api2pdf connection via
RUBE_MANAGE_CONNECTIONSwith toolkitapi2pdf - Always call
RUBE_SEARCH_TOOLSfirst 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.
1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds 2. Call RUBE_MANAGE_CONNECTIONS with toolkit api2pdf 3. If connection is not ACTIVE, follow the returned auth link to complete setup 4. Confirm connection status shows ACTIVE before running any workflows
Tool Discovery
Always discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Api2pdf 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 Api2pdf task"}]
session: {id: "existing_session_id"}Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["api2pdf"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Api2pdf-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit api2pdf |
| 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](https://composio.dev)