# Toolify

When you want to integrate an external tool, API, MCP server, or service into a project...

- Repository: https://github.com/coreyhaines31/makerskills (880 stars)
- Category: Testing
- License: MIT
- Last updated: 2026-10-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add coreyhaines31/makerskills --skill toolify -g -a claude-code -y`
Codex: `npx skills add coreyhaines31/makerskills --skill toolify -g -a codex -y`
Cursor: `npx skills add coreyhaines31/makerskills --skill toolify -g -a cursor -y`
Gemini CLI: `npx skills add coreyhaines31/makerskills --skill toolify -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add coreyhaines31/makerskills`

## Description

When you want to integrate an external tool, API, MCP server, or service into a project, the wizard walks you through auth, config, env vars, client wrapper code, example usage, and an optional smoke test. Scoped to Next.js and Rails projects. Interactive Q&A, starts with the tool name, asks structured questions until the integration is specified, then scaffolds files. Examples, Stripe, Kit, Sanity, Notion, Neon, Supabase, Resend, Postmark, Twilio, Anthropic, OpenAI, Vercel Blob, custom internal APIs. For MCP servers, also handles the .mcp.json wiring. Triggers on "/toolify," "integrate X," "add X to this project," "wire up X," "set up the X integration," "hook up X," "connect X," "add MCP for X." Part of the -ify trifecta (skillify / toolify / loopify). NOT for adding new SKILL.md files, that's skillify. NOT for cron/agent loops, that's loopify.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# /toolify, Wire up an integration or MCP server

Interactive wizard for adding an external tool / API / MCP into a project. Ends with working code + env vars set + a verification path.

## Scope

- **Primary stacks**: Next.js (App Router + TypeScript) and Rails. Reason: those are the two stacks the user actually ships in; supporting every stack bloats the wizard.
- **What toolify handles**: auth pattern (API key, OAuth, JWT, session cookie), env var setup, official SDK vs raw fetch, client wrapper location, example usage, webhook handling (if applicable), MCP `.mcp.json` wiring (if MCP server).
- **What toolify does NOT handle**: writing business logic on top of the integration (that's for the human). It scaffolds the *plumbing*, not the *feature*.

## Step 0, Get the tool name

Ask if not provided: *"Which tool are we integrating?"*

Detect category from name:

The rest: https://github.com/coreyhaines31/makerskills/blob/HEAD/skills/toolify/SKILL.md