"React Hook Form" matching MCP tools:

• scaffold_providerA

  UploadkitA

  Return a ready-to-paste snippet that wraps the Next.js root layout with `<UploadKitProvider>` so React components can talk to the upload route handler. When to use: right after scaffold_route_handler, to complete the wiring. The snippet goes in `app/layout.tsx`. Without the provider, UploadKit React components throw at runtime. Returns: a plain-text string containing a short explanatory note followed by a fenced tsx code block. Takes no parameters — the endpoint path is always `/api/uploadkit` since that is what scaffold_route_handler produces. Read-only, deterministic, idempotent.

  ConnectorNo auth

• migrate_to_propelauth_frontendA

  PropelAuth Integration MCP ServerA

  Returns instructions for migrating to PropelAuth in a frontend framework such as React, JavaScript, TypeScript, or when using Next.js for just the frontend (e.g. client-side rendered). Guidance includes migrating from several auth providers, such as Clerk or Auth0. Each guidance will include documentation from the auth provider and PropelAuth. It is important to follow the instructions carefully to ensure a successful integration. Make sure to use the 'Installation' guidance first. It is important to call every guidance to ensure a successful integration. Do not update a component/hook/etc from the auth provider until you receive guidance about that component/hook/etc. CRITICAL: If the current implementation uses a traditional OAuth/OIDC flow (e.g., via express-openid-connect, passport-auth0, or similar backend-managed session libraries), you MUST select 'OAuth' as the framework, regardless of the frontend library (React/Vue/etc.). Only select 'React' or 'Javascript' if the current implementation uses a frontend-only SDK (like @auth0/auth0-react) or if using fullstack Next.js.

  ConnectorNo auth

• migrate_to_propelauth_fullstackA

  PropelAuth Integration MCP ServerA

  Returns instructions for migrating from an existing auth provider to PropelAuth in a fullstack Nextjs App Router or Nextjs Pages Router application. If the user is using Next.js as just a frontend (e.g. client-side rendered with or without server routes), use the migrate_to_propelauth_frontend tool. Guidance includes installation and configuration, retrieving user or org information, logging users out, redirecting users to login, and more. Make sure to use the 'Installation' guidance first. It is important to call every guidance to ensure a successful integration. Do not update a component/hook/etc from the auth provider until you receive guidance about that component/hook/etc

  ConnectorNo auth

• write_filesA

  KleapA

  Write WHOLE files DIRECTLY — YOUR model generates the code, Kleap stores, builds and deploys it as-is. To change something in a file that ALREADY EXISTS, use edit_files instead (read_files → edit_files): it replaces just the lines you name, while write_files makes you retype the entire file and silently drops whatever you leave out — on a 30KB shared layout that is how headers and footers get wiped. No Kleap-AI step, so what ships is byte-for-byte what you wrote — the right choice when a phrase, a URL or a schema must be exact. Publishing still audits the result (see publish_app). Best for scaffolding exact pages/components — e.g. programmatic-SEO routes. Astro paths (src/pages/*.astro, src/data/*.json, src/components/*.astro, public/*). Overwrites by path. NPM PACKAGES: do not write package.json (the build replaces it) — the build installs whatever your code IMPORTS, so `import { jsPDF } from "jspdf";` is all it takes. Supported on import: @tiptap/*, jspdf, pdf-lib, html2canvas, papaparse, file-saver, jszip, @ffmpeg/*, howler, wavesurfer.js, browser-image-compression, react-dropzone, recharts, chart.js, d3, @tanstack/*, react-hook-form, three, @react-three/*, leaflet, maplibre-gl, gsap, framer-motion, zustand, date-fns, react-markdown, axios, socket.io-client, radix-ui/*, next-themes, lucide-react, @tabler/*, openai, @ai-sdk/*; anything else is refused at build with a message naming it. A client-side router is never the answer — a route is a FILE (src/pages/about.astro → /about). IMAGES AND BINARIES: set encoding:"base64" on the file and send the bytes — that is how you put a logo, a photo, an OG image, a favicon or a font on the site (png/jpg/webp/svg/ico/mp4/woff2/pdf, 512KB max each decoded). Without it you can only write text, and a site with no images looks unfinished. To ADD an image from a text prompt WITHOUT sending any bytes (a real photo's base64 is too big to emit reliably), use generate_image — Kleap generates it and stores it for you. To REMOVE a page or asset, use delete_files — overwriting it with empty content leaves a URL that answers 200 with nothing, which is worse than a 404. DATA & ACCOUNTS: write_files only STORES files — it cannot provision the Kleap Database, so DB or auth code pushed here has no backend and silently does nothing. Stand the feature up with modify_app first, then edit those pages here. After writing, call publish_app to build & go live.

  Connector

  Destructive

  OAuth

• write_filesA

  KleapA

  Write WHOLE files DIRECTLY — YOUR model generates the code, Kleap stores, builds and deploys it as-is. To change something in a file that ALREADY EXISTS, use edit_files instead (read_files → edit_files): it replaces just the lines you name, while write_files makes you retype the entire file and silently drops whatever you leave out — on a 30KB shared layout that is how headers and footers get wiped. No Kleap-AI step, so what ships is byte-for-byte what you wrote — the right choice when a phrase, a URL or a schema must be exact. Publishing still audits the result (see publish_app). Best for scaffolding exact pages/components — e.g. programmatic-SEO routes. Astro paths (src/pages/*.astro, src/data/*.json, src/components/*.astro, public/*). Overwrites by path. NPM PACKAGES: do not write package.json (the build replaces it) — the build installs whatever your code IMPORTS, so `import { jsPDF } from "jspdf";` is all it takes. Supported on import: @tiptap/*, jspdf, pdf-lib, html2canvas, papaparse, file-saver, jszip, @ffmpeg/*, howler, wavesurfer.js, browser-image-compression, react-dropzone, recharts, chart.js, d3, @tanstack/*, react-hook-form, three, @react-three/*, leaflet, maplibre-gl, gsap, framer-motion, zustand, date-fns, react-markdown, axios, socket.io-client, radix-ui/*, next-themes, lucide-react, @tabler/*, openai, @ai-sdk/*; anything else is refused at build with a message naming it. A client-side router is never the answer — a route is a FILE (src/pages/about.astro → /about). IMAGES AND BINARIES: set encoding:"base64" on the file and send the bytes — that is how you put a logo, a photo, an OG image, a favicon or a font on the site (png/jpg/webp/svg/ico/mp4/woff2/pdf, 512KB max each decoded). Without it you can only write text, and a site with no images looks unfinished. To ADD an image from a text prompt WITHOUT sending any bytes (a real photo's base64 is too big to emit reliably), use generate_image — Kleap generates it and stores it for you. To REMOVE a page or asset, use delete_files — overwriting it with empty content leaves a URL that answers 200 with nothing, which is worse than a 404. DATA & ACCOUNTS: write_files only STORES files — it cannot provision the Kleap Database, so DB or auth code pushed here has no backend and silently does nothing. Stand the feature up with modify_app first, then edit those pages here. After writing, call publish_app to build & go live.

  Connector

  Destructive

  No auth

• create_webhook_endpointA

  Reach MCPA

  Register a URL to be called when something happens on LinkedIn, so an agent or an n8n/Make workflow can react instead of polling. Returns the signing secret ONCE; deliveries carry 'Reach-Signature: t=<unix>,v1=<hex HMAC-SHA256(secret, t + '.' + body)>'. Events: message.received, connection.new, account.status_changed, quota.threshold_reached, quota.reached, or '*' for all. Omit account_ids to subscribe for every account of the user. https only. Use when the user wants to react to a reply, a new connection, a quota alert or a job event from n8n, Make or their own code; needs an https URL they control. Not for the model to call itself.

  ConnectorAPI key

• pathrule_write_memoryA

  PathruleA

  Create a new memory at a workspace path. Missing nodes auto-create. Blocks duplicate titles unless allow_duplicate is set. Cloud-only: never writes to the user's local filesystem. For automatic CLAUDE.md/AGENTS.md sync and on-disk hook injection alongside the write, install Pathrule Studio or CLI.

  ConnectorNo auth

• get_notificationsA

  glimindA

  Fetch new reliability alerts for your subscription token (events since your last poll, then the cursor advances). Use this after watch_tool without a webhook to react to outages/recoveries — no public endpoint required. Returns events with tool id, severity, and a link.

  ConnectorNo auth

• generate_article_briefA

  VarynForgeA

  Forge a writer-ready brief from an article suggestion. `channel` picks the brief template: article (default, SEO article outline), reels (hook/beats/shot list), youtube (retention beats/chapters), x (thread posts), linkedin (carousel slide deck: cover hook, one-idea slides, recap, CTA). A suggestion holds one brief per channel — generating a second channel adds a brief without touching the others. When the suggestion already has an article brief, channel briefs DERIVE from it (its key points, hook, and keyStats flow into the channel shape) and are free — they do not consume a daily brief slot. Idempotent per channel: if that channel already has a brief, returns it without consuming a slot; pass `force: true` to regenerate it. When regenerating, pass `guidance` — corrective direction the forge must follow (e.g. the angle the operator actually wants, a section to drop, an audience correction) — instead of re-rolling blind and hoping. Free tier: 10/day for article briefs and non-derived channel briefs. Returns `{ entitlement }` when the daily cap is reached.

  ConnectorNo auth

• delete_form_submissionA

  NovenceA

  Permanently delete one form submission (PII). Does not disable the form — use update_form status=disabled. Irreversible.

  Connector

  Destructive

  No auth

• restore_formA

  RooQuizA

  Restore a form from the trash in the current team (undo delete_form). Only the form owner or the team owner / admin can restore; errors if the form is not in the trash.

  ConnectorAPI key

• restore_formA

  RooQuizA

  Restore a form from the trash in the current team (undo delete_form). Only the form owner or the team owner / admin can restore; errors if the form is not in the trash.

  ConnectorAPI key

• french_cleat_planA

  Fredenslund workshop toolsA

  Plan a French cleat wall for a workshop with the Fredenslund cleat system: 90 mm cleat boards and 90 mm gaps (180 mm pitch), hook plate 72 mm including 12 mm material, 30 mm buffer between hangers, a 900 mm table that hangs on its own cleat one hook lower (cleat top 840) with the rows following that cleat, top cleat at least one gap below the ceiling, lowest cleat at least 210 mm above the floor (its underside; rows 300 … 2280 on the default wall). A hanger comes off by lifting it the material + 3 mm, so the hook plate is at most the gap − 3 and the top cleat at least the hook plate + 3 below the ceiling. The default wall is a full plywood sheet, 1220 × 2440 mm. Give the wall size and the hangers to hang (hooks, shelves, boxes, panels: left edge, the cleat row it hangs on, width, extra rows spanned below — a shelf usually spans one row). Returns the cleat rows (cleat top heights from the floor), every hanger with its panel height and whether it fits — and why not (row missing, row off, outside wall, collision) — the cut list with cleat metres, wall coverage, a picture of the wall (a link to a 1200 × 630 PNG) and a link that opens the same plan editable in the tool. All values in mm. Call with no hangers to get the rows for a wall first. Beta.

  ConnectorNo auth

• quote_ad_proof_packA

  Clip Studio MCPA

  Quote an Ad Lab Proof pack. Does not generate. Default 6 slides at 4:5: hook, in-the-life stills for the user’s niche, and a soft CTA. Pass hasScreenshot true when a product screenshot will be composited on the last slide.

  ConnectorOAuth

• bluffo_actA

  Bluffo — the bluffing game for AI agentsA

  Make your move. type="clue": one short sentence describing your word WITHOUT saying it. type="vote": `target` = a seat number from action.candidates, optional `say` = your one-line reason (public; like every text you send it must not contain your word — if it does, the vote still counts and the reason is dropped with a `warning`). The response says what you cast (`cast`). type="say": a comment during discussion/voting. type="react": float an `emoji` over your seat. type="leave": leave the table. Any move may carry `react` (an emoji) and `wait` (then this call also waits for your next move — the response IS your next state).

  ConnectorNo auth

• export_runA

  Hook DetectorA

  A finished run's hooks as a file a creator can open: format "csv" (default; one row per hook, opens in any spreadsheet, formula-like cells defused with a leading quote), "json" (the full hook objects) or "md" (Markdown notes, one section per hook). Returns {"filename", "content_type", "format", "content"}, where content is the whole file as text: write it to filename. The same bytes as GET /v1/runs/{run_id}/export?format=... . Free. Errors: 404 run_not_found, 409 run_not_finished while the run is queued or running (call get_run with wait_seconds=50 first), 422 invalid_request for another format.

  ConnectorNo auth

• search_docsA

  Devdocs IoB

  Find which documentation SETS exist whose NAME matches a substring (e.g. "python" → Python 3.x, "react" → React). Returns doc SETS, NOT their content — this does NOT look up a function/method/API name. To search inside a doc for an entry like "Array.map" or "fetch", use search_index (slug + query).

  ConnectorNo auth

• load_skillA

  formbaseB

  Load a domain-knowledge skill — themes, settings, analytics, logic-rules, editing-flows, question-types, etc. Returns markdown reference content. Use when the task touches a domain whose conventions or constraints are not obvious from the surrounding tools. For loading additional MCP tool catalogs (deferred tools by bundle name) use `load_tools` instead. Available skills: - toon-format: TOON format reference for reading and parsing form document structure - question-types: All question types with parameters, validation, and when to use each - logic-rules: Conditional logic conditions, actions, patterns, and examples - editing-flows: Editing workflows, node chaining, batch operations, and best practices - form-best-practices: Form design best practices for question design, ordering, and type selection. - analytics: Form analytics interpretation, metrics, and actionable insights - form-settings: Form configuration options, security, notifications, email customization, and data retention - form-themes: Form visual theming system — schema, constraints, design guidelines, and examples - requests: Requests: asking named people to fill a form — field keys, prefill shapes, delivery, callbacks, polling

  ConnectorOAuth

• get_project_contextA

  mainA

  Captures the user's project architecture to inform i18n implementation strategy. ## When to Use **Called during i18n_checklist Step 1.** The checklist tool will tell you when to call this. If you're implementing i18n: 1. Call i18n_checklist(step_number=1, done=false) FIRST 2. The checklist will instruct you to call THIS tool 3. Then use the results for subsequent steps Do NOT call this before calling the checklist tool ## Why This Matters Frameworks handle i18n through completely different mechanisms. The same outcome (locale-aware routing) requires different code for Next.js vs TanStack Start vs React Router. Without accurate detection, you'll implement patterns that don't work. ## How to Use 1. Examine the user's project files (package.json, directories, config files) 2. Identify framework markers and version 3. Construct a detectionResults object matching the schema 4. Call this tool with your findings 5. Store the returned framework identifier for get_framework_docs calls The schema requires: - framework: Exact variant (nextjs-app-router, nextjs-pages-router, tanstack-start, react-router) - majorVersion: Specific version number (13-16 for Next.js, 1 for TanStack Start, 7 for React Router) - sourceDirectory, hasTypeScript, packageManager - Any detected locale configuration - Any detected i18n library (currently only react-intl supported) ## What You Get Returns the framework identifier needed for documentation fetching. The 'framework' field in the response is the exact string you'll use with get_framework_docs.

  ConnectorNo auth

• run_testsA

  flootA

  Run the project's Jasmine spec files (helpers/*.spec.tsx) headlessly on the project VM (jsdom — no browser needed). Frontend AND backend code is testable: specs may render components (@testing-library/react) or import endpoint handlers/backend helpers and call them directly. Limits: fetch throws inside tests (mock with spyOn(globalThis, "fetch")), process.env secrets are absent, and specs importing @floot/* service modules are skipped (no mocks yet). Returns per-file PASS/FAIL with failing expectations. Defaults to all spec files except hook specs (file name contains "use" — those need real React scheduling and are excluded, matching the in-editor checker); pass `paths` to run specific spec files, including hook specs.

  ConnectorOAuth

• create_google_lead_form_extensionA

  Metadata MCP ConnectorA

  Add an inline lead-capture form attached to a Google Ads ad — prospects submit their email plus optional contact and work info without leaving the SERP. Drives higher conversion than landing-page redirects and feeds leads straight into Metadata. ALSO KNOWN AS: lead form, lead gen form, inline form, lead capture, contact form, demo request form, in-ad form, form extension KEYWORDS: lead form, lead gen, lead capture, form, contact form, demo request, inline form, conversion, MQL, opt-in, signup, registration, google ads, extension WHEN TO USE: - "Add a lead form extension to capture demo requests under our search ads" - "Create an inline form asking for work email and job title" - "Set up a Google Ads lead-gen form with a 'Request Demo' CTA" - "Register a contact-us form extension for the homepage campaign" WHEN NOT TO USE: - Just want to drive clicks to a landing page (no inline form) → use create_google_sitelink_extension - Want to plug a single product / pricing tier under the ad → use create_google_price_extension - For Microsoft Ads / Bing — Microsoft does not surface inline lead forms via the platform; pick a different extension type or use a landing-page redirect. - For Facebook lead forms or LinkedIn LeadGen — those are separate channel surfaces, not search-channel ad-extensions. INPUTS (required): - headline: form headline (≤30 chars). - business_name: advertiser name shown in form (≤25 chars). - privacy_policy_url: link to your privacy policy (Google requires it). - post_submit_headline: thank-you screen headline (≤30 chars). - post_submit_description: thank-you screen body (≤200 chars). - post_submit_call_to_action_type: button on the thank-you screen. VISIT_SITE | DOWNLOAD | LEARN_MORE | SHOP_NOW. - call_to_action_type: main CTA on the ad. APPLY_NOW | BOOK_NOW | CONTACT_US | DOWNLOAD | GET_INFO | GET_OFFER | GET_QUOTE | GET_STARTED | JOIN_NOW | LEARN_MORE | REGISTER | REQUEST_DEMO | SIGN_UP | SUBSCRIBE. - call_to_action_description: sub-text under the CTA (≤30 chars). - email_lead_form_user_input_types: at least one of WORK_EMAIL, EMAIL. INPUTS (optional): - description: form body text (≤200 chars). - contact_lead_form_user_input_types: any of FIRST_NAME, LAST_NAME, PHONE_NUMBER, CITY, POSTAL_CODE, REGION, COUNTRY, STREET_ADDRESS. - work_lead_form_user_input_types: any of COMPANY_NAME, JOB_TITLE, WORK_PHONE. - url: thank-you-page URL after submit.

  ConnectorAPI key