Install the APIANT Claude Code Plugin and Claude Code gains the ability to build integrations, edit assemblies, run tests, deploy to production, write docs, and diagnose customer issues. Below is the complete inventory: 35 skills, 125 MCP tools, each one a real capability Claude can invoke on your behalf.
The APIANT Claude Code plugin ships three MCP servers and a skills library. Install it, open Claude Code, and the entire platform becomes addressable through natural language.
Run once. The plugin verifies MCP connections, env vars, and plugin version. Claude announces what's live and what's missing.
"Build a Mindbody to Shopify sync." Claude Code picks the right skill, activates the right toolset, and starts executing with live feedback.
Claude composes assemblies, tests end-to-end, fixes failures, deploys to prod, and monitors the account, without handoffs.
Every skill is a procedure a senior APIANT engineer follows, encoded and executable by Claude Code. Click any card for the full what/when/how.
Verify MCP connections, environment, and plugin version. Run on first install or when something breaks.
"Connect X to Y." Claude picks triggers, actions, field mappings, and stands up the entire flow.
The integration plumbing: OAuth, API Key, or no-cred connectors, triggers, and actions (ADD/GET/LIST/UPDATE/DELETE/FIND).
Multi-automation deployments: two-way sync, data pipelines, coordinated workflows with shared state.
Form schema for lead capture, onboarding, or config, wired straight into an APIANT automation.
Add a step, fix the mapping, swap Mailchimp for Klaviyo, disable a branch. Surgical, non-destructive edits.
Fix JSP, update API calls, change endpoints, rename settings, edit dropdowns, with full diff awareness.
Execute, inspect results, diagnose failures, apply fixes, retest, and run branch coverage automatically.
Validate data flow between automations, shared state, loop prevention, and cross-automation coordination.
Publish template automations and push linked deployments to customer accounts in one coordinated step.
Poll an endpoint on a schedule and fire when a new record appears. The workhorse trigger.
Polls and fires when a record is created or modified. Tracks last-seen cursor automatically.
You paste a URL into the source app. Incoming posts fire the automation.
APIANT creates and tears down the webhook automatically via the target app's API. Zero manual setup.
Credential-based webhook URL with event filtering. Multiple event types route on a single endpoint.
APIANT-to-APIANT internal protocol. Enables chained automations across accounts and environments.
Create a new record in the target app. Handles validation, required fields, and response parsing.
Remove a record by ID or criteria. Safe-mode defaults with rollback metadata preserved.
Search by criteria, return matches. Used for dedup, upsert, and enrichment patterns.
Retrieve one record by ID. The simplest read path. Often chained after FIND or NEW.
Page through results with cursor or offset handling. Rate-limit aware by default.
Patch existing records. Partial updates supported. Only touches the fields you specify.
OAuth V2, API Key, or no-credential auth. Handles token refresh, scopes, and revocation.
Drive a dev browser to register an OAuth app on a vendor portal, capture client_id and secret into the keyvault.
Migrate legacy human-built assemblies to the AI-template pattern so Claude can safely edit them.
Builds the matching trigger and action pair for a two-way sync. Handles loop prevention, last-write-wins, and conflict resolution out of the box.
From simple chatbots to multi-goal conversation flows with memory and tool-calling automations.
Drop in a spreadsheet of "source field -> target field" and Claude wires the mappings verbatim.
Parent/child flows with query-string parameter passing and webhook payload forwarding.
Pause an automation until a person approves or denies via moderation queue link. Decision gates for AI flows.
Launch N child automations in parallel, wait for all to finish, proceed with aggregated results.
Pause an automation until a specific datetime. Useful for drip sequences and scheduled follow-ups.
Watches prod automations for errors. Designed for /loop recurring runs. Alerts with full trace context.
"Why did this not process?" Claude searches execution history, traces failures, extracts HTTP, proposes a fix.
Control which errors retry, which 401s bypass auto-turnoff, alert text rewriting, dismissal lists.
Skills drive the workflow. MCP tools do the actual work against APIANT's dev, prod, and docs environments. Tools are grouped into toolsets. Only the core set is always loaded; the rest activate when a skill asks for them, so the agent's context stays lean and the capability stays deep.
Load the specific toolset needed for the current skill. Keeps the context window lean.
Load, list, create, update, rename, and delete assemblies. The low-level assembly API.
Structured overview of an automation: triggers, steps, mappings. Fast context for edits.
Flat list of every automation in a scope. Filter by name, folder, or status.
Navigate the folder tree. Find automations grouped by customer, product, or environment.
Create, rename, duplicate, move, enable, disable. Every CRUD operation for automations.
The full catalog of available app integrations. Filter by category, vendor, or capability.
30 tools. Search the catalog, compose triggers and actions, edit mappings, commit versions, save patterns. The full automation authoring surface.
17 tools. Run test executions, inspect every step's input and output, mutate data, replay webhooks, walk branch-coverage test points. Debugging with full ground truth.
10 tools. List and organize committed automations, version them, compare versions, roll back. The git-like layer over automation drafts and releases.
25 tools. Switch between customer accounts, query usage and health across a tenant, read the keyvault, run ad-hoc SQL, tune retryable errors, manage lookups. The operator's toolbox.
5 tools. Tenant-wide alert rules, suppressed-alert lists, retry policy, 401 domain carve-outs. Requires Switch Account context.
11 tools. Per-automation alert mapping rules, step-level alert triggers, mapping trace, suppression, system-level mappings.
3 tools. Search, save, and delete reusable pattern recipes: field mappings, transforms, gotchas, templates.
6 tools. Publish folders or individual assemblies from dev to prod. Roll changes out to linked customer accounts in a single coordinated step.
28 tools. Create connectors, inject settings, compile JSP, test API endpoints, wire dynamic field discovery, finalize assemblies. The low-level integration plumbing.
Programmatic access. Issue a docs API key for CI/CD or automated publishing.
Retrieval-augmented Q&A. Claude asks the docs corpus before writing code or answering.
Publish a new doc. Title, body, parent, tags, and status, in one call.
Browse the full table of contents. Filter by section, tag, or status.
Authenticate the docs session. Tokens cached for the session.
Fetch the full contents of any doc. Markdown, images, and metadata included.
Take a live screenshot of the editor or platform UI and embed it into a doc.
Semantic + keyword search across the entire docs corpus. Ranked results with context.
Edit title, body, tags, or status. Revisions tracked automatically.
Attach an illustration or diagram to any page. Auto-alt-text generated.
List revisions, diff between versions, roll back if needed.
''Try a shorter query, remove a filter, or clear the search.
A SaaS team runs a boutique fitness CRM on HubSpot. Two thousand paying customers want their HubSpot contacts to sync two-way with Mindbody clients. Classic white-label integration. Historically: four to six weeks of engineering.
catalog_list_apps({ vertical: 'wellness' }) -> hubspot, mindbody auto_folder({ action: 'create', path: '/customers/boutique-fit' }) -> ok pattern_search({ shape: 'bidirectional-sync' }) -> 2 matches
auto_build({ trigger: 'assembly-trigger-updated', source: 'hubspot.contact' }) auto_edit_structure({ add_step: 'assembly-action-find', app: 'mindbody.client' }) auto_edit_structure({ add_step: 'assembly-action-add-or-update' }) auto_edit_mapping({ fields: [email, firstName, lastName, phone, membership_tier] })
HubSpot stores tier as a free-text dropdown. Mindbody expects one of four enum values. Claude detects the mismatch, adds a lookup-table transform, and saves it as a pattern so the reverse direction reuses it.
auto_build({ trigger: 'assembly-trigger-new', source: 'mindbody.client', interval: '5m' }) pattern_search({ name: 'membership_tier_enum' }) -> reusing from A auto_edit_mapping({ reverse: true, pattern: 'membership_tier_enum' })
Mindbody webhooks silently drop events during high-volume periods. Claude defaulted to polling with a 5-minute cursor, and noted this as a known-gotcha in the pattern library so future Mindbody integrations get the same treatment.
asm_set_action_throttle({ assembly: 'hubspot.contact.update', rate: 100, window: '10s' }) asm_set_connector_throttle({ connector: 'hubspot.v3', burst: 20 })
Throttling per automation would let any other HubSpot flow exhaust the budget. Throttling at the assembly (connector + action) applies the limit across every automation in the tenant, which is the only correct level for a shared API.
exec_test_automation({ direction: 'A', input: <synthetic> }) -> ok (1.2s) exec_test_automation({ direction: 'B', input: <synthetic> }) -> ok (1.8s) exec_get_assembly_log({ check: 'echo_loop' }) -> suppressed 14/14 test cases pass
deploy_publish_assembly({ folder: '/customers/boutique-fit' }) -> v1.0.0 deploy_list_linked_accounts({ template: 'hubspot-mindbody-sync' }) -> 2000 accounts deploy_to_accounts({ batch_size: 50 }) -> 2000/2000 ok
What the builder did not do: write a single line of JSP. Hand-map a single field. Open the Mindbody developer docs. File a ticket about the tier enum. Wait four to six weeks.
> Customer Alpine Clinic says nothing synced last night. ● /support searching execution history found 47 failures at 02:14 UTC root cause: Cliniko API returned 429 (rate limit) during bulk backfill ● /edit-automation -> adding exponential backoff to step 3 retested. replayed failed runs.
> Stop auto-disabling Shopify on 401s from the sandbox tenant. ● /alert-handling admin_ignore_401_domains += sandbox.shopify.com alert_suppress: 'Stale sandbox token' pattern verified against last 24h history noise dropped from 140 to 3 alerts/day
Traditional platforms wrap APIs in UI. APIANT wraps the entire platform in a Claude-Code-addressable plugin. The difference shows up everywhere.
Integrations that used to take weeks ship in a single Claude Code session. Iteration is conversational.
Skills encode what senior APIANT engineers do. Claude doesn't improvise. It follows vetted playbooks with verification steps.
The plugin separates dev and prod. Claude can inspect prod freely; writes require an explicit deploy skill.
The APIANT Claude Code plugin ships with an APIANT license. Tell us what you are integrating, we set you up, and Claude runs the platform from your terminal.
Your request will be posted to our Discord community, where independent builders who run their own APIANT-powered platforms can see it and reach out to you directly to build the integration.
← BackWe'll take a quick look to learn about your business.
Based on what we found, here are integration products that might be a great fit.
Your integration specialist is ready. Alex already knows your platform and what you're looking to build. Choose how you'd like to connect:
Voice call happens right in your browser. WhatsApp options open the app.
Prefer email? We'll follow up at within 2 hours.
Click the button below to start talking. Alex already has your details.
Your browser will ask for microphone access.
← BackExpect to hear from us within one business day.
Something went wrong. Please try again.